# CVE-2025-40145: PCI/pwrctrl: Fix double cleanup on devm_add_action_or_reset() failure

> A double cleanup error in the Linux kernel PCI power control driver can cause a system crash or denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Nov 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-40145, DEBIAN-CVE-2025-40145, GHSA-938p-f83v-2x6c, UBUNTU-CVE-2025-40145

## What is CVE-2025-40145?

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.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

PCI/pwrctrl: Fix double cleanup on devm_add_action_or_reset() failure

When devm_add_action_or_reset() fails, it calls the passed cleanup
function.  Hence the caller must not repeat that cleanup.

Replace the "goto err_regulator_free" by the actual freeing, as there
will never be a need again for a second user of this label.

## Which versions are affected by CVE-2025-40145?


## How do I fix CVE-2025-40145?

Apply the vendor's patch.

## Is CVE-2025-40145 being exploited?

There is no known exploitation of CVE-2025-40145 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40145 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2025-40145 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-40145/ (Markdown: https://insights.sbomify.com/CVE-2025-40145/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-40145
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-40145
- OSV: https://osv.dev/vulnerability/CVE-2025-40145

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-40145/
Summaries are generated and may contain mistakes; the official description above is the record.