Skip to content- Sources: discussion
- Summary: ETH Zurich's Mior redirects the Platform Security Processor's writes during SEV-SNP startup so part of the Reverse Map Table stays uninitialized, letting a hypervisor enable debugging on a confidential VM, read and write its memory, and forge its attestation measurement. It needs hypervisor and BIOS control plus a PCIe device and was shown on a Zen 5 EPYC 9135. Skyfall, from ETH Zurich and Google, uses Transient Scheduler Attacks to read VM register state cached after a deliberately failed VM start, recovering a disk-encryption key on Zen 3 and Zen 4 chips. AMD tracks them as CVE-2026-0462 and CVE-2026-40671, has SEV firmware and microcode dated August 12, and targets platform firmware for November (Skyfall) and December (Mior).
- Why it matters: Anyone renting confidential VMs on EPYC 7003 through 9005 depends on the cloud provider installing BIOS updates and should check the SNP attestation TCB values AMD lists.
- Background: AMD SEV-SNP encrypts a VM's memory and uses the Reverse Map Table, which records the owner and permissions of every physical page, to keep even the host hypervisor out. Attestation reports signed by the security processor let a guest owner verify which software image booted. Earlier attacks by some of the same researchers, Fabricked and RMPocalypse, also corrupted the RMP at startup, and TSA was first disclosed on 2025-07-08.
- Follow-up: AMD platform firmware for Skyfall in November and for Mior in December, and cloud provider statements.