CVE-2025-29940 · Infrastructure
NO FIX YET
Unverified ownership in AMD Secure Encrypted Virtualization firmware lets a privileged attacker controlling a malicious hypervisor overwrite guest memory when segmented Reverse Map Table is enabled. The result is loss of guest data integrity.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Systems running AMD SEV guests on AMD EPYC hosts with segmented RMP enabled, where the hypervisor could be untrusted or compromised. Hosts without SEV or with segmented RMP disabled are not described as exposed. The sources do not list affected firmware versions.
Not affected if no-sev, segmented-rmp-disabled
Who cares amd, confidential-computing, hypervisor, kvm, sev
Unknown from the sources.
No fix yet, per the sources.
Unverified ownership in Secure Encrypted Virtualization (SEV) firmware could allow a privileged attacker with access to a malicious hypervisor to overwrite guest memory if segmented Reverse Map Table (RMP) is enabled potentially resulting in loss of guest data integrity.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.