Description
In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix subbuf resize race with ring_buffer_alloc_read_page() ring_buffer_alloc_read_page() is racy with ring_buffer_subbuf_order_set, it can allocate a reader page with an outdated order. This isn't a big issue, the user can still re-allocate a new reader page and try again. However, what is more problematic is if the value of subbuf_order changes in the middle of ring_buffer_alloc_read_page(). In that case, bpage->order might not match the actual allocated memory. Use bpage->order for the allocation to prevent this race.
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
bce761d757452ba5eb77e11fecc37a04b67494e7 to < 2313ff69bd237aad264a5913907f374f958335a2affectedbce761d757452ba5eb77e11fecc37a04b67494e7 to < 2dc510957fe8fd098ab3c3147ebdf34d00cd2734affectedbce761d757452ba5eb77e11fecc37a04b67494e7 to < 53106e9262a310ef2c9a9321168c03705940c678affectedbce761d757452ba5eb77e11fecc37a04b67494e7 to < e743527c5bfdceda1095bc0a9e596e2aebb6a9c3affected
Linux Linux
Default version status: affected
6.8affected0 to < 6.8unaffected6.12.112 to ≤ 6.12.*unaffected6.18.50 to ≤ 6.18.*unaffected7.2.4 to ≤ 7.2.*unaffected7.3 to ≤ *unaffected