CVE-2025-48517
Access Control Bypass in AMD SEV Firmware Risks Confidentiality
Publication date: 2026-02-10
Last updated on: 2026-02-10
Assigner: Advanced Micro Devices Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| amd | sev_firmware | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-1220 | The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves insufficient granularity of access control in SEV firmware. It allows a privileged user who controls a malicious hypervisor to create a SEV-ES guest with an ASID (Address Space Identifier) that falls within the range intended for SEV-SNP guests. This misassignment can potentially lead to a partial loss of confidentiality.
How can this vulnerability impact me? :
The impact of this vulnerability is a potential partial loss of confidentiality. A malicious hypervisor with privileged access could exploit this flaw to gain unauthorized access to sensitive information within SEV-ES guests by misusing ASIDs intended for SEV-SNP guests.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know