CVE-2025-52535 · Infrastructure
NO FIX YET
AMD Secure Encrypted Virtualization (SEV) firmware reuses a resource improperly, letting an attacker with hypervisor access write to Reverse Map Table (RMP) protected memory. The result can be loss of guest memory integrity for virtual machines.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Affects hosts running AMD SEV-capable processors with SEV firmware in virtualized environments, where guest memory integrity is relied upon. The sources do not name the affected firmware versions or the patched versions, so the exact exposure is unknown. Teams not running AMD SEV-protected virtual machines can likely skip it.
Not affected if no-amd-sev
Who cares amd, hypervisor, sev, virtualization
Unknown from the sources.
No fix yet, per the sources.
Improper resource reuse in the AMD Secure Encrypted Virtualization (SEV) firmware could allow an attacker with hypervisor access to write to the Reverse Map Table (RMP) protected memory, potentially resulting in loss of guest memory integrity.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/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
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.