CVE-2026-97600: Linux kernel · ieee802154: cc2520: fix FIFOP work use-after-free
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ff5891b266a7fc6a062710836be84f1cc19338b5 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:18 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ff5891b266a7fc6a062710836be84f1cc19338b5, c68fd52c73b676aee67020011e98fea125a978f4, 890a80d516a1447db5c21bf92841a82914ea897d +2
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: ieee802154: cc2520: fix FIFOP work use-after-free The FIFOP interrupt handler queues cc2520_fifop_irqwork. On removal, cc2520_remove() only flushes the work. The devm-managed FIFOP IRQ remains active until after ->remove() returns and can queue the work again after that flush, allowing it to run after the private data is released. Disable the work with disable_work_sync() instead of flushing it, so the handler can no longer queue it once removal begins. Destroy the buffer mutex last, since the worker and the stop callback invoked through ieee802154_unregister_hw() both take it. Found by an in-house static analysis tool.
References
- git.kernel.org/stable/c/4a1ba62a486a4c43af91d01661a95e82dc4aaefa (opens in a new tab)
- git.kernel.org/stable/c/56a9919d8494fb118eebf167bef0622528fbf2e7 (opens in a new tab)
- git.kernel.org/stable/c/c68fd52c73b676aee67020011e98fea125a978f4 (opens in a new tab)
- git.kernel.org/stable/c/890a80d516a1447db5c21bf92841a82914ea897d (opens in a new tab)
- git.kernel.org/stable/c/ff5891b266a7fc6a062710836be84f1cc19338b5 (opens in a new tab)