# CVE-2025-29952: Memory corruption in AMD EPYC™ 9005 Series Processors

> An admin-privileged attacker can corrupt RMP-covered memory in AMD SEV firmware, compromising guest memory integrity on EPYC processors.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Feb 2026
- **Updated:** 10 Feb 2026
- **Also known as:** GHSA-36p6-h78p-cx2w, UBUNTU-CVE-2025-29952

## What is CVE-2025-29952?

CVE-2025-29952 is a medium-severity memory corruption vulnerability in AMD EPYC™ 9005 Series Processors, published on 10 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper Initialization within the AMD Secure Encrypted Virtualization (SEV) firmware can allow an admin privileged attacker to corrupt RMP covered memory, potentially resulting in loss of guest memory integrity

Weakness: CWE-457 (Use of Uninitialized Variable)

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


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

No fix has been published for CVE-2025-29952 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-29952 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-29952 is a medium-severity memory corruption vulnerability in AMD EPYC™ 9005 Series Processors, published on 10 Feb 2026. 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-29952 in the wild and no public exploit code.

Affected product: AMD EPYC™ 9005 Series Processors. 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-29952/ (Markdown: https://insights.sbomify.com/CVE-2025-29952/index.md)
```

## Sources

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

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