Technical impact
A NULL pointer dereference occurs in the Linux kernel tracing subsystem when a user switches to a tracer that defines neither static nor default flags such as hwlat, irqsoff, or wakeup. The kernel assigns a null pointer to tr->current_trace_flags, but the ring buffer still contains entries from the previous tracer. When print_graph_function_event attempts to print one of these entries, it dereferences the null pointer, causing a kernel null pointer fault and a system panic, leading to a denial of service.
Affected Systems
The vulnerability affects all Linux kernel versions prior to the patch that introduced a non‑NULL fallback for tr->current_trace_flags. The issue resides in the generic tracing infrastructure and is not limited to a specific architecture or distribution; any kernel that implements the affected tracing logic is susceptible.
Risk and Exploitability
The CVSS score is 4.4, indicating a moderate impact. The EPSS score is < 1%, showing a very low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog. Based on the description, it is inferred that the attack vector requires local access with the ability to write to /sys/kernel/tracing (e.g., a user with elevated privileges). Once exploited, the kernel crashes immediately, resulting in a denial of service rather than remote code execution. No publicly documented exploits exist, but the nature of a kernel panic makes proper mitigation necessary.