Host denial of service via unmasked interrupt ID
Published May 13, 2021 · Updated Aug 3, 2024
Out-of-bounds access in QEMU up to 4.2.0 allows guest OS users to crash the host emulator via a crafted interrupt ID. The ARM Generic Interrupt Controller emulator writes the software-generated interrupt ID without masking it to four bits, allowing an oversized index into controller state arrays. Exploitation requires a privileged guest, an aarch64 setup using kernel-irqchip=off, and can terminate the QEMU process; the default kernel-irqchip=on configuration is unaffected.
Summary
What happened
Out-of-bounds access in QEMU up to 4.2.0 allows guest OS users to crash the host emulator via a crafted interrupt ID. The ARM Generic Interrupt Controller emulator writes the software-generated interrupt ID without masking it to four bits, allowing an oversized index into controller state arrays. Exploitation requires a privileged guest, an aarch64 setup using kernel-irqchip=off, and can terminate the QEMU process; the default kernel-irqchip=on configuration is unaffected.
The record
- CVE
- CVE-2021-20221
- Published
- May 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 13, 2021CVE 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=up to, including qemu 4.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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