Loading vulnerability…
RMPocalypse is a race condition in AMD EPYC processors implementing Secure Encrypted Virtualization – Secure Nested Paging (SEV-SNP). During initialization of the Reverse Map Table (RMP) by the AMD Secure Processor, RMP memory is not fully protected before entries are locked, creating a window in which a malicious or compromised hypervisor with privileged control can write to and corrupt RMP entries. Because the RMP is a core SEV-SNP mechanism used to enforce guest page ownership and integrity, corruption during this initialization phase can undermine the integrity guarantees of confidential virtual machines. Reported demonstrations include manipulation of guest memory protections, attestation-related abuse, VMSA state replay, enabling debug on production-mode confidential VMs, and code injection into protected guests.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
19 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity vulnerability in AMD EPYC processors using SEV-SNP, involving a race condition during Reverse Map Table initialization that can impact guest memory integrity and enable code execution scenarios.
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.
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.