AMD Secure Encrypted Virtualization (SEV) Vulnerabilities
Summary
Potential vulnerabilities in AMD Secure Encrypted Virtualization (SEV) affecting AMD EPYC™ and AMD EPYC™ Embedded Processor platforms were reported by external researchers or identified through internal reviews. AMD has provided mitigations for these issues.
CVE Details
Refer to Glossary for explanation of terms
CVE |
CVE Description |
CVSS Base Score |
CVE-2025-48504 |
Operation on a resource after expiration or release in the Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to manipulate metadata pages potentially resulting in the loss of confidentiality and integrity of guest memory. |
6.8 |
CVE-2025-29941 |
Incorrect usage of seeds in pseudo-random number generator in the Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor or migration agent to import a forged guest context potentially resulting in loss of confidentiality for derived guest keys. |
6.0 |
CVE-2026-0435 |
Operation on a resource after expiration or release in the AMD Secure Encrypted Virtualization (SEV) firmware could allow an attacker with administrative privileges to swap out a guest device without the guest's knowledge, potentially resulting in a loss of confidentiality and integrity. |
6.0 |
CVE-2026-0480 |
Missing Authentication for Critical Function in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to forge SEV-TIO guest request messages potentially compromising SEV-SNP guest memory integrity and confidentiality. |
6.0 |
CVE-2026-0003 |
Use of a per-part static key in the ASP Bootloader could allow an attacker to downgrade the Secure Encrypted Virtualization (SEV) firmware and exploit known vulnerabilities to decrypt memory potentially resulting in loss of confidentiality. |
5.9 |
CVE-2026-28247 |
Improper Access Control Applied to Mirrored or Aliased Memory Regions in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to change the encryption bit for guest context pages potentially resulting in loss of integrity. |
5.9 |
CVE-2026-28248 |
Improper enforcement of behavioral workflow in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to potentially launch a guest whose attestation report contains an ID key digest for an ID block that doesn't match the guest's measurement resulting in loss of integrity. |
5.9 |
CVE-2026-40670 |
Improper check for unusual or exceptional conditions in AMD Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP) could allow a privileged attacker to potentially overlap MMIO regions with DRAM regions resulting in loss of integrity. |
5.9 |
CVE-2026-0454 |
An out-of-bounds write in the AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to corrupt global firmware variables, potentially resulting in loss of integrity. |
4.6 |
CVE-2026-28249 |
Improper preservation of consistency between independent representations of shared state in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to potentially affect cache coherency for guest context pages resulting in loss of integrity. |
4.6 |
CVE-2026-40668 |
Authentication bypass by spoofing in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to request attestation reports for VMPL 0. |
4.6 |
CVE-2026-40669 |
An off-by-one error in AMD Secure Encrypted Virtualization (SEV) firmware could allow an attacker with hypervisor access to corrupt the Reverse Map Table (RMP) table, potentially resulting in loss of guest memory 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
AMD EPYC™ 7003 Series Processors |
CVE-2025-29941 |
MilanPI-SP3_1.0.0.K |
2026-05-07 |
N/A |
N/A |
N/A |
CVE-2025-48504 |
MilanPI-SP3_1.0.0.K |
2026-05-07 |
1.3A.02 |
Mitigation Bit=9 |
TCB[SNP]=0x1E |
|
CVE-2026-0003 |
MilanPI-SP3_1.0.0.K |
2026-05-07 |
1.3A.02 |
Mitigation Bit=5 |
TCB[SNP]=0x1E |
|
CVE-2026-28247 |
MilanPI-SP3_1.0.0.K |
2026-05-07 |
1.3A.02 |
Mitigation Bit=10 |
TCB[SNP]=0x1E |
|
CVE-2026-28248 |
MilanPI-SP3_1.0.0.K |
2026-05-07 |
N/A |
N/A |
N/A |
|
CVE-2026-28249 |
MilanPI-SP3_1.0.0.K |
2026-05-07 |
N/A |
N/A |
N/A |
|
CVE-2026-40668 |
MilanPI-SP3_1.0.0.K |
2026-05-07 |
N/A |
N/A |
N/A |
|
CVE-2026-40669 |
MilanPI-SP3_1.0.0.K |
2026-05-07 |
1.3A.02 |
Mitigation Bit=11 |
TCB[SNP]=0x1E |
|
CVE-2026-40670 |
MilanPI-SP3_1.0.0.K |
2026-05-07 |
N/A |
N/A |
N/A |
|
AMD EPYC™ 8004 Series Processors |
CVE-2025-29941 |
GenoaPI_1.0.0.J |
2026-06-26 |
N/A |
N/A |
N/A |
CVE-2025-48504 |
GenoaPI_1.0.0.J |
2026-06-26 |
1.3A.03 |
Mitigation Bit=7 |
TCB[SNP]=0X1D |
|
CVE-2026-0003 |
GenoaPI_1.0.0.J |
2026-06-26 |
1.3A.03 |
Mitigation Bit=4 |
TCB[SNP]=0x1D |
|
CVE-2026-28247 |
GenoaPI_1.0.0.J |
2026-06-26 |
1.3A.03 |
Mitigation Bit=8 |
TCB[SNP]=0x1D |
|
CVE-2026-28248 |
GenoaPI_1.0.0.J |
2026-06-26 |
N/A |
N/A |
N/A |
|
CVE-2026-28249 |
GenoaPI_1.0.0.J |
2026-06-26 |
N/A |
N/A |
N/A |
|
CVE-2026-40668 |
GenoaPI_1.0.0.J |
2026-06-26 |
N/A |
N/A |
N/A |
|
CVE-2026-40669 |
GenoaPI_1.0.0.J |
2026-06-26 |
1.3A.03 |
Mitigation Bit=9 |
TCB[SNP]=0x1D |
|
CVE-2026-40670 |
GenoaPI_1.0.0.J |
2026-06-26 |
N/A |
N/A |
N/A |
|
AMD EPYC™ 8005 Series Processors |
CVE-2025-29941 |
TurinPI_1.0.0.B |
2026-07-10 |
N/A |
N/A |
N/A |
CVE-2025-48504 |
TurinPI_1.0.0.B |
2026-07-10 |
1.3A.04 |
Mitigation Bit=13 |
TCB[SNP]=0x7 |
|
CVE-2026-0435 |
TurinPI_1.0.0.B |
2026-07-10 |
N/A |
N/A |
N/A |
|
CVE-2026-0454 |
TurinPI_1.0.0.B |
2026-07-10 |
N/A |
N/A |
N/A |
|
CVE-2026-0480 |
TurinPI_1.0.0.B |
2026-07-10 |
N/A |
N/A |
N/A |
|
CVE-2026-28247 |
TurinPI_1.0.0.B |
2026-07-10 |
1.3A.04 |
Mitigation Bit=14 |
TCB[SNP]=0x7 |
|
CVE-2026-28248 |
TurinPI_1.0.0.B |
2026-07-10 |
N/A |
N/A |
N/A |
|
CVE-2026-40668 |
TurinPI_1.0.0.B |
2026-07-10 |
N/A |
N/A |
N/A |
|
CVE-2026-40670 |
TurinPI_1.0.0.B |
2026-07-10 |
N/A |
N/A |
N/A |
|
AMD EPYC™ 9004 Series Processors |
CVE-2025-29941 |
GenoaPI_1.0.0.J |
2026-06-26 |
N/A |
N/A |
N/A |
CVE-2025-48504 |
GenoaPI_1.0.0.J |
2026-06-26 |
1.3A.03 |
Mitigation Bit=7 |
TCB[SNP]=0X1D |
|
CVE-2026-0003 |
GenoaPI_1.0.0.J |
2026-06-26 |
1.3A.03 |
Mitigation Bit=4 |
TCB[SNP]=0x1D |
|
CVE-2026-28247 |
GenoaPI_1.0.0.J |
2026-06-26 |
1.3A.03 |
Mitigation Bit=8 |
TCB[SNP]=0x1D |
|
CVE-2026-28248 |
GenoaPI_1.0.0.J |
2026-06-26 |
N/A |
N/A |
N/A |
|
CVE-2026-28249 |
GenoaPI_1.0.0.J |
2026-06-26 |
N/A |
N/A |
N/A |
|
CVE-2026-40668 |
GenoaPI_1.0.0.J |
2026-06-26 |
N/A |
N/A |
N/A |
|
CVE-2026-40669 |
GenoaPI_1.0.0.J |
2026-06-26 |
1.3A.03 |
Mitigation Bit=9 |
TCB[SNP]=0x1D |
|
CVE-2026-40670 |
GenoaPI_1.0.0.J |
2026-06-26 |
N/A |
N/A |
N/A |
|
AMD EPYC™ 9005 Series Processors |
CVE-2025-29941 |
TurinPI_1.0.0.B |
2026-07-10 |
N/A |
N/A |
N/A |
CVE-2025-48504 |
TurinPI_1.0.0.B |
2026-07-10 |
1.3A.04 |
Mitigation Bit=13 |
TCB[SNP]=0x7 |
|
CVE-2026-0435 |
TurinPI_1.0.0.B |
2026-07-10 |
N/A |
N/A |
N/A |
|
CVE-2026-0454 |
TurinPI_1.0.0.B |
2026-07-10 |
N/A |
N/A |
N/A |
|
CVE-2026-0480 |
TurinPI_1.0.0.B |
2026-07-10 |
N/A |
N/A |
N/A |
|
CVE-2026-28247 |
TurinPI_1.0.0.B |
2026-07-10 |
1.3A.04 |
Mitigation Bit=14 |
TCB[SNP]=0x7 |
|
CVE-2026-28248 |
TurinPI_1.0.0.B |
2026-07-10 |
N/A |
N/A |
N/A |
|
CVE-2026-40668 |
TurinPI_1.0.0.B |
2026-07-10 |
N/A |
N/A |
N/A |
|
CVE-2026-40670 |
TurinPI_1.0.0.B |
2026-07-10 |
N/A |
N/A |
N/A |
SEV Table
CVE ID |
SEV |
SEV-ES |
SEV-SNP |
CVE-2025-48504 |
N |
N |
Y |
CVE-2025-29941 |
N |
N |
Y |
CVE-2026-0435 |
N |
N |
Y |
CVE-2026-0480 |
N |
N |
Y |
CVE-2026-0003 |
N |
N |
Y |
CVE-2026-28247 |
N |
N |
Y |
CVE-2026-28248 |
N |
N |
Y |
CVE-2026-40670 |
N |
N |
Y |
CVE-2026-0454 |
N |
N |
Y |
CVE-2026-28249 |
N |
N |
Y |
CVE-2026-40668 |
N |
N |
Y |
CVE-2026-40669 |
N |
N |
Y |
AMD EPYC™ Embedded Series Processors
Product |
CVE ID |
Mitigation |
Mitigation Release Date |
AMD EPYC™ Embedded 7003 Series Processors |
CVE-2026-28248 |
EmbMilanPI-SP3 1.0.0.E |
2026-07-01 |
CVE-2026-40668 |
EmbMilanPI-SP3 1.0.0.E |
2026-07-01 |
|
CVE-2026-40669 |
EmbMilanPI-SP3 1.0.0.E |
2026-07-01 |
|
CVE-2026-40670 |
EmbMilanPI-SP3 1.0.0.E |
2026-07-01 |
|
CVE-2025-29941 |
EmbMilanPI-SP3 1.0.0.E |
2026-07-01 |
|
CVE-2025-48504 |
EmbMilanPI-SP3 1.0.0.E |
2026-07-01 |
|
CVE-2026-0003 |
EmbMilanPI-SP3 1.0.0.E |
2026-07-01 |
|
CVE-2026-28247 |
EmbMilanPI-SP3 1.0.0.E |
2026-07-01 |
|
CVE-2026-28249 |
EmbMilanPI-SP3 1.0.0.E |
2026-07-01 |
|
AMD EPYC™ Embedded 8004 Series Processors |
CVE-2026-28248 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
CVE-2026-40668 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2026-40669 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2026-40670 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2025-29941 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2025-48504 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2026-0003 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2026-28247 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2026-28249 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
AMD EPYC™ Embedded 9004 Series Processors (formerly codenamed "Bergamo") |
CVE-2026-28248 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
CVE-2026-40668 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2026-40669 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2026-40670 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2025-29941 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2025-48504 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2026-0003 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2026-28247 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2026-28249 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
AMD EPYC™ Embedded 9004 Series Processors (formerly codenamed "Genoa") |
CVE-2026-28248 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
CVE-2026-40668 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2026-40669 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2026-40670 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2025-29941 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2025-48504 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2026-0003 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2026-28247 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
CVE-2026-28249 |
EmbeddedGenoaPI_1.0.0.E |
2026-08-21 |
|
AMD EPYC™ Embedded 9005 Series Processors |
CVE-2026-28248 |
EmbeddedTurinPI_SP5_1005 |
2026-09-15 |
CVE-2026-0454 |
EmbeddedTurinPI_SP5_1005 |
2026-09-15 |
|
CVE-2026-0480 |
EmbeddedTurinPI_SP5_1005 |
2026-09-15 |
|
CVE-2026-40668 |
EmbeddedTurinPI_SP5_1005 |
2026-09-15 |
|
CVE-2026-40670 |
EmbeddedTurinPI_SP5_1005 |
2026-09-15 |
|
CVE-2026-0435 |
EmbeddedTurinPI_SP5_1005 |
2026-09-15 |
|
CVE-2026-28247 |
EmbeddedTurinPI_SP5_1005 |
2026-09-15 |
|
CVE-2025-29941 |
EmbeddedTurinPI_SP5_1005 |
2026-09-15 |
|
CVE-2025-48504 |
EmbeddedTurinPI_SP5_1005 |
2026-09-15 |
Acknowledgement
AMD thanks the following for reporting and engaging in coordinated vulnerability disclosure:
- Externally reported by Jon Lange (Microsoft): CVE-2026-0435
- Bug Bounty researcher Muyan Shen: CVE-2026-0003
- Internally reported: CVE-2026-0454, CVE-2026-0480, CVE-2026-28247, CVE-2026-28248, CVE-2026-28249, CVE-2025-29941, CVE-2026-40668, CVE-2026-40669, CVE-2026-40670, CVE-2025-48504
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.