# CVE-2026-68463: mmc: sdhci-esdhc-imx: use pm_runtime_resume_and_get() in suspend

> A flaw in the Linux kernel's SDHCI driver for i.MX platforms causes a kernel panic during suspend if power management fails, leading to denial of service.

- **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:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-68463, DEBIAN-CVE-2026-68463, GHSA-v5mv-gf7w-fvpr, UBUNTU-CVE-2026-68463

## What is CVE-2026-68463?

CVE-2026-68463 is a vulnerability in Linux, published on 15 Aug 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: sdhci-esdhc-imx: use pm_runtime_resume_and_get() in suspend

Replace pm_runtime_get_sync() with pm_runtime_resume_and_get() to
simplify error handling. pm_runtime_resume_and_get() automatically
drops the usage counter on failure, avoiding the need for a separate
pm_runtime_put_noidle() call. If it fails, the device is unclocked and
accessing hardware registers would cause a kernel panic, so return the
error immediately.

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


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

Apply the vendor's patch.

## Is CVE-2026-68463 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68463 is a vulnerability in Linux, published on 15 Aug 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-68463 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-68463/ (Markdown: https://insights.sbomify.com/CVE-2026-68463/index.md)
```

## Sources

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

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