CVE-2025-0033: Race Condition

Published Oct 13, 2025
·
Updated

AMD CVE-2025-0033: RMP Corruption During SNP Initialization

Other sources

Improper access control within AMD SEV-SNP could allow an admin privileged attacker to write to the RMP during SNP initialization, potentially resulting in a loss of SEV-SNP guest memory integrity.

NVD

Microsoft is aware of AMD-SB-3020 | CVE-2025-0033 disclosed by AMD on October 13, 2025. CVE-2025-0033 is a vulnerability in AMD EPYC processors using Secure Encrypted Virtualization – Secure Nested Paging (SEV-SNP). It involves a race condition during Reverse Map Table (RMP) initialization that could allow a malicious or compromised hypervisor to modify RMP entries before they are locked, potentially impacting the integrity of SEV-SNP guest memory. This issue does not expose plaintext data or secrets and requires privileged control of the hypervisor to exploit. Across Azure Confidential Computing products, multiple security guardrails are in place to prevent host compromise, combining isolation, integrity verification and continuous monitoring. All host operations follow audited and approved management pathways, with administrative access strictly controlled, limited and logged. Together, these protections reduce the risk of host compromise or unauthorized memory manipulation, helping ensure that confidential workloads and customer VMs maintain their confidentiality and integrity on Azure hosts.

Microsoft

Affected Software

8 affected components
AMD SEV-SNP
AMD Secure Processor
Microsoft Azure Confidential Compute
Microsoft Azure Confidential Compute VM SKU DCasv5/DCadsv5
Microsoft Azure Confidential Compute VM SKU ECasv5/ECadsv5
Microsoft Azure Confidential Compute VM SKU DCasv6/DCadsv6
Microsoft Azure Confidential Compute VM SKU ECasv6/ECadsv6
Microsoft Azure Confidential Compute GPU SKU NCC40ads_H100_v5

Event History

Oct 13, 2025
CVE Published
via Microsoft·07:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Description
Oct 14, 2025
CVE Published
via MITRE·02:49 PM
Data Sourced
via MITRE·02:49 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:16 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-0033?

CVE-2025-0033 has been rated as critical due to its potential to allow a malicious hypervisor to compromise memory isolation.

2

How do I fix CVE-2025-0033?

To mitigate CVE-2025-0033, apply the latest firmware updates from AMD and relevant security patches from your cloud service provider.

3

Which platforms are affected by CVE-2025-0033?

CVE-2025-0033 affects AMD's SEV-SNP implementation on Milan, Genoa, and Turin platforms.

4

What type of attack does CVE-2025-0033 enable?

CVE-2025-0033 potentially allows a malicious hypervisor to corrupt Restricted Memory Pages during Secure Nested Paging initialization.

5

Is CVE-2025-0033 specific to certain software?

Yes, CVE-2025-0033 primarily affects AMD SEV-SNP and Secure Processor technologies, as well as Microsoft Azure Confidential Compute.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203