AMD Secure Encrypted Virtualization (SEV) Vulnerabilities
Summary
Potential vulnerabilities in AMD Secure Encrypted Virtualization affecting AMD EPYC™ and AMD EPYC™ Embedded Processor platforms were found internally. AMD has provided mitigations for these issues.
CVE Details
Refer to Glossary for explanation of terms
| CVE | CVE Description | CVSS Base Score |
CVE-2025-0027 |
Improper access control in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to bypass Reverse Map Table (RMP) protections, potentially impacting the integrity of Secure Encrypted Virtualization-Secure Nested Paging (SEV-SNP) guest memory. |
5.9 |
CVE-2025-29940 |
Unverified ownership in Secure Encrypted Virtualization (SEV) firmware could allow a privileged attacker with access to a malicious hypervisor to overwrite guest memory if segmented Reverse Map Table (RMP) is enabled potentially resulting in loss of guest data integrity. |
5.9 |
CVE-2025-52535 |
Improper resource reuse in the AMD Secure Encrypted Virtualization (SEV) firmware could allow an attacker with hypervisor access to write to the Reverse Map Table (RMP) protected memory, potentially resulting in loss of guest memory integrity. |
5.9 |
CVE-2025-54503 |
Improper handling of overlap between protected memory ranges in the Secure Encrypted Virtualization (SEV) firmware could allow a privileged attacker to cause misconfigurations in the RMP potentially resulting in loss of integrity. |
5.9 |
CVE-2025-54504 |
Insufficient Granularity of Access Control in AMD Secure Encrypted Virtualization (SEV) firmware could allow an attacker with administrative privileges attacker to write to a trusted region used by AMD Secure Encrypted Virtualization-Encrypted State (SEV-ES), potentially resulting in loss of integrity. |
5.9 |
CVE-2025-62620 |
Improper validation of unsafe equivalence in input could allow an attacker with high privileges to reclaim the ring buffer queue status page, potentially resulting in loss of guest memory integrity. |
5.9 |
CVE-2025-62621 |
Expected behavior violation in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to bypass Reverse Map Table (RMP) protections, potentially resulting in a loss of Secure Encrypted Virtualization-Secure Nested Paging (SEV-SNP) guest memory integrity. |
5.9 |
CVE-2025-52537 |
Improper access control within the AMD Secure Encrypted Virtualization (SEV) firmware could allow an attacker with administrative privileges to tamper with memory, potentially resulting in loss of guest memory integrity. |
4.0 |
CVE-2025-54506 |
A time-of-check to time-of-use (TOCTOU) race condition in the AMD SEV Secure Encrypted Virtualization (SEV) firmware could allow an attacker with administrative privileges to bypass security checks on scatter lists, potentially resulting in loss of guest integrity. |
4.0 |
CVE-2025-54508 |
Improper validation of Reverse Map Table (RMP) entries in the Secure Encrypted Virtualization (SEV) firmware could allow a privileged attacker to trigger concurrent modifications to RMP entries without proper synchronization potentially resulting in loss of data integrity. |
4.0 |
Specific CVSS scores may change subject to your implementation. We encourage you to calculate CVSS scores independently for your system.
Affected Products and Mitigation
AMD recommends updating to the Platform Initialization (PI) firmware version indicated below (note the PI firmware versions were released by AMD to the Original Equipment Manufacturers (OEM) on the dates listed below). Please contact your OEM for the BIOS update specific to your product(s).
*Note: Products believed to not be affected by the listed CVEs are not included.
AMD EPYC™ Series Processors
Product |
CVE ID |
Platform Initialization (PI) Mitigation |
PI Release Date |
SEV FW Mitigation (included in PI) |
OS Update |
Mitigation Bit |
TCB Values for SNP Attestation |
AMD EPYC™ 7003 Series Processors |
CVE-2025-0027 |
MilanPI-SP3_1.0.0.K |
2026-05-07 |
1.3A.02 |
Yes VMWare + Windows |
Mitigation Bit=3 |
TCB[SNP]=0x1E |
CVE-2025-52535 |
MilanPI-SP3_1.0.0.K |
2026-05-07 |
1.3A.02 |
N/A |
N/A |
TCB[SNP]=0x1E |
|
CVE-2025-62620 |
MilanPI-SP3_1.0.0.K |
2026-05-07 |
1.3A.02 |
N/A |
Mitigation Bit=7 |
TCB[SNP]=0x1E |
|
AMD EPYC™ 8004 Series Processors |
CVE-2025-0027 |
GenoaPI_1.0.0.J |
2026-06-26 |
1.3A.03 |
Yes VMWare + Windows |
mitigation bit=3 |
TCB[SNP]=0x1D |
CVE-2025-52535 |
GenoaPI_1.0.0.J |
2026-06-26 |
N/A |
N/A |
N/A |
N/A |
|
CVE-2025-62620 |
GenoaPI_1.0.0.J |
2026-06-26 |
1.3A.03 |
N/A |
Mitigation Bit=5 |
TCB[SNP]=0x1D |
|
AMD EPYC™ 9004 Series Processors |
CVE-2025-0027 |
GenoaPI_1.0.0.J |
2026-06-26 |
1.3A.03 |
Yes VMWare + Windows |
Mitigation Bit=3 |
TCB[SNP]=0x1D |
CVE-2025-52535 |
GenoaPI_1.0.0.J |
2026-06-26 |
1.3A.03 |
N/A |
N/A |
TCB[SNP]=0x1D |
|
CVE-2025-62620 |
GenoaPI_1.0.0.J |
2026-06-26 |
1.3A.03 |
N/A |
Mitigation Bit=5 |
TCB[SNP]=0x1D |
|
AMD EPYC™ 9005 Series Processors |
CVE-2025-0027 |
TurinPI_1.0.0.A |
2026-02-24 |
1.3A.05 |
Yes VMWare + Windows |
Mitigation Bit=3 |
TCB[SNP]=0x6 |
CVE-2025-29940 |
TurinPI_1.0.0.A |
2026-02-24 |
1.3A.04 |
N/A |
Mitigation Bit=6 |
TCB[SNP]=0x6 |
|
CVE-2025-52535 |
TurinPI_1.0.0.A |
2026-02-24 |
1.3A.06 |
N/A |
N/A |
TCB[SNP]=0x6 |
|
CVE-2025-52537 |
TurinPI_1.0.0.A |
2026-02-24 |
1.3A.06 |
N/A |
N/A |
TCB[SNP]=0x6 |
|
CVE-2025-54503 |
TurinPI_1.0.0.A |
2026-02-24 |
1.3A.04 |
N/A |
Mitigation Bit=7 |
TCB[SNP]=0x6 |
|
CVE-2025-54504 |
TurinPI_1.0.0.A |
2026-02-24 |
1.3A.06 |
N/A |
N/A |
TCB[SNP]=0x6 |
|
CVE-2025-54506 |
TurinPI_1.0.0.A |
2026-02-24 |
1.3A.06 |
N/A |
N/A |
TCB[SNP]=0x6 |
|
CVE-2025-54508 |
TurinPI_1.0.0.A |
2026-02-24 |
1.3A.04 |
N/A |
Mitigation Bit=10 |
TCB[SNP]=0x6 |
|
CVE-2025-62620 |
TurinPI_1.0.0.A |
2026-02-24 |
1.3A.04 |
N/A |
Mitigation Bit=11 |
TCB[SNP]=0x6 |
|
CVE-2025-62621 |
TurinPI_1.0.0.A |
2026-02-24 |
1.3A.04 |
N/A |
Mitigation Bit=8 |
TCB[SNP]=0x6 |
SEV Table
CVE ID |
SEV |
SEV-ES |
SEV-SNP |
CVE-2025-0027 |
N |
N |
Y |
CVE-2025-29940 |
N |
N |
Y |
CVE-2025-52535 |
N |
N |
Y |
CVE-2025-54503 |
N |
N |
Y |
CVE-2025-54504 |
N |
N |
Y |
CVE-2025-62620 |
N |
N |
Y |
CVE-2025-62621 |
N |
N |
Y |
CVE-2025-52537 |
N |
N |
Y |
CVE-2025-54506 |
N |
N |
Y |
CVE-2025-54508 |
N |
N |
Y |
AMD EPYC™ Embedded Series Processors
Product |
CVE ID |
Mitigation |
Mitigation Release Date |
AMD EPYC™ Embedded 7003 Series Processors |
CVE-2025-0027 |
EmbMilanPI-SP3 1.0.0.E |
2026-07-01 |
CVE-2025-52535 |
EmbMilanPI-SP3 1.0.0.E |
2026-07-01 |
|
CVE-2025-62620 |
EmbMilanPI-SP3 1.0.0.E |
2026-07-01 |
|
AMD EPYC™ Embedded 8004 Series Processors |
CVE-2025-0027 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
CVE-2025-52535 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2025-62620 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
AMD EPYC™ Embedded 9004 Series Processors (formerly codenamed "Bergamo") |
CVE-2025-0027 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
CVE-2025-52535 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2025-62620 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
AMD EPYC™ Embedded 9004 Series Processors (formerly codenamed "Genoa") |
CVE-2025-0027 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
CVE-2025-52535 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2025-62620 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
AMD EPYC™ Embedded 9005 Series Processors |
CVE-2025-0027 |
EmbeddedTurinPI_SP5_1004 |
2026-04-13 |
CVE-2025-29940 |
EmbeddedTurinPI_SP5_1004 |
2026-04-13 |
|
CVE-2025-52535 |
EmbeddedTurinPI_SP5_1004 |
2026-04-13 |
|
CVE-2025-52537 |
EmbeddedTurinPI_SP5_1004 |
2026-04-13 |
|
CVE-2025-54503 |
EmbeddedTurinPI_SP5_1004 |
2026-04-13 |
|
CVE-2025-54504 |
EmbeddedTurinPI_SP5_1004 |
2026-04-13 |
|
CVE-2025-54506 |
EmbeddedTurinPI_SP5_1004 |
2026-04-13 |
|
CVE-2025-54508 |
EmbeddedTurinPI_SP5_1004 |
2026-04-13 |
|
CVE-2025-62620 |
EmbeddedTurinPI_SP5_1004 |
2026-04-13 |
|
CVE-2025-62621 |
EmbeddedTurinPI_SP5_1004 |
2026-04-13 |
Acknowledgement
AMD thanks the following for reporting and engaging in coordinated vulnerability disclosure:
- Internally reported: CVE-2025-0027, CVE-2025-29940, CVE-2025-52535, CVE-2025-52537, CVE-2025-54503, CVE-2025-54504, CVE-2025-54506, CVE-2025-54508, CVE-2025-62620, CVE-2025-62621
Revisions
| Revision Date | Description |
| 2026-11-10 | Initial version |
DISCLAIMER
The information contained herein is for informational purposes only and is subject to change without notice. While every precaution has been taken in the preparation of this document, it may contain technical inaccuracies, omissions and typographical errors, and AMD is under no obligation to update or otherwise correct this information. Advanced Micro Devices, Inc. makes no representations or warranties with respect to the accuracy or completeness of the contents of this document, and assumes no liability of any kind, including the implied warranties of noninfringement, merchantability or fitness for particular purposes, with respect to the operation or use of AMD hardware, software or other products described herein. Any computer system has risks of security vulnerabilities that cannot be completely prevented or mitigated. No license, including implied or arising by estoppel, to any intellectual property rights is granted by this document. Terms and limitations applicable to the purchase or use of AMD's products are as set forth in a signed agreement between the parties or in AMD's Standard Terms and Conditions of Sale.
AMD, the AMD Arrow logo, EPYC, and combinations thereof are trademarks of Advanced Micro Devices, Inc. CVE is a trademark of The MITRE Corporation. Other product names used in this publication are for identification purposes only and may be trademarks of their respective companies.
Third party content may be licensed to you directly by the third party that owns the content and is not licensed to you by AMD. ALL LINKED THIRD-PARTY CONTENT IS PROVIDED 'AS IS' WITHOUT A WARRANTY OF ANY KIND. USE OF SUCH THIRD-PARTY CONTENT IS DONE AT YOUR SOLE DISCRETION AND UNDER NO CIRCUMSTANCES WILL AMD BE LIABLE TO YOU FOR ANY THIRD PARTY CONTENT. YOU ASSUME ALL RISK AND ARE SOLELY RESPONSIBILITY FOR ANY DAMAGES THAT MAY ARISE FROM YOUR USE OF THIRD-PARTY CONTENT.
© 2026 Advanced Micro Devices, Inc. All rights reserved.