Guest-to-host code execution via zero-size capability buffer
Published Jun 2, 2021 · Updated Aug 3, 2024
Out-of-bounds write in QEMU 6.0 and earlier allows privileged guest OS users to crash the host QEMU process via a GET_CAPSET command. In virgl_cmd_get_capset(), a zero max_size produces a response allocation with no capability-data space before virgl_renderer_fill_caps writes after it. The vhost-user-gpu device must be configured and controlled from a guest; successful corruption causes a host process crash or code execution with that process's privileges.
Summary
What happened
Out-of-bounds write in QEMU 6.0 and earlier allows privileged guest OS users to crash the host QEMU process via a GET_CAPSET command. In virgl_cmd_get_capset(), a zero max_size produces a response allocation with no capability-data space before virgl_renderer_fill_caps writes after it. The vhost-user-gpu device must be configured and controlled from a guest; successful corruption causes a host process crash or code execution with that process's privileges.
The record
- CVE
- CVE-2021-3546
- Published
- Jun 2, 2021
- Updated
- Aug 3, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-787, T1499.004, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 2, 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=All QEMU versions up to and including 6.0
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