Technical impact
The flaw occurs in the Linux kernel's tracepoint histogram handling. During synthetic event field validation, a stacktraced field that is marked as a stack can bypass proper type checks if its histogram counterpart is not a "long[" stacktrace array. This leads to the kernel interpreting an 8‑byte signed scalar value as a stack pointer. When trace_stack dereferences that value, the kernel may dereference an invalid address, causing an Oops and presenting an opportunity for a denial of service.
Affected Systems
Linux kernel builds that lack the recent commit series fixing the synthetic field validation. The issue is present in every kernel version prior to the inclusion of the commits referenced in the advisory. All architectures that rely on the tracing subsystem and accept user‑supplied synthetic events are affected.
Risk and Exploitability
Based on the description, it is inferred that the attack vector involves crafting a synthetic event with mismatched stacktrace definitions, which requires write access to synthetic events. The EPSS score is 0.00134, indicating a very low but nonzero exploitation probability, and the vulnerability is not flagged in the CISA KEV catalog. However, the flaw can be triggered by any user with permission to write synthetic events, which is a common capability for debugging or performance monitoring. The resulting Oops can crash the system, and because the exploit path is straightforward—crafting an event with mismatched stacktrace definitions—security teams should treat it as a moderate to high risk with a CVSS score of 7.8.
Debian DLA