Impact
Internal kernel tracepoints in the TIPC module accidentally dump the socket receive queue while holding a spinlock that does not protect the queue against concurrent consumption. This dereferences memory that may have already been freed, causing a use‑after‑free error as confirmed by KASAN. The resulting memory corruption can abort the kernel, potentially causing a denial of service. The weakness is an improper synchronization exploit.
Affected Systems
Linux kernels that contain the tipc module before the commit referenced in the advisory are affected. This includes all releases of the mainline Linux kernel up to the point where the fix was merged. No specific version ranges are listed, so all susceptible kernels are at risk.
Risk and Exploitability
The CVSS score is 9.8, and the EPSS score is < 1%, indicating a high severity but low exploitation probability. The bug is triggered when a user‑level process initiates a TIPC enqueue operation while the TIPC_DUMP_ALL tracepoint is enabled, typically a privileged debugging capability. The vulnerability is not listed in CISA's KEV catalog, implying no confirmed exploitation reports. Nonetheless, the local nature of the trigger means that an attacker with sufficient local privileges could invoke the vulnerability by enabling the relevant tracepoints and causing the TIPC socket to process queued packets. The likely attack vector is local, requiring the attacker to have access to processes that can enable tracepoints and interact with the tipc module.
OpenCVE Enrichment
Debian DLA