CVE-2026-93145: Linux kernel · clk: qcom: gdsc: tear down per-domain genpds in gdsc_unregister()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f60f495858379dc70e87c6898d761a9db98739ff : update Linux kernel when convenient.
Data as of 26 Oct 2026, 15:59 UTC
Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f60f495858379dc70e87c6898d761a9db98739ff, cfe16d993c578f6b17e0171a8dfd68f6fdfcfb24, 6333cbf7e86df9797b342ce64ae7d32ba46d8d10 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 17 Sep 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.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in multiple Linux kernel commits as indicated by the fixedVersions. Users should update to a Linux kernel version that includes these fixes to resolve the issue. No additional mitigation actions are required beyond applying the official patch.
Description
A vulnerability in the Linux kernel's Qualcomm GDSC clock driver was fixed by ensuring proper teardown of per-domain generic power domains (genpds) in the gdsc_unregister() function. The issue involved missing calls to pm_genpd_remove() on individual generic_pm_domain structures, causing dangling entries and potential conflicts during re-registration after provider unbind/rebind cycles.
References
- git.kernel.org/stable/c/418d2f0a32b2a9ceb656a88aa9139408a9b7b517 (opens in a new tab)
- git.kernel.org/stable/c/6333cbf7e86df9797b342ce64ae7d32ba46d8d10 (opens in a new tab)
- git.kernel.org/stable/c/cfe16d993c578f6b17e0171a8dfd68f6fdfcfb24 (opens in a new tab)
- git.kernel.org/stable/c/0f4733f5fc6b6b62750619f30c18730922a1dbdb (opens in a new tab)
- git.kernel.org/stable/c/6b9228a43963bcd4db92deb467375345132c29b3 (opens in a new tab)
- git.kernel.org/stable/c/f60f495858379dc70e87c6898d761a9db98739ff (opens in a new tab)
- git.kernel.org/stable/c/40bd77fa2857ccfa77b885b77d44cea406f24a4c (opens in a new tab)
- git.kernel.org/stable/c/86b23609d5e17a770d03037e53c6a443e742a6e6 (opens in a new tab)