# CVE-2025-48517: Missing authorization in AMD EPYC™ 9005 Series Processors

> A privileged user with a malicious hypervisor can create a SEV-ES guest with restricted ASIDs, leading to partial loss of confidentiality.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/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:** 10 Feb 2026
- **Updated:** 10 Feb 2026
- **Also known as:** DEBIAN-CVE-2025-48517, GHSA-jhpq-g463-wv89, UBUNTU-CVE-2025-48517

## What is CVE-2025-48517?

CVE-2025-48517 is a medium-severity missing authorization 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

Insufficient Granularity of Access Control in SEV firmware could allow a privileged user with a malicious hypervisor to create a SEV-ES guest with an ASID in the range meant for SEV-SNP guests potentially resulting in a partial loss of confidentiality.

Weakness: CWE-1220 (Insufficient Granularity of Access Control)

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


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

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

## Is CVE-2025-48517 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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