# CVE-2026-98212: mmc: hsq: Fix use-after-free in retry work

> A use-after-free in the Linux kernel MMC host queue driver allows local attackers to cause denial of service or potentially execute code during device unbinding.

- **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-106418, BELL-CVE-2026-98212, DEBIAN-CVE-2026-98212, GHSA-9ffv-qr59-hrp8, UBUNTU-CVE-2026-98212

## What is CVE-2026-98212?

CVE-2026-98212 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: hsq: Fix use-after-free in retry work

mmc_hsq_pump_requests() queues retry_work when request_atomic() returns
-EBUSY; today sdhci-sprd is the only consumer that implements
request_atomic(). The work is embedded in a devm-allocated mmc_hsq, but
is never cancelled during driver removal. Work still pending at unbind
can therefore run after the devm allocation has been released and
dereference hsq->mmc and hsq->mrq.

Use devm_work_autocancel() to cancel and drain retry_work before the devm
allocation is released. By the time devres cleanup begins,
mmc_remove_host() has already stopped the host, so no new requests can
arm the work.

This issue was found by an in-house static analysis tool.

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


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

Apply the vendor's patch.

## Is CVE-2026-98212 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98212 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-98212 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-98212/ (Markdown: https://insights.sbomify.com/CVE-2026-98212/index.md)
```

## Sources

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

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