CVE-2025-54507 · Infrastructure
NO FIX YET
AMD SEV firmware does not properly check input consistency, so a user with administrative privileges can create multiple RMP entries for the same guest physical address. This can result in loss of guest integrity for virtual machines protected by SEV.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Cloud and hypervisor operators running AMD EPYC hosts with SEV enabled for confidential virtual machines. The attacker must already hold administrative privileges on the host, so a team with no SEV-enabled hosts can skip it. The sources do not list affected firmware versions.
Not affected if no-sev-hosts, non-amd-hardware
Who cares amd-epyc, amd-sev, confidential-computing, hypervisor
Unknown from the sources.
No fix yet, per the sources.
Improper validation of consistency within input in AMD SEV (Secure Encrypted Virtualization) firmware could allow an attacker with administrative privileges to create multiple RMP entries for the same guest physical address, potentially resulting in loss of guest 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.
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.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.