# CVE-2025-29943: Memory corruption in AMD EPYC™ 8004 Series Processors

> An admin-privileged attacker can corrupt the stack pointer in SEV-SNP guests by modifying CPU pipeline configuration, potentially leading to code execution or privilege escalation.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/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:** Yes
- **Published:** 16 Jan 2026
- **Updated:** 16 Jan 2026
- **Also known as:** BELL-CVE-2025-29943, DEBIAN-CVE-2025-29943, GHSA-4vw8-pffj-q9x7, UBUNTU-CVE-2025-29943

## What is CVE-2025-29943?

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

### Official description

Write what were condition within AMD CPUs may allow an admin-privileged attacker to modify the configuration of the CPU pipeline potentially resulting in the corruption of the stack pointer inside an SEV-SNP guest.

Weakness: CWE-123 (Write-what-where Condition)

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


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

Apply the vendor's patch.

## Is CVE-2025-29943 being exploited?

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

Public exploit code:

- PoC de CVE-2025-29943 (StackWarp): corrupcion del stack en CPUs AMD Zen bajo SEV-SNP (write-what-where). (github_poc): https://github.com/fevar54/POC_CVE-2025-29943_Write-what-where-Condition

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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