Technical impact
The vulnerability is a race condition between the FireWire core response handler and the timeout callback. Both functions may manipulate the same transaction entry in the pending list, and when a timer deletion returns zero the timeout callback could already be running; the response handler may mistakenly process the entry as well. This double manipulation can lead to a use‑after‑free of the transaction structure, allowing an attacker with local access to corrupt kernel memory or execute arbitrary code. Additionally, the improper removal of the transaction entry when the timeout callback runs (CWE-825) further exacerbates the memory corruption risk.
Affected Systems
All Linux kernel versions that contain the legacy split transaction logic and have not applied the recent patch are potentially vulnerable. The issue is not tied to a specific distribution but affects the generic Linux kernel core. Any system that supports FireWire and loads the firewire core module could be impacted.
Risk and Exploitability
The flaw has no confirmed public exploitation, but its EPSS score is <1%, indicating a low likelihood of widespread exploitation. It remains a high‑severity kernel bug due to the use‑after‑free, with a CVSS score of 8.8. The attack vector is local, with an attacker needing access to a FireWire interface or the ability to generate split transactions against the kernel.