CVE-2026-98496
Last modified
CVE-2026-98496 is a vulnerability of currently unknown severity. In 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.
Description
In 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 Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 23290c7bc190def4e1ca61610992d9b7c32e33f3, < aca91d8fa0ecbc990ebf9a688c684dda78a43c00; >= 23290c7bc190def4e1ca61610992d9b7c32e33f3, < da9d42531f3a6dfea2e9c775b62a46185dbf280a; >= 23290c7bc190def4e1ca61610992d9b7c32e33f3, < 4bdee8060d1e4581624e68fbd369b1afb14df4bc |
| Linux | Linux | 6.15 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98496?
How severe is CVE-2026-98496?
How do I fix CVE-2026-98496?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98490In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-98491In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-98492In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98493In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98494In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98495In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98497In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-98498In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98499In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-98500In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98501In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-98502In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98496?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
