GHSA-RQ9H-JCG5-92GP
Vulnerability from github – Published: 2026-09-25 12:31 – Updated: 2026-09-25 12:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-97600"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-25T11:17:11Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nieee802154: cc2520: fix FIFOP work use-after-free\n\nThe FIFOP interrupt handler queues cc2520_fifop_irqwork. On removal,\ncc2520_remove() only flushes the work. The devm-managed FIFOP IRQ\nremains active until after -\u003eremove() returns and can queue the work\nagain after that flush, allowing it to run after the private data is\nreleased.\n\nDisable the work with disable_work_sync() instead of flushing it, so\nthe handler can no longer queue it once removal begins. Destroy the\nbuffer mutex last, since the worker and the stop callback invoked\nthrough ieee802154_unregister_hw() both take it.\n\nFound by an in-house static analysis tool.",
"id": "GHSA-rq9h-jcg5-92gp",
"modified": "2026-09-25T12:31:26Z",
"published": "2026-09-25T12:31:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-97600"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/56a9919d8494fb118eebf167bef0622528fbf2e7"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/890a80d516a1447db5c21bf92841a82914ea897d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c68fd52c73b676aee67020011e98fea125a978f4"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ff5891b266a7fc6a062710836be84f1cc19338b5"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.