Zero Day Room
Live
Threats

Mior and Skyfall Attacks Breach AMD SEV-SNP Memory Encryption

Two new attacks, Mior and Skyfall, exploit vulnerabilities in AMD's SEV-SNP technology, allowing malicious hosts to read and modify data within protected virtual machines. Firmware and microcode updates from server manufacturers are required to mitigate the threats.

Two new attacks, Mior and Skyfall, exploit vulnerabilities in AMD's SEV-SNP technology, allowing malicious hosts to read...

Two attacks named Mior and Skyfall compromise data confidentiality in AMD SEV-SNP protected virtual machines through hypervisor and firmware manipulation. These attacks allow a malicious host to read data inside virtual machines secured by AMD's hardware-based memory encryption, threatening confidential computing in cloud environments.

Researchers demonstrated both attacks in lab tests on AMD EPYC server processors. SEV-SNP uses hardware-enforced memory encryption and access control to protect VMs from the host's hypervisor. The attacks exploit this protection during the virtual machine startup process.

Mior Attack Requires Firmware and Hardware Control

Mior exploits SEV-SNP's ciphertext hiding by manipulating hypervisor, UEFI BIOS, and PCIe devices to corrupt memory routing protections. The attack requires control of the hypervisor, the UEFI BIOS, and a PCIe device such as a graphics card to execute. It works even with SEV-SNP's ciphertext hiding feature enabled, which is designed to prevent hypervisor access to encrypted VM memory.

The ETH Zurich team behind Mior attacked SEV-SNP during VM start-up by manipulating the Platform Security Processor and the Reverse Map Table. They redirected PSP writes to a controlled graphics card's memory, leaving part of the real RMP uninitialized. This allowed the hypervisor to rewrite the RMP's memory protections. The team enabled debugging on a confidential VM and used PSP debug commands to read and write the VM's memory in all 1,000 test attempts. Mior can also modify a VM's memory and fake the signed attestation report that confirms which software it runs.

Mior was demonstrated on an AMD EPYC 9135 processor with Zen 5 architecture. Zen 3 and Zen 4 chips are potentially affected but were not tested due to BIOS modification requirements. The proof-of-concept code requires a BIOS that leaves memory-routing settings unlocked for testing. Mior affects only SEV-SNP, not earlier SEV and SEV-ES versions, and is separate from earlier attacks like Fabricked and RMPocalypse.

Skyfall Exploits VM Startup Failures for Memory Leak

Skyfall recovers VM state and encryption keys through transient scheduler attacks during VM startup failures, affecting multiple Zen processor generations. It requires a malicious host or hypervisor but no hardware tampering, and needs privileged software on the machine. The attack builds on Transient Scheduler Attacks, a timing-based flaw in AMD processors, by reading cached data left after a VM fails to start.

Skyfall recovered a VM's saved register values and a disk-encryption key in tests. The team used a technique called SEV-Step to step through the VM until the key reached the registers. Skyfall can read VM memory at three fixed cache lines in a targeted page and can also read decrypted microcode updates on all tested chips and recover register values in System Management Mode memory.

Processor ModelArchitectureSkyfall Test Result
EPYC 9135Zen 5Attack not demonstrated (Mior tested)
EPYC 7313Zen 3Leak demonstrated
EPYC 9124Zen 4Leak demonstrated
EPYC 9334Zen 4Leak demonstrated

The IEEE Symposium on Security and Privacy committee noted that Skyfall overlooks realistic attack requirements, including a processor core free of other activity, failing VM starts, high-speed performance-counter reads, and a non-crashing VM.

AMD Provides Patch Timeline and Vendor Guidance

AMD plans firmware updates for Mior in December and microcode for Skyfall in November, with customers advised to obtain fixes from server manufacturers. The company has released initial firmware and microcode updates dated August 12. Updated firmware for Mior is already available, and new microcode has been released for Skyfall.

Host firmware carries the fixes, so cloud providers must install them for customers renting confidential VMs. Supermicro has published a BIOS fix list for H12, H13, and H14 motherboards, requiring a BMC firmware update. The Instinct MI300A accelerator has a Skyfall patch dated September 21. Fixes for embedded EPYC models are due between January and April 2027.

AMD has assigned the following Common Vulnerabilities and Exposures identifiers and severity scores:

CVE IdentifierAttackCVSS 4.0 Score
CVE-2026-0462Mior5.9
CVE-2026-40671Skyfall VM Leak4.9
CVE-2026-18448Skyfall SMM Leak5.6

The EDK II project's advisory for the SMM leak lists no patched version as of today. AMD lists SEV-SNP as affected by Mior and five EPYC server lines for both flaws. The Mior advisory lists TCB values for SNP attestation next to each fixed firmware version but does not explain how VM owners should check them. Neither advisory states whether the flaws have been used in attacks. The researchers said, "We operate in AMD’s threat model defined for SEV-SNP. AMD explicitly distrusts the UEFI, thus an attacker can modify the UEFI."

VM owners should verify firmware versions, TCB values, and BIOS updates with providers before trusting confidential VMs. Customers should obtain BIOS updates directly from their server manufacturer.

Topics

#Threats

Related coverage

More from Threats