---
id: "CVE-2025-62621"
page: "https://infrastack.ai/live/CVE-2025-62621"
kind: "vulnerability"
aliases: ["CVE-2025-62621"]
title: "AMD SEV firmware: malicious hypervisor can break SEV-SNP guest memory integrity"
severity: "medium"
cvss: 5.9
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["amd", "confidential-computing", "hypervisor", "infrastructure", "sev-snp"]
not_affected_if: ["managed-hosting", "no-sev-snp"]
published_at: "2026-11-10T22:17:47+00:00"
first_seen_at: "2026-11-10T22:27:23+00:00"
updated_at: "2026-11-10T22:30:34+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-62621", "first_seen_at": "2026-11-10T22:27:23+00:00"}]
exploit_sources: []
---

# AMD SEV firmware: malicious hypervisor can break SEV-SNP guest memory integrity

Link for people: https://infrastack.ai/live/CVE-2025-62621 (this .md is for agents)

AMD Secure Encrypted Virtualization firmware has an expected-behavior violation that lets a malicious hypervisor bypass Reverse Map Table protections. An attacker controlling the hypervisor could alter memory of SEV-SNP guests, losing their memory integrity.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check whether hosts run AMD EPYC processors with SEV-SNP enabled for confidential VMs, for example by reviewing the hypervisor and host firmware versions.

## Timeline

- 2026-11-10T22:27:23+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2025-62621

## From the sources

Expected behavior violation in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to bypass Reverse Map Table (RMP) protections, potentially resulting in a loss of Secure Encrypted Virtualization-Secure Nested Paging (SEV-SNP) guest memory integrity.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_