ieee802154: cc2520: fix FIFOP work use-after-free (CVE-2026-97600) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-97600

ieee802154: cc2520: fix FIFOP work use-after-free

Answer in brief

CVE-2026-97600 records a Unknown severity vulnerability in ieee802154: cc2520: fix FIFOP work use-after-free. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 25, 2026Updated Sep 25, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 25, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=0da6bc8cc3417a5e452efb886ff2c61e72b743d6 <56a9919d8494fb118eebf167bef0622528fbf2e7 \|\| >=0da6bc8cc3417a5e452efb886ff2c61e72b743d6 <c68fd52c73b676aee67020011e98fea125a978f4 \|\| >=0da6bc8cc3417a5e452efb886ff2c61e72b743d6 <890a80d516a1447db5c21bf92841a82914ea897d \|\| >=0da6bc8cc3417a5e452efb886ff2c61e72b743d6 <ff5891b266a7fc6a062710836be84f1cc19338b5	56a9919d8494fb118eebf167bef0622528fbf2e7, c68fd52c73b676aee67020011e98fea125a978f4, 890a80d516a1447db5c21bf92841a82914ea897d, ff5891b266a7fc6a062710836be84f1cc19338b5
Linux/Linuxgeneric	3.17	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 56a9919d8494fb118eebf167bef0622528fbf2e7 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.