CVE-2025-0033
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAMD SEV-SNP (Secure Encrypted Virtualization with Secure Nested Paging) has an improper access control vulnerability during SNP initialization that allows an administrator-privileged attacker to write to the Reverse Page Table (RMP), compromising guest memory integrity.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify CPU hardware support for SEV-SNPRun `grep -o 'sev_snp\|sev' /proc/cpuinfo` or use `cpuid | grep -i sev` to check if the processor advertises SEV-SNP capability in CPU flagsAffected if The CPU does not show sev_snp or sev flags, indicating the processor lacks SEV-SNP hardware support and is not affected
-
Confirm hypervisor type and SEV-SNP statusCheck if running under a KVM hypervisor with `lsmod | grep kvm` and verify SEV-SNP is enabled in the hypervisor configuration or libvirt XML definitions for the VMAffected if Hypervisor is not KVM-based or does not have SEV-SNP explicitly enabled in the VM configuration, indicating the attack surface is not present
-
Inspect SEV-SNP enablement in hypervisor boot or configReview hypervisor boot parameters (e.g., kvm_amd.sev=1 in kernel cmdline) or configuration files for SEV-SNP initialization settingsAffected if SEV-SNP is not enabled in the hypervisor, meaning the vulnerable SNP initialization code path is not executed
-
Check BIOS/UEFI for SEV-SNP memory encryption settingAccess system BIOS/UEFI setup and look for memory encryption settings (e.g., 'AMD Memory Guard', 'SEV-SNP', 'Secure Encrypted Virtualization') - if accessible via `dmidecode`, check for memory encryption-related entriesAffected if Memory encryption or SEV-SNP is disabled in BIOS/UEFI, so the vulnerable code path during SNP initialization is not reached
-
Identify hypervisor and check for SNP initializationDetermine hypervisor version via `qemu-system-x86_64 --version`, `virsh version`, or host OS details, then check whether SNP-enabled VMs have been launchedAffected if No SEV-SNP virtual machines have been instantiated on the hypervisor, as the vulnerability requires SNP initialization to be triggered
A system is affected only if it runs on AMD hardware with SEV-SNP capability, uses a hypervisor that supports and enables SEV-SNP, and has SEV-SNP virtual machines initialized, allowing an administrator to reach the vulnerable SNP initialization code path.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply AMD-provided firmware/microcode updates for SEV-SNP-enabled processors and ensure hypervisors are updated to enforce proper RMP access controls during SNP initialization.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-0033 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-0033 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data