CVE-2025-48504 · Infrastructure
NO FIX YET
A flaw in the AMD Secure Encrypted Virtualization (SEV) firmware lets operations run on a resource after it has expired or been released. A malicious hypervisor could use this to manipulate metadata pages, which can break the confidentiality and integrity of guest virtual machine memory.
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.
Affects hosts running AMD EPYC processors with SEV firmware to protect virtual machines; the attacker must already control the hypervisor. Teams running only non-AMD hardware or without confidential-VM workloads can skip it. The sources do not name affected firmware versions.
Not affected if no-sev-guests, non-amd-hardware
Who cares amd, confidential-computing, hypervisor, sev
Unknown from the sources.
No fix yet, per the sources.
Operation on a resource after expiration or release in the Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to manipulate metadata pages potentially resulting in the loss of confidentiality and integrity of guest memory.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/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.