IRQ leakage via mismatched cleanup context
Published Oct 14, 2026 · Updated Oct 14, 2026
IRQ leakage in Linux's mwifiex PCIe driver allows attackers to leave handlers registered via failed MSI-X initialization. The mwifiex_pcie_request_irq() cleanup loop passes the failed vector's context to free_irq() instead of each registered vector's context, preventing handler removal and generating warnings. The path requires affected hardware using MSI-X and a request_irq() failure after an earlier registration succeeds; no attacker-controlled trigger or resulting crash is documented.
Summary
What happened
IRQ leakage in Linux's mwifiex PCIe driver allows attackers to leave handlers registered via failed MSI-X initialization. The mwifiex_pcie_request_irq() cleanup loop passes the failed vector's context to free_irq() instead of each registered vector's context, preventing handler removal and generating warnings. The path requires affected hardware using MSI-X and a request_irq() failure after an earlier registration succeeds; no attacker-controlled trigger or resulting crash is documented.
The record
- CVE
- CVE-2026-98426
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.6
- Affected versionversion=99074fc1e67b374b5c72406a23ac01fed806d634 <03d5e4776e8b71c2468c5c3c48b39202c87a8796
- Affected versionversion=99074fc1e67b374b5c72406a23ac01fed806d634 <0969c9688389f2e0f65b1a924b0dd6625a3bb776
- Affected versionversion=99074fc1e67b374b5c72406a23ac01fed806d634 <11bc2cbb14f450eaa47cce9eb086f948ef8f4bcd
- Affected versionversion=99074fc1e67b374b5c72406a23ac01fed806d634 <1a60cb2292194cc9eafae7ca8a8a72d37ae78d97
- Affected versionversion=99074fc1e67b374b5c72406a23ac01fed806d634 <2761b21cb896b1da8dd46cee5084c9032b2d7098
- Affected versionversion=99074fc1e67b374b5c72406a23ac01fed806d634 <5fd4cc87e6cc0839aac89c24ebe39ce262fe088f
- Affected versionversion=99074fc1e67b374b5c72406a23ac01fed806d634 <a3d722190cdef18da4878b5efc27c3c386dda248
- Affected versionversion=99074fc1e67b374b5c72406a23ac01fed806d634 <fcac5813f324cd07dfd36b4adf624fc70f7587d6
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started