# CVE-2026-99034: mmc: sdhci-sprd: disable runtime PM on remove


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** AZL-110897, BELL-CVE-2026-99034, DEBIAN-CVE-2026-99034, GHSA-gp3v-p42p-6pmv, UBUNTU-CVE-2026-99034

## What is CVE-2026-99034?

CVE-2026-99034 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

mmc: sdhci-sprd: disable runtime PM on remove

sdhci_sprd_probe() enables runtime PM, while sdhci_sprd_remove() does
not perform the corresponding runtime PM cleanup.

The probe failure path disables runtime PM before disabling the clocks,
but the normal remove path directly disables clocks that are also
managed by the runtime PM callbacks. If the device is runtime
suspended, those clocks may already be disabled.

Resume the device before removal, disable runtime PM and drop the
temporary runtime PM reference before disabling the clocks.

This issue was found by manual code inspection.

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


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

Upgrade to a fixed version.

## Is CVE-2026-99034 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99034 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99034 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-99034/ (Markdown: https://insights.sbomify.com/CVE-2026-99034/index.md)
```

## Sources

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

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