CVE-2026-40670 · Infrastructure
NO FIX YET
AMD Secure Encrypted Virtualization with Secure Nested Paging (SEV-SNP) fails to check for unusual conditions, so a privileged attacker can map MMIO regions over DRAM regions. The result is loss of data integrity for 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.
Affects hosts running AMD EPYC processors with SEV-SNP enabled for confidential virtual machines. The attacker needs privileged access on the host, so ordinary guests and internet users are not the main concern. Teams without SEV-SNP confidential computing can skip it.
Not affected if no-sev-snp, non-amd-hardware
Who cares amd, confidential-computing, hypervisor, sev-snp
Unknown from the sources.
No fix yet, per the sources.
Improper check for unusual or exceptional conditions in AMD Secure Encrypted Virtualization - Secure Nested Paging (SEV-SNP) could allow a privileged attacker to potentially overlap MMIO regions with DRAM regions resulting in loss of 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.
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.