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

> A use-after-free in the Linux kernel MMC core allows local attackers to cause a denial of service or potentially execute code by triggering a race condition during host removal.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106110, BELL-CVE-2026-98213, DEBIAN-CVE-2026-98213, GHSA-q4vm-jrgj-pmvw, UBUNTU-CVE-2026-98213

## What is CVE-2026-98213?

CVE-2026-98213 is an use after free vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-98213?


## How do I fix CVE-2026-98213?

Apply the vendor's patch.

## Is CVE-2026-98213 being exploited?

There is no known exploitation of CVE-2026-98213 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98213 and fix it if it is affected.

What it is: CVE-2026-98213 is an use after free vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98213 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98213/ (Markdown: https://insights.sbomify.com/CVE-2026-98213/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98213
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98213
- OSV: https://osv.dev/vulnerability/CVE-2026-98213

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98213/
Summaries are generated and may contain mistakes; the official description above is the record.