CVE-2026-98210
mmc: mxcmmc: cancel data work and watchdog on remove
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ f6ad0a481342223b2e7ae9f55b154e14f1391ada, < 740f595f8ad678cb4d79f13edd12851df2492bddUpgrade to: 740f595f8ad678cb4d79f13edd12851df2492bddAffected: ≥ f6ad0a481342223b2e7ae9f55b154e14f1391ada, < d3641afe6ee76d852834a34ef0669eefced32752Upgrade to: d3641afe6ee76d852834a34ef0669eefced32752Affected: ≥ f6ad0a481342223b2e7ae9f55b154e14f1391ada, < 314966b490323bdcfd3162a1398b00e587e0ced4Upgrade to: 314966b490323bdcfd3162a1398b00e587e0ced4Affected: ≥ f6ad0a481342223b2e7ae9f55b154e14f1391ada, < ae10838a7cdf0e54caa9d0a4f488704fd04e7f01Upgrade to: ae10838a7cdf0e54caa9d0a4f488704fd04e7f01 + 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: mmc: mxcmmc: cancel data work and watchdog on remove mxcmci_remove() frees the host through the devm tail, but neither it nor mmc_remove_host() drains the driver's own asynchronous state. host->watchdog, a 10 s timer armed on the DMA path in mxcmci_setup_data(), is deleted only by the DMA- and IRQ-complete paths, which the remove path does not explicitly drain; it can therefore fire after the host is freed and dereference it in mxcmci_watchdog(). host->datawork, armed from the IRQ handler on the PIO path, is not cancelled by the remove path either. Free the devm-registered IRQ, then cancel datawork and delete the watchdog in mxcmci_remove(), before dma_release_channel(). Freeing the IRQ first keeps a trailing handler from re-arming datawork between the cancel and the host free. Both callbacks are non-self-rearming. 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 7th 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/23383e0578b58ba2dc0730cf9f7806bd66bf859a
- git.kernel.org/stable/c/314966b490323bdcfd3162a1398b00e587e0ced4
- git.kernel.org/stable/c/740f595f8ad678cb4d79f13edd12851df2492bdd
And 5 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