Quick answers
- Is CVE-2026-99034 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-99034 being exploited in the wild.
- How severe is CVE-2026-99034?
- Informational severity, published 23 October 2026.
- Which products and versions are affected?
- Unknown Linux kernel versions with fb8bd90f83c4 applied, prior to fix commit e1c6c10a6a70a69e29b04fcc1ebe4b9bcbc7a49a.
- Is there a fix for CVE-2026-99034?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-99034 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-99034?
- Check whether you run Unknown Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The sdhci_sprd_remove() function did not perform runtime PM cleanup that was enabled in sdhci_sprd_probe(), causing a clock management mismatch when the device was runtime suspended. The fix resumes the device, disables runtime PM, and drops the PM reference before disabling clocks, preventing attempts to disable already-suspended clock resources.
Affected products
- <UNKNOWN> Linux kernel versions with fb8bd90f83c4 applied, prior to fix commit e1c6c10a6a70a69e29b04fcc1ebe4b9bcbc7a49a
Timeline
- 2026-10-23: disclosed
- 2026-09-16: other: Patch authored