{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-93145 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-93145 is an use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-93145 and fix it if it is affected.\n\nWhat it is: CVE-2026-93145 is an use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-93145 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-93145/ (Markdown: https://insights.sbomify.com/CVE-2026-93145/index.md)","id":"CVE-2026-93145","markdown":"https://insights.sbomify.com/CVE-2026-93145/index.md","name":"CVE-2026-93145","record":{"aliases":["AZL-101960","BELL-CVE-2026-93145","DEBIAN-CVE-2026-93145","GHSA-qp94-vr9v-vp96","UBUNTU-CVE-2026-93145"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A use-after-free vulnerability in the Linux kernel's Qualcomm GDSC driver allows local attackers to cause a denial of service via module unloading or rebind cycles.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nclk: qcom: gdsc: tear down per-domain genpds in gdsc_unregister()\n\ngdsc_unregister() removes the OF provider entry and tears down the\nparent/subdomain wiring, but never calls pm_genpd_remove() on the\nindividual generic_pm_domain structures registered by gdsc_init():\n\n\tvoid gdsc_unregister(struct gdsc_desc *desc)\n\t{\n\t\tstruct device *dev = desc-\u003edev;\n\t\tsize_t num = desc-\u003enum;\n\n\t\tgdsc_pm_subdomain_remove(desc, num);\n\t\tof_genpd_del_provider(dev-\u003eof_node);\n\t}\n\nThat leaves dangling entries on the global gpd_list. After a provider\nunbind/rebind cycle (deferred-probe replay during early boot, real\nmodule unload of a clk driver that owns GDSCs, or an OF-overlay tear-\ndown) the next gdsc_init() will end up trying to re-register a name\nthat is still in the list and pm_genpd_init() returns -EEXIST.\n\nWhile we are here, flip the order so the consumer-facing OF provider\nentry is the first thing removed -- otherwise a fresh\nof_genpd_get_from_provider() call racing with the teardown could\nattach to a domain that is mid-removal.\n\nIterate the scs[] array and pm_genpd_remove() each registered domain\nafter the subdomain links are torn down. The regulators stay devm-\nmanaged (devm_regulator_get_optional() in gdsc_register()), so the\nrelease happens automatically when the underlying device is unbound;\njust the genpd accounting needs to be undone explicitly.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"clk: qcom: gdsc: tear down per-domain genpds in gdsc_unregister()","id":"CVE-2026-93145","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"time/namespace: Validate nanosecond field in proc_timens_set_offset()","id":"CVE-2026-93146"},"packages":[],"prev":{"headline":"bpf: Reject writes through untrusted BTF pointers","id":"CVE-2026-93144"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A use-after-free vulnerability in the Linux kernel's Qualcomm GDSC driver allows local attackers to cause a denial of service via module unloading or rebind cycles.","url":"https://insights.sbomify.com/CVE-2026-93145/"}