CVE-2026-80858
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.
Affected versions
Linux kernel versions
6.14
and later are affected. Fixed in
6.18.51,
7.2.3,
7.3
and their respective stable series.
References
3 totalFrequently asked questions
-
What is CVE-2026-80858?
CVE-2026-80858 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.14 onward and has been patched in 6.18.51, 7.2.3 and 7.3. CVE-2026-80858 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-80858?
Yes. CVE-2026-80858 has been patched. Fixed versions include 6.18.51, 7.2.3 and 7.3. If you are running Linux kernel 6.14 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-80858 actively exploited?
No. CVE-2026-80858 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.