Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98426wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path mwifiex_pcie_request_irq() registers each MSI-X vector with a per-index dev_id (&card->msix_ctx[i]). On a request_irq() failure the cleanup loop "for (j = 0; j < i; j++)" frees msix_entries[j].vector but passes the failed index's &card->msix_ctx[i] as the dev_id. free_irq() matches on (irq, dev_id), so it fails to find the action registered with &card->msix_ctx[j]: the already-requested IRQ j is not freed (leaked) and free_irq() warns about freeing a non-existent IRQ. Use &card->msix_ctx[j].

Timeline

  1. ID reserved

    By Linux

  2. · 19 days later

    Published

  3. · 5 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 99074fc1e67b374b5c72406a23ac01fed806d634 – < 11bc2cbb14f450eaa47cce9eb086f948ef8f4bcd
    • affected 99074fc1e67b374b5c72406a23ac01fed806d634 – < 1a60cb2292194cc9eafae7ca8a8a72d37ae78d97
    • affected 99074fc1e67b374b5c72406a23ac01fed806d634 – < fcac5813f324cd07dfd36b4adf624fc70f7587d6
    • affected 99074fc1e67b374b5c72406a23ac01fed806d634 – < 2761b21cb896b1da8dd46cee5084c9032b2d7098
    • affected 99074fc1e67b374b5c72406a23ac01fed806d634 – < 5fd4cc87e6cc0839aac89c24ebe39ce262fe088f
    • affected 99074fc1e67b374b5c72406a23ac01fed806d634 – < 0969c9688389f2e0f65b1a924b0dd6625a3bb776
    • affected 99074fc1e67b374b5c72406a23ac01fed806d634 – < 03d5e4776e8b71c2468c5c3c48b39202c87a8796
    • affected 99074fc1e67b374b5c72406a23ac01fed806d634 – < a3d722190cdef18da4878b5efc27c3c386dda248
  • Linux · Linux

    • affected 4.6
    • unaffected < 4.6
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98426 badge
[![CVE-2026-98426](https://cveledger.app/badge/CVE-2026-98426.svg)](https://cveledger.app/cve/CVE-2026-98426)

Record last updated .