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

CVE-2026-98213: mmc: core: Cancel SDIO IRQ work before freeing host

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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 0bf3d168a2cc20b120d6b50f0a8ac5b40ff4d589, 1d6e7315ee1c992b4ca42c9b11c5ed0e925a00e0, 2a863458828ade0671c2bc2e469bbd7f2340eb03; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.

Low priority for now. Upgrade to Linux Linux 0bf3d168a2cc20b120d6b50f0a8ac5b40ff4d589, 1d6e7315ee1c992b4ca42c9b11c5ed0e925a00e0, 2a863458828ade0671c2bc2e469bbd7f2340eb03; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.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: mmc: core: Cancel SDIO IRQ work before freeing host A host controller that uses sdio_signal_irq() schedules host->sdio_irq_work from its interrupt handler. That work is only cancelled on the suspend path (mmc_sdio_suspend()), not on the remove/free path, so a worker armed just before the controller freed its IRQ can run after mmc_host_classdev_release() has freed the host and dereference it through container_of(). Cancel host->sdio_irq_work in mmc_free_host(), like the existing host->detect drain added by commit 1036f69e2513 ("mmc: core: Cancel delayed work before releasing host"). This issue was found by an in-house static analysis tool.

—No exploit Fix available
Published
Oct 6, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 11th 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-98213

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.13affected
    • 682696605c7093d2800c498c04166831e5aedf87 and later · before bae1cf4f9902b2065bd78b759c7fe6312855f05eaffected · git
    • 682696605c7093d2800c498c04166831e5aedf87 and later · before 0bf3d168a2cc20b120d6b50f0a8ac5b40ff4d589affected · git
    • 682696605c7093d2800c498c04166831e5aedf87 and later · before 1d6e7315ee1c992b4ca42c9b11c5ed0e925a00e0affected · git
    • 682696605c7093d2800c498c04166831e5aedf87 and later · before 4553b5004eca9c9eae29a421f1a9c4d5db2c9114affected · git
    • 682696605c7093d2800c498c04166831e5aedf87 and later · before 2a863458828ade0671c2bc2e469bbd7f2340eb03affected · git
    • 682696605c7093d2800c498c04166831e5aedf87 and later · before 6feadbecdae60a6324c967f3b1493741083793a3affected · git
    • before 4.13not affected · semver
    • 6.1.189 and later · up to and including 6.1.*not affected · semver
    • 6.6.158 and later · up to and including 6.6.*not 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

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-98211Oct 6, 2026 · mmc: mmci: Fix use-after-free in busy-timeout work
    0Monitor
  • ← EarlierCVE-2026-98212Oct 6, 2026 · mmc: hsq: Fix use-after-free in retry work
    0Monitor
  • Later →CVE-2026-98214Oct 6, 2026 · selinux: recheck intermediate backing files on mprotect()
    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 Linux0bf3d168a2cc20b120d6b50f0a8ac5b40ff4d589Vendor (CNA)
Linux Linux1d6e7315ee1c992b4ca42c9b11c5ed0e925a00e0Vendor (CNA)
Linux Linux2a863458828ade0671c2bc2e469bbd7f2340eb03Vendor (CNA)
Linux Linux4553b5004eca9c9eae29a421f1a9c4d5db2c9114Vendor (CNA)
Linux Linux6feadbecdae60a6324c967f3b1493741083793a3Vendor (CNA)
Linux Linuxbae1cf4f9902b2065bd78b759c7fe6312855f05eVendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.06.6.158.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)

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+34 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).

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 (5 more)

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

All records