# CVE-2025-29939: Privilege escalation in AMD EPYC™ 7003 Series Processors

> A privileged attacker can compromise guest memory confidentiality and integrity in AMD SEV-SNP environments by exploiting improper access controls during initialization.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/VA:N/SC:H/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-cfmm-jqwq-9m7g, UBUNTU-CVE-2025-29939

## What is CVE-2025-29939?

CVE-2025-29939 is a medium-severity vulnerability in AMD EPYC™ 7003 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 access control in secure encrypted virtualization (SEV) could allow a privileged attacker to write to the reverse map page (RMP) during secure nested paging (SNP) initialization, potentially resulting in a loss of guest memory confidentiality and integrity.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-29939 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-29939 is a medium-severity vulnerability in AMD EPYC™ 7003 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-29939 in the wild and no public exploit code.

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

## Sources

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

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