Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: fuse: publish io-uring queues with release semantics fuse_uring_create_queue() initializes a fuse_ring_queue and then publishes the pointer into ring->queues[qid] with WRITE_ONCE() under the fch->lock. There are several readers that may concurrently be fetching that pointer locklessly and then deferencing it. WRITE_ONCE() doesn't ensure ordering of the queue's field initialization before the ring->queues[qid] pointer assignment. The queue must be published with smp_store_release() so the field initialization is guaranteed to happen before. Readers in paths where the read may happen concurrently with the store need to use READ_ONCE() because any race involving a plain access is undefined.
References
- https://git.kernel.org/stable/c/42df916e5a5f8fb4b60c8cefb54318d1ec02c580
- https://git.kernel.org/stable/c/a1bb359c443d048fe5dfd6ca9caf4e3897f3e9aa
- https://git.kernel.org/stable/c/a5bb215dbc34b4c6a5e144ea1416bf66450d519f
FAQ
What is CVE-2026-80858?
CVE-2026-80858 is a documented vulnerability. In the Linux kernel, the following vulnerability has been resolved: fuse: publish io-uring queues with release semantics fuse_uring_create_queue() initializes a fuse_ring_queue and then publishes th...
How severe is CVE-2026-80858?
CVSS scoring is not yet available for CVE-2026-80858. Check NVD for updates.
Is there a patch for CVE-2026-80858?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.