CVE-2026-93145
Vulnérabilité non évaluée dans Linux (Linux)
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.
Gravité et risque d'exploitation
CVE-2026-93145 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.21 %, ce qui la place devant 10.7 % des CVE référencées.
Que faire ?
- Vérifiez si Linux (versions <=6.1.*, <418d2f0a32b2a9ceb656a88aa9139408a9b7b517, <=6.12.*, 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5, 5.15.221, 5.10.270, 0, <6b9228a43963bcd4db92deb467375345132c29b3, 6.1.188, 6.18.52, <f60f495858379dc70e87c6898d761a9db98739ff, <40bd77fa2857ccfa77b885b77d44cea406f24a4c, 4.4, <=5.10.*, <=6.6.*, <0f4733f5fc6b6b62750619f30c18730922a1dbdb, 6.6.157, <6333cbf7e86df9797b342ce64ae7d32ba46d8d10, 7.2.6, <86b23609d5e17a770d03037e53c6a443e742a6e6, <=6.18.*, 7.3, 6.12.110, <=7.2.*, <=*, <=5.15.*, <cfe16d993c578f6b17e0171a8dfd68f6fdfcfb24, <4.4) est présent sur votre parc.
- Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
- À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
- Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.
Références
- 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
