CVE-2025-54501 · Infrastructure
NO FIX YET
An internal debug interface has improper access control, so a highly privileged attacker can bypass memory access controls. The result is loss of integrity for SEV-SNP confidential guest memory.
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.
Teams running confidential VMs on AMD SEV-SNP hardware are the ones exposed; the sources do not name the affected firmware or products or say which configurations are vulnerable. Systems without SEV-SNP guests are unlikely to be affected.
Not affected if no-sev-snp
Who cares amd, confidential-computing, sev-snp
Unknown from the sources.
No fix yet, per the sources.
Improper access control on an internal debug interface could allow a high privileged attacker to bypass memory access controls potentially resulting in a loss of SEV-SNP guest memory 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.