Guest-triggered host process crash via unchecked coordinates
Published Mar 3, 2022 · Updated Aug 3, 2024
Out-of-bounds write in QEMU 4.0 through 6.1 ATI VGA emulation allows guest OS users to crash the host QEMU process. The ati_2d_blt() path passes unadjusted destination coordinates from guest MMIO registers to pixman_fill() for PATCOPY, BLACKNESS, and WHITENESS operations, writing beyond video RAM. Exploitation requires a guest configured with the experimental ATI VGA device and interrupts only that guest's emulator process on the host.
Summary
What happened
Out-of-bounds write in QEMU 4.0 through 6.1 ATI VGA emulation allows guest OS users to crash the host QEMU process. The ati_2d_blt() path passes unadjusted destination coordinates from guest MMIO registers to pixman_fill() for PATCOPY, BLACKNESS, and WHITENESS operations, writing beyond video RAM. Exploitation requires a guest configured with the experimental ATI VGA device and interrupts only that guest's emulator process on the host.
The record
- CVE
- CVE-2021-3638
- Published
- Mar 3, 2022
- Updated
- Aug 3, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 3, 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=Affects qemu v4.0 to v6.1
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.
Public exploit references
- ATI VGA MMIO crash reproducerproof of concept · demonstrated
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