Technical impact
The Linux kernel’s eventfs subsystem frees its inode at the end of an SRCU grace period without ensuring that all readers have finished. A pathwalk that calls tracefs_d_revalidate() can therefore read a dentry that points to an inode that has already been freed, causing a slab use‑after‑free. This kernel memory corruption can destabilize the system, leading to crashes or unpredictable behavior, but the official data does not state any confirmed privilege escalation or denial‑of‑service scenarios.
Affected Systems
All Linux kernels that were built before the commit that introduced the SRCU‑based fix (8e556432477e) are affected. This includes every distribution’s stock kernel that predates that change, meaning practically all kernels distributed before the patch was released are vulnerable.
Risk and Exploitability
The CVSS score of 7.8 indicates high severity and the EPSS score of < 1% points to a low chance of exploitation, and the vulnerability is not listed in CISA KEV, implying no known public exploits. Based on the description, it is inferred that the likely attack vector is a local user invoking system calls such as statx or fstatat that trigger a pathwalk through tracefs, which can cause the use‑after‑free. The impact remains kernel memory corruption and system instability, without immediate privilege escalation, yet it requires mitigation especially on systems that expose tracefs or eventfs to users.
Debian DLA