A race condition in the Linux kernel tracing subsystem allows multiple threads to free the same module_delta data twice or to update it while it is being freed. The resulting double‑free or use‑after‑free can corrupt kernel memory, causing kernel crashes or, depending on the attacker’s ability to control the freed data, arbitrary code execution. The flaw arises because the functions tracing_open, tracing_read_pipe, and tracing_buffers_read do not hold trace_types_lock before manipulating module_delta, violating the kernel’s memory safety guarantees.

All Linux kernel releases are affected because the source references the generic "Linux:Linux" vendor–product pair and no specific version scope is listed. The vulnerability exists in any kernel configuration that enables the tracing subsystem, including the default kernel image used on most production systems.

The CVSS score of 7.8 indicates a high severity flaw. EPSS data is not available, so the probability of exploitation cannot be quantified from the provided information. The issue is not listed in the CISA KEV catalog, suggesting no publicly known exploits yet. Exploitation would require an attacker with local or privileged access to trigger concurrent trace reads or open operations, which is a realistic scenario for privileged users or compromised applications.