{"id":13836,"date":"2026-09-04T19:01:00","date_gmt":"2026-09-04T11:01:00","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-10671"},"modified":"2026-09-04T19:01:00","modified_gmt":"2026-09-04T11:01:00","slug":"cve-2026-10671","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-10671","title":{"rendered":"CVE-2026-10671 [HIGH] &#8211; In Zephyr&#8217;s kernel pipe implementation, the userspace syscall verifier z_vrfy_k_pipe_init("},"content":{"rendered":"<p>In Zephyr&#8217;s kernel pipe implementation, the userspace syscall verifier z_vrfy_k_pipe_init() in kernel\/pipe.c used K_SYSCALL_OBJ() (which requires the kernel object to already be initialized) instead of K_SYSCALL_OBJ_NEVER_INIT() (which rejects an already-initialized object). As a result, on CONFIG_USERSPACE builds an unprivileged user thread that has been granted access to a k_pipe object can invoke the k_pipe_init syscall to re-initialize a pipe that is already in use.<\/p>\n<p>z_impl_k_pipe_init() unconditionally resets the ring buffer, sets pipe-&gt;waiting to 0, and re-initializes both wait queues (z_waitq_init on pipe-&gt;data and pipe-&gt;space) without waking or accounting for threads currently blocked on the pipe. Any thread already pended in k_pipe_read()\/k_pipe_write() is left orphaned: still marked pending with pended_on pointing at the cleared wait queue and with stale qnode_dlist links into the (now re-initialized) embedded list head.<\/p>\n<p>When such an orphaned waiter is later timed out or woken, the scheduler calls sys_dlist_remove() on its stale node, writing through dangling prev\/next pointers into kernel wait-queue\/scheduler structures, causing list corruption (an attacker-driven invalid kernel write), lost wakeups, indefinitely blocked threads, and silent data loss. The flaw lets a deprivileged user thread corrupt the state of a kernel object shared with other threads\/partitions.<\/p>\n<p>The fix switches the verifier to K_SYSCALL_OBJ_NEVER_INIT(), matching the existing k_msgq_init verifier, so a user thread can no longer re-initialize a live pipe. The vulnerable code shipped in v4.1.0 and remained through v4.4.0.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In Zephyr&#8217;s kernel pipe implementation, the userspace syscall verifier z_vrfy_k_pipe_init() in kernel\/pipe.c used K_SYSCALL_OBJ() (which requires the kernel object to already be initialized) instead o<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-13836","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/13836","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=13836"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=13836"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=13836"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}