CVE-2026-93145

CVE CVE-2026-93145EUVD EUVD-2026-82253Published 2026-09-17T16:11:43.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux patch: 6.1.188; 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 <6b9228a43963bcd4db92deb467375345132c29b3; patch: 5.15.221; patch: 6.12.110; patch: 5.10.270; 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 <f60f495858379dc70e87c6898d761a9db98739ff; patch: 0; 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 <0f4733f5fc6b6b62750619f30c18730922a1dbdb; 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 <86b23609d5e17a770d03037e53c6a443e742a6e6; 4.4; patch: 7.2.6; patch: 6.6.157; patch: 6.18.52; 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 <6333cbf7e86df9797b342ce64ae7d32ba46d8d10; 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 <418d2f0a32b2a9ceb656a88aa9139408a9b7b517; patch: 7.3-rc1; 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 <40bd77fa2857ccfa77b885b77d44cea406f24a4c; 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 <cfe16d993c578f6b17e0171a8dfd68f6fdfcfb24

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.