Cyber Resilience

CVE-2025-61972

Published
13 May 2026
Modified
17 June 2026
CVSS Score v4 8.5
Click a component to see what it means
Raw vectorCVSS: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:X
EPSS Score 0.0013 3th percentile
Risk Priority 24 floored blend · peak EPSS

Summary

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

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

T1542 Pre-OS Boot Stealth
Adversaries may abuse Pre-OS Boot mechanisms as a way to establish persistence on a system.
T1542.001 System Firmware Stealth
Adversaries may modify system firmware to persist on systems.
T1542.002 Component Firmware Stealth
Adversaries may modify component firmware to persist on systems.
T1601 Modify System Image Defense Impairment
Adversaries may make changes to the operating system of embedded network devices to weaken defenses and provide new capabilities for themselves.
T1495 Firmware Corruption Impact
Adversaries may overwrite or corrupt the flash memory contents of system BIOS or other firmware in devices attached to a system in order to render them inoperable or unable to boot, thus denying the availability to use the devices and/or…
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-61971Shared CWE-1233
CVE-2025-25733Shared CWE-1233
CVE-2025-25735Shared CWE-1233
CVE-2025-25734Shared CWE-1233

Affected Assets

Amd
inferred from references and description; NVD did not file a CPE for this CVE

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.

PR.PS-01 mostly match
prevents

Hardened configuration baselines and verification directly enforce lock-bit settings on security-sensitive registers.

ID.RA-09 partial match
prevents

Pre-acquisition integrity checks can identify hardware lacking effective register lock-bit controls.

PR.PS-03 partial match
prevents

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.

finds

Security testing can detect missing lock-bit protection during hardware/firmware validation.

prevents

Secure system architecture principles require hardware lock-bit protection for critical configuration registers.

degrades

Configuration management enforces lock-bit settings and prevents unauthorized hardware register changes.

none

Secure coding practices can include checks for proper lock-bit usage in firmware.

none

Change management processes can require verification that lock bits remain set after updates.

References