Firmware integrity loss via modifiable SEV lock bit
Published Feb 10, 2026 · Updated Feb 10, 2026
Improper lock-bit protection in AMD SEV-SNP firmware on affected EPYC processors allows local administrators to downgrade firmware. The firmware fails to prevent modification of a security lock bit after it is set, leaving rollback protection ineffective. Exploitation requires high local privileges and can replace protected firmware state with an older version, compromising firmware integrity.
Summary
What happened
Improper lock-bit protection in AMD SEV-SNP firmware on affected EPYC processors allows local administrators to downgrade firmware. The firmware fails to prevent modification of a security lock bit after it is set, leaving rollback protection ineffective. Exploitation requires high local privileges and can replace protected firmware state with an older version, compromising firmware integrity.
The record
- CVE
- CVE-2025-52536
- Published
- Feb 10, 2026
- Updated
- Feb 10, 2026
- Vendor
- Advanced Micro Devices, Inc.
- Product
- AMD EPYC Embedded 8004 Series Processors
- Classifications
- CWE-1231
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 10, 2026CVE publishedPublication date reported by the CVE source.
- Feb 10, 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