Linux
ring-buffer: Fix subbuf resize race with ring_buffer_alloc_read_page()
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= bce761d757452ba5eb77e11fecc37a04b67494e7, < 2313ff69bd237aad264a5913907f374f958335a2
- >= bce761d757452ba5eb77e11fecc37a04b67494e7, < 2dc510957fe8fd098ab3c3147ebdf34d00cd2734
- >= bce761d757452ba5eb77e11fecc37a04b67494e7, < 53106e9262a310ef2c9a9321168c03705940c678
- >= bce761d757452ba5eb77e11fecc37a04b67494e7, < e743527c5bfdceda1095bc0a9e596e2aebb6a9c3
Fixed in 2313ff69bd237aad264a5913907f374f958335a2, 2dc510957fe8fd098ab3c3147ebdf34d00cd2734, 53106e9262a310ef2c9a9321168c03705940c678, e743527c5bfdceda1095bc0a9e596e2aebb6a9c3
- 6.8
Fixed in 0, 6.12.112, 6.18.50, 7.2.4, 7.3
Mitigation
Upgrade Linux to 2313ff69bd237aad264a5913907f374f958335a2 or 2dc510957fe8fd098ab3c3147ebdf34d00cd2734 or 53106e9262a310ef2c9a9321168c03705940c678 or e743527c5bfdceda1095bc0a9e596e2aebb6a9c3 or later.
Upgrade Linux to 0 or 6.12.112 or 6.18.50 or 7.2.4 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.