Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Medium

AMD IOMMU RMP Check Bypass Leading to Guest Memory Integrity Corruption

IdentifiersCVE-2023-20585CWE-125

CVE-2023-20585 is an AMD IOMMU-related vulnerability caused by insufficient checks of the Reverse Map Table (RMP) during host buffer access. According to the provided content, the flaw allows an attacker with privileges and a compromised hypervisor to trigger an out-of-bounds condition without the expected RMP checks. The issue affects confidential computing guest protections and has been described by Microsoft as an AMD IOMMU Write Buffer vulnerability that could lead to corruption of guest encrypted memory. The Linux kernel fix references the iommu/amd subsystem and specifically notes a remediation to use the maximum event log buffer size when Secure Nested Paging (SNP) is enabled on AMD Family 0x19 systems.

Share:
For your environment

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.

ANALYST BRIEF

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.

Successful exploitation can undermine confidential guest integrity by enabling corruption or tampering of guest encrypted memory or other protected guest state. The provided content does not indicate a direct confidentiality or availability impact, but it does explicitly state integrity loss for confidential guests and guest encrypted memory corruption as the primary consequence.

Mitigation

If you can’t patch tonight, do this now.

The provided content indicates that mitigation is primarily patch-based. Apply the relevant Windows update or updated Linux kernel packages from the platform vendor. Because exploitation requires a compromised hypervisor and high privileges, reducing exposure of confidential-computing workloads to untrusted or compromised hypervisors and limiting privileged access on the host may reduce risk, but specific non-patch mitigations are not provided in the source content.

Remediation

Patch, then assume compromise.

Apply vendor-provided updates that address CVE-2023-20585. In the Linux kernel context provided, SUSE remediated the issue in iommu/amd by using the maximum event log buffer size when SNP is enabled on Family 0x19, with fixed kernel package versions released across supported SUSE product lines. In the Microsoft context, install the latest supported Windows build or relevant Windows security update, which Microsoft states enables the mitigation for this vulnerability. Where applicable, consult AMD bulletin AMD-SB-3016 and platform vendor advisories for product-specific fixed versions.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.