CVE-2025-54506 · Infrastructure
NO FIX YET
A time-of-check to time-of-use race in AMD SEV firmware lets an attacker with administrative privileges bypass security checks on scatter lists. The result can be loss of guest integrity in confidential virtual machines.
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.
Only hosts running AMD SEV confidential virtual machines are exposed, and the attacker must already hold administrative privileges on the host. Teams that do not run SEV-enabled AMD hardware can skip it. The sources do not name affected firmware versions.
Not affected if no-amd-sev, non-admin-only
Who cares amd, confidential-computing, hypervisor, sev
Unknown from the sources.
No fix yet, per the sources.
A time-of-check to time-of-use (TOCTOU) race condition in the AMD SEV Secure Encrypted Virtualization (SEV) firmware could allow an attacker with administrative privileges to bypass security checks on scatter lists, potentially resulting in loss of guest integrity.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:P/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.