# CVE-2025-0032: Code injection in AMD EPYC™ 9005 Series Processors

> Local administrators can load malicious CPU microcode due to improper cleanup, compromising instruction execution integrity on AMD processors.

- **Severity:** High 7.2 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A: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:** 6 Sep 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-f56j-gf6f-jg43

## What is CVE-2025-0032?

CVE-2025-0032 is a high-severity code injection vulnerability in AMD EPYC™ 9005 Series Processors, published on 6 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper cleanup in AMD CPU microcode patch loading could allow an attacker with local administrator privilege to load malicious CPU microcode, potentially resulting in loss of integrity of x86 instruction execution.

Weakness: CWE-459 (Incomplete Cleanup)

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


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

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

## Is CVE-2025-0032 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0032 is a high-severity code injection vulnerability in AMD EPYC™ 9005 Series Processors, published on 6 Sep 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-0032 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-0032/ (Markdown: https://insights.sbomify.com/CVE-2025-0032/index.md)
```

## Sources

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

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