clk: qcom: gdsc: tear down per-domain genpds in gdsc_unregister()
Summary
| CVE | CVE-2026-93145 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-17 17:18:09 UTC |
| Updated | 2026-09-17 17:18:09 UTC |
| Description | 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 418d2f0a32b2a9ceb656a88aa9139408a9b7b517 git |
Not specified |
| CNA |
Linux |
Linux |
affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 6333cbf7e86df9797b342ce64ae7d32ba46d8d10 git |
Not specified |
| CNA |
Linux |
Linux |
affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 cfe16d993c578f6b17e0171a8dfd68f6fdfcfb24 git |
Not specified |
| CNA |
Linux |
Linux |
affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 0f4733f5fc6b6b62750619f30c18730922a1dbdb git |
Not specified |
| CNA |
Linux |
Linux |
affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 6b9228a43963bcd4db92deb467375345132c29b3 git |
Not specified |
| CNA |
Linux |
Linux |
affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 f60f495858379dc70e87c6898d761a9db98739ff git |
Not specified |
| CNA |
Linux |
Linux |
affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 40bd77fa2857ccfa77b885b77d44cea406f24a4c git |
Not specified |
| CNA |
Linux |
Linux |
affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 86b23609d5e17a770d03037e53c6a443e742a6e6 git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.4 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 4.4 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.10.270 5.10.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.221 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.188 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.157 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.110 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.52 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.6 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/40bd77fa2857ccfa77b885b77d44cea406f24a4c |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/6333cbf7e86df9797b342ce64ae7d32ba46d8d10 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/cfe16d993c578f6b17e0171a8dfd68f6fdfcfb24 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/6b9228a43963bcd4db92deb467375345132c29b3 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/86b23609d5e17a770d03037e53c6a443e742a6e6 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/418d2f0a32b2a9ceb656a88aa9139408a9b7b517 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/0f4733f5fc6b6b62750619f30c18730922a1dbdb |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/f60f495858379dc70e87c6898d761a9db98739ff |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.