Technical impact
The vulnerability in the Linux kernel lies in the calculation of sub-buffer array indices for persistent ring buffers. The function that determines the index can return a value one too high, causing an off‑by‑one error when initializing the sub-buffer identifiers. This leads to a NULL pointer in the first entry of the array. When a user process maps the trace_pipe_raw channel, the kernel dereferences this NULL entry, triggering a memory fault. The misalignment also corrupts internal metadata, so that on the next system boot the kernel rejects incomplete trace data and abandons the previous trace, potentially causing additional instability. The overall impact includes kernel panic, data loss, and denial of service for systems relying on kernel tracing.
Affected Systems
The vulnerability is present in Linux kernel versions that predate the commit correcting rb_meta_subbuf_idx. Any distribution shipping such kernels, with persistent ring buffers enabled, may be impacted.
Risk and Exploitability
The CVSS score of 4.4 indicates low to moderate severity, and the EPSS score of <1% suggests a very low current exploitation probability. The vulnerability is not listed in CISA’s KEV catalog. The likely attack vector is a local user process that has permission to map trace_pipe_raw or otherwise enable persistent ring buffers; the attacker would trigger the fault by performing such a mapping. No publicly demonstrated exploits exist, but the defect is straightforward to trigger if the attacker can invoke the trace subsystem. Consequently, systems that require high uptime or rely heavily on trace data integrity should treat this as a moderate risk.
Debian DLA