CVE-2021-4093

What it actually does

Out-of-bounds read and write in the host kernel triggered by a malicious VMGEXIT for string I/O instructions (outs/ins) under SVM_EXIT_IOIO when a guest uses AMD SEV-ES.

Why it matters to the business

A compromised or malicious virtual machine can crash the entire host server or escape to access other virtual machines and host resources, disrupting operations across all workloads on the affected system.

How an attack unfolds

An attacker who controls a guest VM configured for SEV-ES crafts a string I/O instruction that generates an SVM_EXIT_IOIO VMGEXIT; the unhandled exit reason in the KVM AMD SEV-ES code path performs an out-of-bounds access in the host kernel, resulting in a crash or arbitrary read/write that can be leveraged for guest-to-host escape.

How to fix it

Apply the latest security updates for the Linux kernel on all affected distributions (Red Hat Enterprise Linux, Fedora, Ubuntu) that contain the SEV-ES fixes; disable SEV-ES on AMD hosts if patches cannot be applied promptly.

How to confirm the fix worked

Verify that running kernel versions contain the upstream KVM AMD SEV-ES IOIO fixes; confirm no vulnerable code paths remain by inspecting kvm-amd and svm.c after reboot; re-test guest VMs with SEV-ES enabled under load.

Typical attack path

1. Gain control of a guest VM that supports or can enable SEV-ES
2. Issue a malicious string I/O instruction (outs/ins) from the guest
3. Force an SVM_EXIT_IOIO VMGEXIT with crafted parameters
4. Trigger out-of-bounds memory access in the host KVM AMD handler
5. Crash the host or escalate to full host compromise

How to detect it

Search hypervisor and kernel logs for repeated SVM_EXIT_IOIO exits from SEV-ES guests, unexpected host panics in kvm-amd or svm code paths, and any post-crash artifacts indicating guest-initiated IOIO activity.

What your security team should do

• Prioritize kernel updates on all AMD hosts running KVM with SEV-ES
• Isolate or migrate workloads away from unpatched hosts until fixed
• Review hypervisor logs for SVM_EXIT_IOIO entries from untrusted guests
• Consider disabling SEV-ES where not strictly required until patches are deployed