GHSA-QQ9M-VQCJ-573M
Vulnerability from github – Published: 2026-10-18 18:31 – Updated: 2026-10-18 18:31In the Linux kernel, the following vulnerability has been resolved:
net: airoha: npu: cancel wdt_work after releasing the WDT IRQ
airoha_npu_remove() calls cancel_work_sync() on each core's wdt_work, but the watchdog IRQ that queues it is requested with devm_request_irq() and is freed only after .remove() returns. airoha_npu_wdt_handler() can therefore schedule_work() again once the cancel has returned. struct airoha_npu, which contains the work, is devm_kzalloc()'d and is freed in that same unwind, so the late work dereferences freed memory.
Register the work with devm_work_autocancel() before devm_request_irq() and drop .remove(). Devres runs in reverse order, so the IRQ is freed before cancel_work_sync(), including when probe fails. A cancel left in .remove() cannot get that order. Initializing the work first also stops a pending watchdog interrupt from queuing an uninitialized work item. Probe currently calls INIT_WORK() only after devm_request_irq().
This issue was identified during our ongoing static-analysis research while reviewing kernel code.
{
"affected": [],
"aliases": [
"CVE-2026-98496"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:00Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: airoha: npu: cancel wdt_work after releasing the WDT IRQ\n\nairoha_npu_remove() calls cancel_work_sync() on each core\u0027s wdt_work,\nbut the watchdog IRQ that queues it is requested with devm_request_irq()\nand is freed only after .remove() returns. airoha_npu_wdt_handler() can\ntherefore schedule_work() again once the cancel has returned. struct\nairoha_npu, which contains the work, is devm_kzalloc()\u0027d and is freed in\nthat same unwind, so the late work dereferences freed memory.\n\nRegister the work with devm_work_autocancel() before devm_request_irq()\nand drop .remove(). Devres runs in reverse order, so the IRQ is freed\nbefore cancel_work_sync(), including when probe fails. A cancel left in\n.remove() cannot get that order. Initializing the work first also stops\na pending watchdog interrupt from queuing an uninitialized work item.\nProbe currently calls INIT_WORK() only after devm_request_irq().\n\nThis issue was identified during our ongoing static-analysis research\nwhile reviewing kernel code.",
"id": "GHSA-qq9m-vqcj-573m",
"modified": "2026-10-18T18:31:51Z",
"published": "2026-10-18T18:31:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98496"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4bdee8060d1e4581624e68fbd369b1afb14df4bc"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/aca91d8fa0ecbc990ebf9a688c684dda78a43c00"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/da9d42531f3a6dfea2e9c775b62a46185dbf280a"
}
],
"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.