PT-2026-85736 · Linux · Linux

CVE-2026-80858

·

Published

2026-09-04

·

Updated

2026-09-04

None

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.
Found an issue in the description? Have something to add? Feel free to write us 👾

Related Identifiers

CVE-2026-80858

Affected Products

Linux