ring-buffer: Fix subbuf resize race with ring_buffer_alloc_read_page()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.112, 6.18.50, 7.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From bce761d757452ba5eb77e11fecc37a04b67494e7 · fixed in 2313ff69bd237aad264a5913907f374f958335a2; From bce761d757452ba5eb77e11fecc37a04b67494e7 · fixed in 2dc510957fe8fd098ab3c3147ebdf34d00cd2734; From bce761d757452ba5eb77e11fecc37a04b67494e7 · fixed in 53106e9262a310ef2c9a9321168c03705940c678; From bce761d757452ba5eb77e11fecc37a04b67494e7 · fixed in e743527c5bfdceda1095bc0a9e596e2aebb6a9c3
- Linux Linux
6.8
- KernelLinux
From 6.8.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4