Guest-to-host escape via oversized SEV-ES string I/O
Published Feb 18, 2022 · Updated Aug 3, 2024
Out-of-bounds access in Linux Kernel 5.10 before 5.15 allows guest OS users to crash the host or escape via a malicious VMGEXIT. In sev_es_string_io(), guest-controlled repetition counts and I/O widths drive a memcpy beyond the one-page vcpu->arch.pio_data buffer. Exploitation requires an AMD KVM host running an SEV-ES guest; the corruption can panic the host and create a guest-to-host code-execution path.
Summary
What happened
Out-of-bounds access in Linux Kernel 5.10 before 5.15 allows guest OS users to crash the host or escape via a malicious VMGEXIT. In sev_es_string_io(), guest-controlled repetition counts and I/O widths drive a memcpy beyond the one-page vcpu->arch.pio_data buffer. Exploitation requires an AMD KVM host running an SEV-ES guest; the corruption can panic the host and create a guest-to-host code-execution path.
The record
- CVE
- CVE-2021-4093
- Published
- Feb 18, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-787, CWE-125, T1499.004, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 18, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=kernel 5.15
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo