CVE-2026-28249 · Infrastructure
NO FIX YET
AMD Secure Encrypted Virtualization (SEV) firmware fails to keep independent copies of shared state consistent. A malicious hypervisor could affect cache coherency for guest context pages, causing loss of data integrity inside protected 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.
Organizations running AMD EPYC servers with SEV or SEV-SNP confidential virtual machines on a hypervisor. The flaw requires a malicious hypervisor, so teams that do not run SEV guests or trust their hypervisor's operator are lower risk. The sources do not name affected firmware versions.
Not affected if no-sev-guests, non-amd-hardware
Who cares amd, confidential-computing, hypervisor, kvm, linux, sev
Unknown from the sources.
No fix yet, per the sources.
Improper preservation of consistency between independent representations of shared state in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to potentially affect cache coherency for guest context pages resulting in loss of integrity.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:P/PR:N/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.