{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40145 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40145 is a memory corruption vulnerability in Linux, published on 12 Nov 2025. 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-2025-40145 and fix it if it is affected.\n\nWhat it is: CVE-2025-40145 is a memory corruption vulnerability in Linux, published on 12 Nov 2025. 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-2025-40145 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-2025-40145/ (Markdown: https://insights.sbomify.com/CVE-2025-40145/index.md)","id":"CVE-2025-40145","markdown":"https://insights.sbomify.com/CVE-2025-40145/index.md","name":"CVE-2025-40145","record":{"aliases":["BELL-CVE-2025-40145","DEBIAN-CVE-2025-40145","GHSA-938p-f83v-2x6c","UBUNTU-CVE-2025-40145"],"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 double cleanup error in the Linux kernel PCI power control driver can cause a system crash or denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nPCI/pwrctrl: Fix double cleanup on devm_add_action_or_reset() failure\n\nWhen devm_add_action_or_reset() fails, it calls the passed cleanup\nfunction.  Hence the caller must not repeat that cleanup.\n\nReplace the \"goto err_regulator_free\" by the actual freeing, as there\nwill never be a need again for a second user of this label.","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":"PCI/pwrctrl: Fix double cleanup on devm_add_action_or_reset() failure","id":"CVE-2025-40145","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"blk-mq: fix potential deadlock while nr_requests grown","id":"CVE-2025-40146"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2025-40144"},"products":["Linux"],"published":"2025-11-12","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-05-11","vendors":["Linux"]},"summary":"A double cleanup error in the Linux kernel PCI power control driver can cause a system crash or denial of service.","url":"https://insights.sbomify.com/CVE-2025-40145/"}