# CVE-2025-68204: pmdomain: arm: scmi: Fix genpd leak on provider registration failure

> A memory leak in the Linux kernel SCMI power domain driver can lead to a kernel crash during debug initialization, causing denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-68204, DEBIAN-CVE-2025-68204, GHSA-c8h7-f9cr-785x, ROOT-OS-UBUNTU-2204-CVE-2025-68204, ROOT-OS-UBUNTU-2404-CVE-2025-68204, UBUNTU-CVE-2025-68204

## What is CVE-2025-68204?

CVE-2025-68204 is a memory corruption vulnerability in Linux, published on 16 Dec 2025. 

### Official description

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

pmdomain: arm: scmi: Fix genpd leak on provider registration failure

If of_genpd_add_provider_onecell() fails during probe, the previously
created generic power domains are not removed, leading to a memory leak
and potential kernel crash later in genpd_debug_add().

Add proper error handling to unwind the initialized domains before
returning from probe to ensure all resources are correctly released on
failure.

Example crash trace observed without this fix:

  | Unable to handle kernel paging request at virtual address fffffffffffffc70
  | CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.0-rc1 #405 PREEMPT
  | Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform
  | pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
  | pc : genpd_debug_add+0x2c/0x160
  | lr : genpd_debug_init+0x74/0x98
  | Call trace:
  |  genpd_debug_add+0x2c/0x160 (P)
  |  genpd_debug_init+0x74/0x98
  |  do_one_initcall+0xd0/0x2d8
  |  do_initcall_level+0xa0/0x140
  |  do_initcalls+0x60/0xa8
  |  do_basic_setup+0x28/0x40
  |  kernel_init_freeable+0xe8/0x170
  |  kernel_init+0x2c/0x140
  |  ret_from_fork+0x10/0x20

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


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

Apply the vendor's patch.

## Is CVE-2025-68204 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68204 is a memory corruption vulnerability in Linux, published on 16 Dec 2025. 
Exploitation: There is no known exploitation of CVE-2025-68204 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-68204/ (Markdown: https://insights.sbomify.com/CVE-2025-68204/index.md)
```

## Sources

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

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