RMPocalypse in AMD SEV-SNP RMP Initialization
CVE-2025-0033, also referred to as RMPocalypse, is a race condition in AMD SEV-SNP affecting AMD EPYC and EPYC Embedded processors. During initialization of the Reverse Map Table (RMP) by the AMD Secure Processor (ASP), the memory backing the RMP is not fully protected before the table is locked. A malicious or compromised hypervisor with administrative control can win this initialization race and write to RMP entries before protections take effect. Because the RMP is the SEV-SNP mechanism that tracks page ownership and mappings to prevent hypervisor tampering with guest memory, corruption of RMP entries can undermine SEV-SNP guest memory integrity. Reported demonstrations include enabling debug on production confidential VMs, faking attestation, VMSA state replay, and code injection. Microsoft states the issue impacts memory integrity and does not directly expose plaintext guest data or secrets.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Hardware/virtualization security issue in AMD EPYC SEV-SNP where a race during RMP initialization could let a malicious/compromised hypervisor alter RMP entries before lock, impacting memory integrity (not plaintext exposure).
A publicly disclosed vulnerability involving AMD SEV-SNP RMP corruption (as described in the article).
A race condition affecting Azure Confidential Computing integrity on AMD EPYC SEV-SNP processors.
Race condition during SEV-SNP Reverse Map Table initialization that could allow a malicious/compromised hypervisor to modify RMP entries before lock, corrupting guest memory; patch not yet available per the content.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.