Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2025-0033 Overview
CVE-2025-0033 is an improper access control vulnerability [CWE-284] in AMD Secure Encrypted Virtualization-Secure Nested Paging (SEV-SNP). The flaw allows an administrator-privileged attacker to write to the Reverse Map Table (RMP) during SNP initialization. Successful exploitation can compromise the integrity of SEV-SNP guest memory, undermining a core confidential computing guarantee that protects guest workloads from a malicious or compromised hypervisor.
Critical Impact
An attacker with admin-level host privileges can corrupt RMP state during initialization, breaking SEV-SNP guest memory integrity protections and enabling tampering with confidential VM workloads.
Affected Products
- AMD processors supporting SEV-SNP (see AMD Security Bulletin SB-3020 for the full product list)
- Platforms running affected AMD Secure Processor firmware prior to the fixed versions
- Confidential computing environments relying on SEV-SNP for guest memory integrity
Discovery Timeline
- 2025-10-14 - CVE-2025-0033 published to the National Vulnerability Database
- 2026-10-18 - Last updated in NVD database
Technical Details for CVE-2025-0033
Vulnerability Analysis
AMD SEV-SNP extends SEV with the Reverse Map Table (RMP), a hardware-enforced structure that tracks page ownership and prevents the hypervisor from remapping or modifying guest-owned memory. The RMP is the trust anchor for SEV-SNP memory integrity guarantees.
CVE-2025-0033 arises from insufficient access control during the SNP initialization sequence. In this window, an administrator-privileged actor on the host can issue writes to the RMP that should be prohibited. Because the RMP governs which physical pages belong to which guest, unauthorized writes can corrupt page ownership metadata before guests begin executing.
The outcome is a loss of guest memory integrity. A privileged attacker can manipulate RMP entries so that subsequent guest memory accesses do not match the expected ownership state, breaking the isolation that confidential VMs depend on.
Root Cause
The root cause is improper access control [CWE-284] on RMP write operations during the SNP initialization phase. The platform firmware does not sufficiently restrict which entities can modify RMP entries at this stage, allowing a host administrator to perform writes that should be reserved for the AMD Secure Processor.
Attack Vector
Exploitation requires local access with high privileges on the host platform. The attacker must already hold administrative control of the host and must act during SNP initialization. No user interaction is required, and the scope is changed because the attack impacts guest VMs that are logically separate from the attacker's security domain. The vulnerability affects integrity only; confidentiality and availability are not directly impacted according to the CVSS vector.
No public proof-of-concept exploit is available, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.
Detection Methods for CVE-2025-0033
Indicators of Compromise
- Unexpected modifications to RMP state or SEV-SNP initialization errors reported by the AMD Secure Processor
- Guest VM attestation failures or integrity measurement mismatches following host administrative activity
- Hypervisor logs showing anomalous SNP_INIT or RMP management calls outside of planned provisioning windows
Detection Strategies
- Monitor host-level administrative actions that touch SEV-SNP initialization paths and correlate with change management records
- Validate SEV-SNP guest attestation reports before trusting workloads and alert on unexpected measurement changes
- Audit platform firmware and AMD Secure Processor firmware versions across the fleet against AMD Security Bulletin SB-3020
Monitoring Recommendations
- Ingest hypervisor, BMC, and platform firmware logs into a centralized analytics pipeline for correlation with host privilege use
- Track SNP guest launch and attestation telemetry to identify integrity verification failures at scale
- Alert on privileged shell sessions on confidential computing hosts outside maintenance windows
How to Mitigate CVE-2025-0033
Immediate Actions Required
- Review AMD Security Bulletin SB-3020 and identify affected processors in your environment
- Apply the AMD Secure Processor firmware and platform BIOS updates provided by your server OEM
- Restrict and audit administrative access on hosts running SEV-SNP confidential VMs
Patch Information
AMD has published remediation guidance in AMD Security Bulletin SB-3020. Fixes are delivered as updated AMD Secure Processor firmware packaged in OEM BIOS or platform firmware updates. Confirm that updates are applied before re-enabling SEV-SNP guest launches on remediated hosts.
Workarounds
- Enforce strict separation of duties so that no single administrator can perform SNP initialization unaudited
- Require guest attestation verification before accepting workloads onto SEV-SNP hosts and reject hosts with unverified firmware
- Defer confidential workloads to hosts confirmed to be running patched firmware pending full remediation
# Verify AMD Secure Processor and SEV-SNP firmware status on Linux hosts
sudo dmesg | grep -i -E 'sev|snp|ccp'
sudo cat /sys/module/kvm_amd/parameters/sev_snp
# Compare platform BIOS and PSP firmware versions against AMD SB-3020 fixed versions
sudo dmidecode -s bios-version
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

