The vulnerability in the Linux kernel ring‑buffer module allows a race condition during concurrent resizes that causes a page to be freed with an incorrect order. When the ring buffer is resized, the free_page routine uses the current global subbuf_order value, which may differ from the order used to allocate the page. This mismatch can corrupt kernel memory, leading to a crash or leaking memory as the incorrect page order is applied to free operations. The weakness is a race condition, classified as CWE‑763.

All installations of the Linux kernel that include the ring‑buffer code without the recent patch are affected. No specific version range is listed, so any kernel compiled with this unpatched implementation carries the risk.

The CVSS score is 4.1 and the EPSS score is less than 1%, indicating a very low probability of exploitation. The flaw is not listed in the CISA KEV catalog. The exploit requires a concurrent ring‑buffer resize, which typically needs privileged access to trigger the race. Because the conditions are restrictive and the likelihood is low, the overall risk is moderate but the potential impact is system destabilization.