Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Fixed version: Linux Linux 03d5e4776e8b71c2468c5c3c48b39202c87a8796, 0969c9688389f2e0f65b1a924b0dd6625a3bb776, 11bc2cbb14f450eaa47cce9eb086f948ef8f4bcd; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 03d5e4776e8b71c2468c5c3c48b39202c87a8796, 0969c9688389f2e0f65b1a924b0dd6625a3bb776, 11bc2cbb14f450eaa47cce9eb086f948ef8f4bcd; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

—No exploit Fix available
Published
Oct 14, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-98426

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.6affected
    • 99074fc1e67b374b5c72406a23ac01fed806d634 and later · before 11bc2cbb14f450eaa47cce9eb086f948ef8f4bcdaffected · git
    • 99074fc1e67b374b5c72406a23ac01fed806d634 and later · before 1a60cb2292194cc9eafae7ca8a8a72d37ae78d97affected · git
    • 99074fc1e67b374b5c72406a23ac01fed806d634 and later · before fcac5813f324cd07dfd36b4adf624fc70f7587d6affected · git
    • 99074fc1e67b374b5c72406a23ac01fed806d634 and later · before 2761b21cb896b1da8dd46cee5084c9032b2d7098affected · git
    • 99074fc1e67b374b5c72406a23ac01fed806d634 and later · before 5fd4cc87e6cc0839aac89c24ebe39ce262fe088faffected · git
    • 99074fc1e67b374b5c72406a23ac01fed806d634 and later · before 0969c9688389f2e0f65b1a924b0dd6625a3bb776affected · git
    • 99074fc1e67b374b5c72406a23ac01fed806d634 and later · before 03d5e4776e8b71c2468c5c3c48b39202c87a8796affected · git
    • 99074fc1e67b374b5c72406a23ac01fed806d634 and later · before a3d722190cdef18da4878b5efc27c3c386dda248affected · git
    • before 4.6not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.190-16.1.190-1
Debian:12linux-6.12before 6.12.113-1~deb12u16.12.113-1~deb12u1
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.8-17.2.8-1
openSUSE:Tumbleweedkernel-sourcebefore 7.2.11-1.17.2.11-1.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-98424Oct 14, 2026 · wifi: cfg80211: undo netns switch if renaming the wiphy fails
    0Monitor
  • ← EarlierCVE-2026-98425Oct 14, 2026 · wifi: mac80211: don't warn when an IBSS has no channel to scan
    0Monitor
  • Later →CVE-2026-98427Oct 14, 2026 · net/sched: codel: bound the dropping loop per dequeue call
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux03d5e4776e8b71c2468c5c3c48b39202c87a8796Vendor (CNA)
Linux Linux0969c9688389f2e0f65b1a924b0dd6625a3bb776Vendor (CNA)
Linux Linux11bc2cbb14f450eaa47cce9eb086f948ef8f4bcdVendor (CNA)
Linux Linux1a60cb2292194cc9eafae7ca8a8a72d37ae78d97Vendor (CNA)
Linux Linux2761b21cb896b1da8dd46cee5084c9032b2d7098Vendor (CNA)
Linux Linux5fd4cc87e6cc0839aac89c24ebe39ce262fe088fVendor (CNA)
Linux Linuxa3d722190cdef18da4878b5efc27c3c386dda248Vendor (CNA)
Linux Linuxfcac5813f324cd07dfd36b4adf624fc70f7587d6Vendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.06.6.159.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)
debian:linux7.2.8-1 · Debian:14Package registry (OSV)
debian:linux-6.126.12.113-1~deb12u1 · Debian:12Package registry (OSV)
opensuse:kernel-source7.2.11-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 9, 2026+26 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Exploit maturity— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records