SEV-SNP guest integrity loss via unlocked NBIO registers
Published May 13, 2026 · Updated May 13, 2026
Missing lock-bit protection in affected AMD EPYC processors allows local users with host administration to alter SEV-SNP guest execution. NBIO registers remain writable after trusted firmware initializes them, allowing privileged host software to rewrite MMIO routing configuration. Host administrator privileges and an active SEV-SNP guest are required; the documented consequence is guest-integrity loss without confidentiality or availability impact.
Summary
What happened
Missing lock-bit protection in affected AMD EPYC processors allows local users with host administration to alter SEV-SNP guest execution. NBIO registers remain writable after trusted firmware initializes them, allowing privileged host software to rewrite MMIO routing configuration. Host administrator privileges and an active SEV-SNP guest are required; the documented consequence is guest-integrity loss without confidentiality or availability impact.
The record
- CVE
- CVE-2025-61971
- Published
- May 13, 2026
- Updated
- May 13, 2026
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD EPYC Embedded 8004 Series Processors
- Classifications
- CWE-1233, CAPEC-680, CAPEC-176, T1565.003
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 13, 2026CVE publishedPublication date reported by the CVE source.
- May 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo