# CVE-2025-54514: Other in AMD EPYC™ 9005 Series Processors

> A malicious local attacker with high privileges can compromise integrity by exploiting improper isolation of shared resources in AMD processors.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Feb 2026
- **Updated:** 11 Feb 2026
- **Also known as:** DEBIAN-CVE-2025-54514, GHSA-57cm-p6rm-7r9v, UBUNTU-CVE-2025-54514

## What is CVE-2025-54514?

CVE-2025-54514 is a medium-severity 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 isolation of shared resources on a system on a chip by a malicious local attacker with high privileges could potentially lead to a partial loss of integrity.

Weakness: CWE-1189 (Improper Isolation of Shared Resources on System-on-a-Chip (SoC))

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


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

Apply the vendor's patch.

## Is CVE-2025-54514 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54514 is a medium-severity 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-54514 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-54514/ (Markdown: https://insights.sbomify.com/CVE-2025-54514/index.md)
```

## Sources

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

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