Technical impact
The Linux kernel tracing subsystem contains an improper bounds check in the predicate_parse function. The function accesses the operator stack before validating opening parentheses, and the push operation can write beyond the last allocated stack entry when the stack top already points to the final slot. This results in an out‑of‑bounds write that can corrupt kernel memory. The vulnerability is a classic example of improper bounds checking (CWE‑787), which may affect the confidentiality, integrity, or availability of the kernel once triggered.
Affected Systems
All Linux kernel builds are potentially affected since no specific releases are listed as vulnerable or fixed in the available data. The CPE entry cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:* indicates the entire Linux kernel family, and the vendor information lists Linux as the affected vendor. Without explicit version data, any deployed kernel may be at risk until a fix is applied.
Risk and Exploitability
The CVSS score of 7.1 indicates a medium severity vulnerability, and the EPSS score of less than 1% suggests that observed exploitation is limited or absent in public data. The vulnerability is not yet listed in the CISA KEV catalog. Because the flaw occurs in kernel memory, it could lead to privilege escalation or system compromise if an attacker can supply crafted trace data or otherwise trigger the out‑of‑bounds write. The likely attack vector is local or remote through the tracing subsystem; however, this is inferred from the nature of the code changes and not explicitly stated in the CVE data.
Debian DLA