# CVE-2025-54509: Missing authorization in AMD EPYC™ 8004 Series Processors

> A privileged attacker can exploit improper IOMMU access controls to cause non-coherent accesses by the AMD Secure Processor, compromising data integrity.

- **Severity:** Medium 4.0 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/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:** 9 Jun 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-gchr-732q-fg34

## What is CVE-2025-54509?

CVE-2025-54509 is a medium-severity missing authorization vulnerability in AMD EPYC™ 8004 Series Processors, published on 9 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper access control for register interface in the Input-Output Memory Management Unit (IOMMU) could allow a privileged attacker to cause non-coherent accesses by the AMD Secure Processor (ASP), potentially resulting in loss of integrity.

Weakness: CWE-1262 (Improper Access Control for Register Interface)

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


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

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

## Is CVE-2025-54509 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54509 is a medium-severity missing authorization vulnerability in AMD EPYC™ 8004 Series Processors, published on 9 Jun 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-54509 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-54509/ (Markdown: https://insights.sbomify.com/CVE-2025-54509/index.md)
```

## Sources

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

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