CVE-2025-0033
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-10-14

Last updated on: 2025-10-14

Assigner: Advanced Micro Devices Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-10-14
Last Modified
2025-10-14
Generated
2026-06-16
AI Q&A
2025-10-14
EPSS Evaluated
2026-06-15
NVD
CVE-2025-0033
EUVD
EUVD-2025-34221
Affected Vendors & Products
Showing 7 associated CPEs
Vendor Product Version / Range
amd epyc 9005
amd epyc 7002
amd epyc 7001
amd sev *
amd epyc 4004
amd epyc 8004
amd epyc 7003
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2025-0033 is a medium-severity vulnerability in AMD's Secure Encrypted Virtualization Secure Nested Paging (SEV-SNP) technology. It involves improper access control during the initialization of the Reverse Map Table (RMP), where a malicious hypervisor with administrative privileges can exploit a race condition to write to and corrupt the RMP content. This corruption can compromise the integrity of the SEV-SNP guest memory. [1]

Impact Analysis

This vulnerability allows a local attacker with administrative privileges on the hypervisor to corrupt the guest memory integrity of SEV-SNP protected virtual machines. While it does not affect confidentiality or availability, it can lead to loss of integrity of guest memory, potentially allowing malicious manipulation of data within the virtualized environment. [1]

Mitigation Strategies

To mitigate CVE-2025-0033, immediately update the SEV Firmware and microcode to the specified versions for your AMD EPYC processor family (e.g., Milan SEV FW 1.37.23 with microcode 0x0A0011DE, Genoa SEV FW 1.37.31 with microcode 0x0A101156, Turin SEV FW 1.37.41 with microcode 0x0B002150). Alternatively, apply the AGESA SEV Mitigation Vector Bit 1 via Platform Initialization (PI) firmware updates provided by your OEM. These BIOS/firmware updates are critical to prevent a privileged hypervisor from exploiting the race condition in SEV-SNP RMP initialization. [1]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-0033. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart