CVE-2026-93145clk: qcom: gdsc: tear down per-domain genpds in gdsc_unregister()
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: clk: qcom: gdsc: tear down per-domain genpds in gdsc_unregister() gdsc_unregister() removes the OF provider entry and tears down the parent/subdomain wiring, but never calls pm_genpd_remove() on the individual generic_pm_domain structures registered by gdsc_init(): void gdsc_unregister(struct gdsc_desc *desc) { struct device *dev = desc->dev; size_t num = desc->num; gdsc_pm_subdomain_remove(desc, num); of_genpd_del_provider(dev->of_node); } That leaves dangling entries on the global gpd_list. After a provider unbind/rebind cycle (deferred-probe replay during early boot, real module unload of a clk driver that owns GDSCs, or an OF-overlay tear- down) the next gdsc_init() will end up trying to re-register a name that is still in the list and pm_genpd_init() returns -EEXIST. While we are here, flip the order so the consumer-facing OF provider entry is the first thing removed -- otherwise a fresh of_genpd_get_from_provider() call racing with the teardown could attach to a domain that is mid-removal. Iterate the scs[] array and pm_genpd_remove() each registered domain after the subdomain links are torn down. The regulators stay devm- managed (devm_regulator_get_optional() in gdsc_register()), so the release happens automatically when the underlying device is unbound; just the genpd accounting needs to be undone explicitly.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Sep 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 before 418d2f0a32b2a9ceb656a88aa9139408a9b7b517; from 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 before 6333cbf7e86df9797b342ce64ae7d32ba46d8d10; from 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 before cfe16d993c578f6b17e0171a8dfd68f6fdfcfb24; 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 builds before 0f4733f5fc6b6b62750619f30c18730922a1dbdb; 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 builds before 6b9228a43963bcd4db92deb467375345132c29b3; from 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 before f60f495858379dc70e87c6898d761a9db98739ff; 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 builds before 40bd77fa2857ccfa77b885b77d44cea406f24a4c; from 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 before 86b23609d5e17a770d03037e53c6a443e742a6e6 | CNA record |
References
- https://git.kernel.org/stable/c/418d2f0a32b2a9ceb656a88aa9139408a9b7b517
- https://git.kernel.org/stable/c/6333cbf7e86df9797b342ce64ae7d32ba46d8d10
- https://git.kernel.org/stable/c/cfe16d993c578f6b17e0171a8dfd68f6fdfcfb24
- https://git.kernel.org/stable/c/0f4733f5fc6b6b62750619f30c18730922a1dbdb
- https://git.kernel.org/stable/c/6b9228a43963bcd4db92deb467375345132c29b3
- https://git.kernel.org/stable/c/f60f495858379dc70e87c6898d761a9db98739ff
- https://git.kernel.org/stable/c/40bd77fa2857ccfa77b885b77d44cea406f24a4c
- https://git.kernel.org/stable/c/86b23609d5e17a770d03037e53c6a443e742a6e6
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.