CVE-2026-89503
In the Linux kernel, the following vulnerability has been resolved: …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/2dc510957fe8fd098ab3c3147ebdf34d00cd2734
- git.kernel.org/stable/c/53106e9262a310ef2c9a9321168c03705940c678
- git.kernel.org/stable/c/e743527c5bfdceda1095bc0a9e596e2aebb6a9c3
- git.kernel.org/stable/c/2313ff69bd237aad264a5913907f374f958335a2
- nvd.nist.gov/vuln/detail/CVE-2026-89503
- cve.org/CVERecord?id=CVE-2026-89503
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.