Live › vulnerability › CVE-2026-99034
Go to dashboardThe sdhci-sprd MMC driver in the Linux kernel does not undo its runtime power management setup when removed, so clocks can be disabled twice if the device is suspended. The sources describe a kernel fault found by code inspection, with no stated way for an attacker to trigger it.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the Unisoc sdhci-sprd SD/MMC host controller driver, mainly devices that unbind or remove this controller at runtime. Systems without this Unisoc hardware, or that never unbind the controller, are unlikely to be affected. The sources do not name specific kernel versions.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-99034")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.