
Two research attacks made public this week let a malicious server host read data inside AMD SEV-SNP virtual machines (VMs), a feature built to keep the server’s operator out. Both were shown in lab tests on AMD EPYC server processors, and both need control of the host’s hypervisor. The Hacker News reports that Mior also needs control of the server’s BIOS and a PCIe device such as a graphics card. Per The Hacker News, neither AMD advisory says whether the flaws have been used in attacks, and both research teams have published code.
Mior (CVE-2026-0462, CVSS 4.0 score 5.9 in AMD’s advisory) comes from an ETH Zurich team. It targets SEV-SNP while it is starting up: the team redirected writes from the chip’s security co-processor to the memory of a graphics card it controlled, which left part of the table that records who owns each memory page uninitialized. The hypervisor could then rewrite those protections, switch on debugging for a VM that had it disabled and read and write the VM’s memory. The researchers say this worked in all 1,000 attempts across two test runs. In a second test they copied a harmless VM’s software measurement into a malicious VM, so the malicious VM’s attestation reports described the harmless image. It was tested on one EPYC 9135 (Zen 5) chip and worked with the optional ciphertext-hiding feature turned on. The team considers Zen 3 and Zen 4 chips potentially affected but did not test them.
Skyfall (CVE-2026-40671, score 4.9) comes from a team at ETH Zurich and Google and builds on AMD’s Transient Scheduler Attacks. When a hypervisor deliberately makes a VM fail to start, saved VM register state is left behind without the usual cleanup and can be read through timing side channels. The team recovered register values and a disk-encryption key from a test VM, though for the key it modified the test VM’s kernel to pause at the right moment. Memory reads are limited to three fixed cache lines in a targeted page. It was tested on an EPYC 7313 (Zen 3) and on EPYC 9124 and 9334 chips (Zen 4), and the leak was not shown on Zen 5. The IEEE Symposium on Security and Privacy program committee, which accepted the Skyfall paper, said it overlooks what a realistic attack on VMs would need, such as a processor core free of other activity and a VM that does not crash or time out. The Hacker News also reports a related SMM-memory leak tracked as CVE-2026-18448 (rated 5.6) in EDK II firmware, with no patched EDK II version listed as of its writing.
How to check if you’re affected
Affected products are the five AMD EPYC server lines both advisories list: 7003, 8004, 8005, 9004 and 9005. They matter to anyone running SEV-SNP confidential VMs on them. AMD’s Mior advisory lists only SEV-SNP as affected, according to The Hacker News.
- Mior (AMD-SB-3059): SEV firmware dated August 12, 2026 (1.3A.03 for the 7003 series, 1.3A.4 for 8004 and 9004, 1.3A.0A for 8005 and 9005). Platform firmware (MilanPI-SP3_1.0.0.L, GenoaPI_1.0.0.K, TurinPI_1.0.0.C) is a target release planned for December 2026.
- Skyfall (AMD-SB-3061): microcode dated August 12, 2026 for these lines, with platform firmware (MilanPI-SP3_1.0.0.L, Genoa_100J Patch 3, TurinPI_1.0.0.C) targeted for November 2026. The Hacker News adds an Instinct MI300A patch dated September 21 and embedded EPYC fixes due between January and April 2027.
- AMD tells customers to get the BIOS update from their server maker. The advisories do not say whether the firmware or microcode works on its own or only as part of the BIOS update, and they list no workaround. Because the fixes are in the host’s firmware, customers renting confidential VMs depend on their cloud provider to install them; asking your provider which firmware your hosts run is our suggestion, not AMD’s.
- The Mior advisory lists a TCB (trusted computing base) value for SNP attestation next to each fixed firmware version, but, per The Hacker News, it does not say how VM owners should check them.
- The two advisories give the TurinPI_1.0.0.C package different target months, per The Hacker News; check each bulletin and your server maker for the current date.
