CVE Tools

CVE-2026-98426

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

No known exploitation. EPSS puts it in the 12th percentile. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • LinuxAffected: ≥ 99074fc1e67b374b5c72406a23ac01fed806d634, < 11bc2cbb14f450eaa47cce9eb086f948ef8f4bcdUpgrade to: 11bc2cbb14f450eaa47cce9eb086f948ef8f4bcdAffected: ≥ 99074fc1e67b374b5c72406a23ac01fed806d634, < 1a60cb2292194cc9eafae7ca8a8a72d37ae78d97Upgrade to: 1a60cb2292194cc9eafae7ca8a8a72d37ae78d97Affected: ≥ 99074fc1e67b374b5c72406a23ac01fed806d634, < fcac5813f324cd07dfd36b4adf624fc70f7587d6Upgrade to: fcac5813f324cd07dfd36b4adf624fc70f7587d6Affected: ≥ 99074fc1e67b374b5c72406a23ac01fed806d634, < 2761b21cb896b1da8dd46cee5084c9032b2d7098Upgrade to: 2761b21cb896b1da8dd46cee5084c9032b2d7098 + 4 more branchesStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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].

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS12th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.2% chance of exploitation activity in the next 30 days, which ranks it in the 12th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

4 events over 8 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Record updated
  3. Publishedrecord updated

Affected products

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Linux, not every advisory.