VulnerabilityPublished 15 Aug 2026Updated 27 Oct 2026

CVE-2026-68463: Linux kernel · mmc: sdhci-esdhc-imx: use pm_runtime_resume_and_get() in suspend

Affects Linux kernelSource GCVE Database

Not known to be exploited · fixed in 7.0.0-1014.14~24.04.1 : update Linux kernel when convenient.

Data as of 28 Oct 2026, 05:11 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.0.0-1014.14~24.04.1, 7.0.0-1017.17~24.04.1, 7.0.0-1016.16~24.04.1 +11

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Patches and advisories

Affected software

Product	Affected	Fixed in
Ubuntu 26.04 LTSlinux`pkg:deb/ubuntu/linux?arch=source&distro=resolute`Other threats	Affected <7.0.0-38.38	Fixed in 7.0.0-38.38
Ubuntu 26.04 LTSlinux-aws`pkg:deb/ubuntu/linux-aws?arch=source&distro=resolute`Other threats	Affected <7.0.0-1014.14	Fixed in 7.0.0-1014.14
Ubuntu 26.04 LTSlinux-azure`pkg:deb/ubuntu/linux-azure?arch=source&distro=resolute`Other threats	Affected <7.0.0-1017.17	Fixed in 7.0.0-1017.17
Ubuntu 26.04 LTSlinux-azure-fde`pkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resolute`Other threats	Affected <7.0.0-1016.16	Fixed in 7.0.0-1016.16
Ubuntu 26.04 LTSlinux-gcp`pkg:deb/ubuntu/linux-gcp?arch=source&distro=resolute`Other threats	Affected <7.0.0-1014.14	Fixed in 7.0.0-1014.14
Ubuntu 26.04 LTSlinux-gke`pkg:deb/ubuntu/linux-gke?arch=source&distro=resolute`Other threats	Affected <7.0.0-1008.9	Fixed in 7.0.0-1008.9

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and has been released in Linux kernel versions 7.0.0-1014.14~24.04.1 and later. Users should update to these fixed versions or later to remediate the vulnerability. No additional mitigation steps are required beyond applying the official fix.

Description

CVE-2026-68463 is a vulnerability in the Linux kernel's mmc subsystem, specifically in the sdhci-esdhc-imx driver. The issue involved improper use of runtime power management functions during suspend, which could lead to a kernel panic if hardware registers were accessed after the device was unclocked. This flaw was fixed by replacing pm_runtime_get_sync() with pm_runtime_resume_and_get(), which simplifies error handling and prevents the kernel panic by properly managing the device's usage count and clock state.

Impact

If the vulnerability is triggered, the device could become unclocked while the kernel still attempts to access hardware registers, leading to a kernel panic and potential system instability or denial of service. There is no indication of privilege escalation or data compromise from this flaw.

Summary

The Linux kernel's mmc sdhci-esdhc-imx driver previously used pm_runtime_get_sync() during suspend, which did not handle errors correctly. This could result in the device being unclocked while hardware registers were still accessed, causing a kernel panic. The fix replaces pm_runtime_get_sync() with pm_runtime_resume_and_get(), which automatically drops the usage counter on failure, avoiding the need for a separate pm_runtime_put_noidle() call and preventing kernel panic by returning the error immediately.

References

Community reviews

Loading reviews…