CVE-2025-61971: NBIO Register Privilege Escalation Flaw

CVE-2025-61971 Overview

CVE-2025-61971 is a hardware-level vulnerability in AMD platforms caused by missing lock bit protection on Northbridge I/O (NBIO) registers. A local attacker with administrative privileges can modify Memory-Mapped I/O (MMIO) routing configurations that should be immutable after platform initialization. The flaw maps to [CWE-1233: Security-Sensitive Hardware Controls with Missing Lock Bit Protection]. Exploitation can break the integrity guarantees of Secure Encrypted Virtualization-Secure Nested Paging (SEV-SNP) confidential guests running on the affected host.

Critical Impact

A local admin-privileged attacker on the host can manipulate MMIO routing through unlocked NBIO registers and undermine SEV-SNP confidential guest integrity protections.

Affected Products

• AMD processors supporting SEV-SNP with affected NBIO register configurations (see AMD Security Bulletin AMD-SB-3030)
• Host platforms exposing unlocked NBIO MMIO routing registers
• SEV-SNP confidential virtualization deployments relying on host integrity isolation

Discovery Timeline

• 2026-05-13 - CVE-2025-61971 published to the National Vulnerability Database
• 2026-05-13 - Last updated in NVD database

Technical Details for CVE-2025-61971

Vulnerability Analysis

The vulnerability resides in the NBIO register set used to configure MMIO address routing on AMD platforms. Lock bits are hardware mechanisms that freeze register contents after firmware completes initialization. When these lock bits are missing or not asserted, privileged software running on the host can rewrite routing configuration at runtime. This breaks an architectural assumption of SEV-SNP, which relies on the host platform exposing a stable and trustworthy memory topology to the secure processor and to confidential guests. By rerouting MMIO regions, an attacker can redirect device traffic or memory accesses in ways that violate the integrity guarantees promised to a confidential VM.

Root Cause

The root cause is the absence of lock bit enforcement on security-sensitive NBIO configuration registers. Hardware controls that govern platform memory routing must be locked before guest workloads execute. Without that enforcement, the registers remain writable through their administrative interfaces and become a tampering primitive available to any code running with local admin privileges on the host.

Attack Vector

Exploitation requires local access and high privileges on the host operating system or hypervisor. An attacker with administrative rights writes to the affected NBIO MMIO routing registers to alter the platform memory map after SEV-SNP guests have started. The attack does not require user interaction and is not exposed remotely. The integrity impact targets the confidential guest rather than confidentiality or availability, consistent with the SEV-SNP threat model where the host is considered untrusted.

No public proof-of-concept code is available for CVE-2025-61971. Refer to AMD Security Bulletin AMD-SB-3030 for vendor-supplied technical detail.

Detection Methods for CVE-2025-61971

Indicators of Compromise

• Unexpected writes to NBIO MMIO configuration registers after platform initialization completes
• Runtime changes to host memory routing tables that were expected to be static
• SEV-SNP guest attestation failures or integrity measurement mismatches on previously trusted hosts

Detection Strategies

• Monitor host kernel and hypervisor logs for privileged drivers or modules accessing AMD NBIO register space outside of firmware initialization windows
• Validate firmware and BIOS versions across the fleet against AMD's fixed builds referenced in AMD-SB-3030
• Correlate administrative logons on confidential-compute hosts with subsequent device or kernel module load events

Monitoring Recommendations

• Alert on loading of unsigned or unexpected kernel drivers on hosts running SEV-SNP workloads
• Track SEV-SNP guest attestation reports for deviations and route failures to the SOC for review
• Audit administrative account usage on confidential virtualization hosts and require multi-party approval for privileged sessions

How to Mitigate CVE-2025-61971

Immediate Actions Required

• Inventory AMD-based hosts running SEV-SNP confidential workloads and identify systems exposed to AMD-SB-3030
• Apply the BIOS, firmware, and AGESA updates published by AMD and your server OEM as soon as they are available for your platform
• Restrict and audit local administrative access on confidential-compute hosts, since exploitation requires high privileges

Patch Information

AMD has documented the affected platforms and fixed firmware levels in AMD Security Bulletin AMD-SB-3030. Coordinate with your server vendor to obtain BIOS or AGESA updates that enforce lock bit protection on the affected NBIO registers, then redeploy the firmware across all impacted hosts and verify SEV-SNP attestation after the update.

Workarounds

• Limit host administrator accounts to a minimal, monitored set until firmware updates are deployed
• Avoid scheduling sensitive SEV-SNP confidential workloads on hosts that have not yet received the AMD-SB-3030 firmware fix
• Enforce attestation-based admission control so that guests refuse to run on hosts reporting unpatched firmware versions

# Verify host firmware level against AMD-SB-3030 fixed versions
sudo dmidecode -s bios-version
sudo dmidecode -s bios-release-date

# Confirm SEV-SNP platform state on a Linux host
cat /sys/module/kvm_amd/parameters/sev_snp