The vulnerability resides in the Linux kernel’s tracing subsystem. When a histogram trigger fails to enable, the system attempts to roll back the registration but mistakenly allows a use‑after‑free of the trigger data. Because the freed memory can still be accessed by subsequent code paths, malicious input could corrupt kernel memory and potentially lead to arbitrary code execution at very high privilege. The underlying weakness is a classic use‑after‑free bug.

All Linux kernel releases that include the tracing subsystem and have not incorporated the commit that moves the registration logic into the failure path are potentially affected. The CVE description does not list specific kernel version identifiers; therefore, any kernel build prior to the fix should be considered at risk.

The severity of the flaw is moderate, reflected by the CVSS score of 5.5 and the potential for kernel memory corruption. The exploitability depends on the ability to trigger the enabling of a histogram trigger and induce its failure. While the CVE details do not explicitly state the attack vector, it is inferred that interacting with the tracefs interface—specifically writing trigger definitions—could trigger the bug. Thus, systems that expose tracing interfaces to non‑trusted users are at higher risk. The EPSS score is < 1% and the vulnerability is not listed in the CISA KEV catalog, indicating a very low probability of exploitation. The risk is therefore moderate for exposed systems, but widespread exploitation has not been observed yet.