CVE-2026-98213
mmc: core: Cancel SDIO IRQ work before freeing host
No known exploitation. EPSS puts it in the 11th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 682696605c7093d2800c498c04166831e5aedf87, < bae1cf4f9902b2065bd78b759c7fe6312855f05eUpgrade to: bae1cf4f9902b2065bd78b759c7fe6312855f05eAffected: ≥ 682696605c7093d2800c498c04166831e5aedf87, < 0bf3d168a2cc20b120d6b50f0a8ac5b40ff4d589Upgrade to: 0bf3d168a2cc20b120d6b50f0a8ac5b40ff4d589Affected: ≥ 682696605c7093d2800c498c04166831e5aedf87, < 1d6e7315ee1c992b4ca42c9b11c5ed0e925a00e0Upgrade to: 1d6e7315ee1c992b4ca42c9b11c5ed0e925a00e0Affected: ≥ 682696605c7093d2800c498c04166831e5aedf87, < 4553b5004eca9c9eae29a421f1a9c4d5db2c9114Upgrade to: 4553b5004eca9c9eae29a421f1a9c4d5db2c9114 + 2 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: 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.
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.
- 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 11th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/bae1cf4f9902b2065bd78b759c7fe6312855f05e
- git.kernel.org/stable/c/0bf3d168a2cc20b120d6b50f0a8ac5b40ff4d589
- git.kernel.org/stable/c/1d6e7315ee1c992b4ca42c9b11c5ed0e925a00e0
And 3 more references. See all after sign-in
In the news
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.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI