CVE-2026-89503
- Source
- https://cve.org/CVERecord?id=CVE-2026-89503
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89503.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-89503
- Downstream
- Published
- 2026-09-11T19:43:51Z
- Modified
- 2026-09-13T03:47:18Z
- Summary
- ring-buffer: Fix subbuf resize race with ring_buffer_alloc_read_page()
- Details
-
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.
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89503.json" }- References
-
- https://git.kernel.org/stable/c/2dc510957fe8fd098ab3c3147ebdf34d00cd2734
- https://git.kernel.org/stable/c/53106e9262a310ef2c9a9321168c03705940c678
- https://git.kernel.org/stable/c/e743527c5bfdceda1095bc0a9e596e2aebb6a9c3
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89503.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-89503
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git