fuse: publish io-uring queues with release semantics
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.517.2.37.3In 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.
From the CVE record · Linux
The Linux kernel can publish a FUSE io-uring queue pointer before the queue’s fields are guaranteed to be visible to concurrent readers. A concurrent reader may access improperly initialized fields; the input does not establish an attacker-controlled exploit path or specify authentication or user-interaction requirements.
Teams running Linux kernels with FUSE io-uring support should check their kernel versions against the vendor advisory; affected versions are not specified.