Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-93145clk: qcom: gdsc: tear down per-domain genpds in gdsc_unregister()

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 – < 418d2f0a32b2a9ceb656a88aa9139408a9b7b517
    • affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 – < 6333cbf7e86df9797b342ce64ae7d32ba46d8d10
    • affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 – < cfe16d993c578f6b17e0171a8dfd68f6fdfcfb24
    • affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 – < 0f4733f5fc6b6b62750619f30c18730922a1dbdb
    • affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 – < 6b9228a43963bcd4db92deb467375345132c29b3
    • affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 – < f60f495858379dc70e87c6898d761a9db98739ff
    • affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 – < 40bd77fa2857ccfa77b885b77d44cea406f24a4c
    • affected 45dd0e55317ccb27fe8eae639275c2b3a2fb52e5 – < 86b23609d5e17a770d03037e53c6a443e742a6e6
  • Linux · Linux

    • affected 4.4
    • unaffected < 4.4
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93145 badge
[![CVE-2026-93145](https://cveledger.app/badge/CVE-2026-93145.svg)](https://cveledger.app/cve/CVE-2026-93145)

Record last updated .