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

> A malicious guest can write to host memory due to improper bound checks in AMD CPU microcode, compromising host integrity.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Feb 2026
- **Updated:** 11 Feb 2026
- **Also known as:** DEBIAN-CVE-2025-52534, GHSA-633w-44jw-wrp4, UBUNTU-CVE-2025-52534

## What is CVE-2025-52534?

CVE-2025-52534 is a medium-severity memory corruption vulnerability in AMD EPYC™ 9005 Series Processors, published on 10 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper bound check within AMD CPU microcode can allow a malicious guest to write to host memory, potentially resulting in loss of integrity.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

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


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

Apply the vendor's patch.

## Is CVE-2025-52534 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52534 is a medium-severity memory corruption vulnerability in AMD EPYC™ 9005 Series Processors, published on 10 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52534 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-52534/ (Markdown: https://insights.sbomify.com/CVE-2025-52534/index.md)
```

## Sources

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

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