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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
24fe962c86f55347385933a1b06ca71b60854690 to < a5bb215dbc34b4c6a5e144ea1416bf66450d519faffected24fe962c86f55347385933a1b06ca71b60854690 to < a1bb359c443d048fe5dfd6ca9caf4e3897f3e9aaaffected24fe962c86f55347385933a1b06ca71b60854690 to < 42df916e5a5f8fb4b60c8cefb54318d1ec02c580affected
Linux Linux
Default version status: affected
6.14affected0 to < 6.14unaffected6.18.51 to ≤ 6.18.*unaffected7.2.3 to ≤ 7.2.*unaffected7.3 to ≤ *unaffected