CVE-2025-61972 Details
Description
Missing lock bit protection for NBIO registers could allow a local admin-privileged attacker to gain arbitrary System Management Network (SMN) access, potentially resulting in arbitrary code execution in AMD Secure Processor (ASP) and loss of the SEV-SNP guest's confidentiality and integrity.
A vulnerability exists in AMD EPYC and AMD EPYC Embedded Series Processors due to missing lock bit protection for NBIO registers. This flaw could enable a local admin-privileged attacker to gain unauthorized access to the System Management Network (SMN), potentially leading to arbitrary code execution within the AMD Secure Processor (ASP) environment. Additionally, this vulnerability could compromise the confidentiality and integrity of SEV-SNP guests.
Users are advised to update to the Platform Initialization (PI) firmware version specific to their processor series. For AMD EPYC Embedded 9005 Series Processors, the recommended version is EmbeddedTurinPI_SP5_1004, available from the original equipment manufacturer (OEM).
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No CVSS 3.x data is available for this CVE.
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed May 13, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://www.amd.com/en/resources/product-security/bulletin/AMD-SB-3030.html | [email protected] |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-1233 | Security-Sensitive Hardware Controls with Missing Lock Bit Protection | [email protected] |
Affected Products
No affected product data is available for this CVE.
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| May 13, 2026 | New CVE Received | [email protected] |