# CVE-2026-68465: mmc: sdhci-esdhc-imx: fix esdhc_change_pinstate() to allow default state restore

> A logic error in the Linux kernel's SDHCI driver prevents default pin state restoration, potentially causing denial of service for specific hardware configurations.

- **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-68465, DEBIAN-CVE-2026-68465, GHSA-6w8x-qp9f-74pq, UBUNTU-CVE-2026-68465

## What is CVE-2026-68465?

CVE-2026-68465 is a denial of service 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: fix esdhc_change_pinstate() to allow default state restore

esdhc_change_pinstate() checks for pins_100mhz and pins_200mhz at the
top of the function and returns -EINVAL if either is not defined. This
prevents the default case from ever being reached, which means devices
with a sleep pinctrl state but without high-speed pin states (100mhz/
200mhz) can never restore their default pin configuration.

Move the IS_ERR checks for pins_100mhz and pins_200mhz into their
respective switch cases.

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


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

Apply the vendor's patch.

## Is CVE-2026-68465 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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