The Linux kernel tracing subsystem contains a memory corruption flaw that occurs when a "STACKTRACE" histogram key is parsed. Parsing this key leads to an unbounded memcpy that reads from an arbitrary kernel address, which in turn triggers a general protection fault and a kernel panic. The outcome is a denial of service by halting the affected system. The vulnerability stems from improper bounds checking in the field parsing logic, representing a classic out‑of‑bounds copy (CWE‑787).

All Linux kernel versions built with the original tracing implementation are affected. The fix appears in the commits linked in the advisory (e.g., 7f711e62355bb3123a2ca2f97a2facbfebc678c6). Without a specific version range in the advisory, any kernel released before these commits should be considered vulnerable. Detailed version information is not provided, so a conservative approach is to treat all pre‑patch kernels as at risk.

The CVSS score of 7.0 indicates high severity, while the EPSS score of less than 1% suggests a very low probability of exploitation. The flaw is not listed in the CISA KEV catalog. The likely attack vector is a local attacker who can write to the /sys/kernel/tracing interface to configure a histogram key, which normally requires privileged access. Once the trigger is written, the kernel will panic, disrupting all users on the machine. The consequence is immediate service disruption; confidentiality and integrity are not directly affected beyond the crash.