CVE-2025-61972
Raw vector
CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-61972 is a high-severity Security-Sensitive Hardware Controls with Missing Lock Bit Protection (CWE-1233) vulnerability in Amd (inferred from references). Its CVSS base score is 8.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Pre-OS Boot (T1542); ranked at the 3th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-209812
Vulnerability Data
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…
more
integrity.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-3 directly requires enforcement of authorizations that would stop unauthorized writes to lock-bit-protected hardware registers.
Least privilege limits which subjects may alter security-sensitive configuration registers even when lock bits are present.
CM-5 mandates documented and enforced access restrictions on changes to system configuration, covering hardware register lock mechanisms.
Isolating security functions reduces the attack surface for tampering with hardware configuration registers protected by lock bits.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Hardened configuration baselines and verification directly enforce lock-bit settings on security-sensitive registers.
Pre-acquisition integrity checks can identify hardware lacking effective register lock-bit controls.
Hardware replacement decisions can address devices lacking functional lock-bit protection.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing lock-bit protection during hardware/firmware validation.
Secure system architecture principles require hardware lock-bit protection for critical configuration registers.
Configuration management enforces lock-bit settings and prevents unauthorized hardware register changes.
Secure coding practices can include checks for proper lock-bit usage in firmware.
Change management processes can require verification that lock bits remain set after updates.