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

> A use-after-free in the Linux kernel cc2520 driver allows attackers to cause denial of service or execute code via race conditions during device removal.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-104630, BELL-CVE-2026-97600, DEBIAN-CVE-2026-97600, GHSA-rq9h-jcg5-92gp, UBUNTU-CVE-2026-97600

## What is CVE-2026-97600?

CVE-2026-97600 is an use after free vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-97600?


## How do I fix CVE-2026-97600?

Apply the vendor's patch.

## Is CVE-2026-97600 being exploited?

There is no known exploitation of CVE-2026-97600 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97600 and fix it if it is affected.

What it is: CVE-2026-97600 is an use after free vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97600 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97600/ (Markdown: https://insights.sbomify.com/CVE-2026-97600/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97600
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97600
- OSV: https://osv.dev/vulnerability/CVE-2026-97600

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97600/
Summaries are generated and may contain mistakes; the official description above is the record.