CVE-2021-3653

What it actually does

Improper validation of the int_ctl field in the VMCB allows a malicious L1 guest to enable AVIC for an L2 guest, granting the L2 guest direct read/write access to host physical memory pages.

Why it matters to the business

Virtualized environments using affected AMD KVM kernels face risk of complete host system crashes, sensitive data exposure from memory, or full guest-to-host compromise, leading to widespread downtime and potential data breaches in cloud or enterprise virtualization deployments.

How an attack unfolds

An attacker controlling an L1 guest crafts a malicious VMCB structure with manipulated int_ctl bits to enable AVIC for a nested L2 guest. The L2 guest then uses the incorrectly granted AVIC capabilities to access and manipulate host physical memory, enabling crashes, data leaks, or escape to the host.

How to fix it

Upgrade the Linux kernel to version 5.14-rc7 or later on all affected systems. Apply vendor backports for supported distributions such as RHEL and Debian where available. Disable nested virtualization (SVM) on AMD hosts if upgrades cannot be applied immediately.

How to confirm the fix worked

Verify the running kernel version is 5.14-rc7 or newer using uname -r. Test nested guest creation with AVIC-related VMCB fields under controlled conditions to confirm the validation fix prevents unauthorized host memory access.

Typical attack path

1. Gain code execution or control within an L1 guest VM on an affected AMD KVM host
2. Construct and submit a VMCB with invalid int_ctl settings to the KVM hypervisor
3. Trigger nested virtualization to spawn an L2 guest with AVIC enabled
4. Use the resulting host memory access to read/write arbitrary physical pages
5. Escalate to host-level code execution, data exfiltration, or denial of service

How to detect it

Review hypervisor logs for unexpected nested guest creations or VMCB processing anomalies on AMD hosts. Correlate with system crashes or unusual memory access patterns from guest processes. No specific public IOCs are widely documented for this kernel-level flaw.

What your security team should do

• Prioritize kernel upgrades on all AMD KVM hosts within the next patching cycle due to the high CVSS and public exploit availability
• Audit virtualization configurations to identify and isolate workloads using nested SVM
• Monitor vendor advisories for distribution-specific backports and apply them promptly
• Consider compensating controls such as disabling nested virtualization where feasible