https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 16:12:10 +0000 https://vulnerability.circl.lu/vuln/cve-2026-80859 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>fuse: fix missing barrier when checking io-uring readiness</p> <p>fuse_block_alloc() reads fch-&gt;initialized and then fch-&gt;io_uring. fch-&gt;io_uring is set before fch-&gt;initialized, ordered by the smp_wmb() in fuse_chan_set_intialized(), but fuse_block_alloc() has no matching read barrier between the two loads.</p> <p>This may lead a CPU to observe fch-&gt;initialized=1 but fch-&gt;io_uring=0, and skip the check that blocks request allocation until the io-uring queues are ready. This can reintroduce the lock-order inversion deadlock that commit 3393ff964e0f prevents.</p> <p>Add an smp_rmb() barrier to pair with the smp_wmb() in fuse_chan_set_initialized() to prevent this.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>fuse: fix missing barrier when checking io-uring readiness</p> <p>fuse_block_alloc() reads fch-&gt;initialized and then fch-&gt;io_uring. fch-&gt;io_uring is set before fch-&gt;initialized, ordered by the smp_wmb() in fuse_chan_set_intialized(), but fuse_block_alloc() has no matching read barrier between the two loads.</p> <p>This may lead a CPU to observe fch-&gt;initialized=1 but fch-&gt;io_uring=0, and skip the check that blocks request allocation until the io-uring queues are ready. This can reintroduce the lock-order inversion deadlock that commit 3393ff964e0f prevents.</p> <p>Add an smp_rmb() barrier to pair with the smp_wmb() in fuse_chan_set_initialized() to prevent this.</p> https://vulnerability.circl.lu/vuln/cve-2026-80859