CVE-2026-98210: Linux kernel · mmc: mxcmmc: cancel data work and watchdog on remove
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 01:27 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- ubuntu.com/security/CVE-2026-98210 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-98210 (opens in a new tab)
- git.kernel.org/linus/d3a421c82412344022982d5b91ba23194a0a6f29 (opens in a new tab)
- git.kernel.org/stable/c/23383e0578b58ba2dc0730cf9f7806bd66bf859a (opens in a new tab)
- git.kernel.org/stable/c/314966b490323bdcfd3162a1398b00e587e0ced4 (opens in a new tab)
- git.kernel.org/stable/c/740f595f8ad678cb4d79f13edd12851df2492bdd (opens in a new tab)
- git.kernel.org/stable/c/a1ff367e0dc961d73707add508a95df5c3509bd1 (opens in a new tab)
- git.kernel.org/stable/c/ae10838a7cdf0e54caa9d0a4f488704fd04e7f01 (opens in a new tab)
- git.kernel.org/stable/c/d3641afe6ee76d852834a34ef0669eefced32752 (opens in a new tab)
- git.kernel.org/stable/c/d3a421c82412344022982d5b91ba23194a0a6f29 (opens in a new tab)
- git.kernel.org/stable/c/e2948c4232209e87c861a680f20f1e3cf8a57fec (opens in a new tab)