Host denial of service via unreleased GPU resources
Published Jun 2, 2021 · Updated Aug 3, 2024
Memory leaks in QEMU vhost-user-gpu 6.0 and earlier allow guest OS users to exhaust host memory through crafted GPU commands. Resource creation, backing attachment, and unref paths in vhost-user-gpu.c and virgl.c omit buffer or iovec release after errors and repeated operations. Access to the vhost-user GPU device is required, and repeated commands can exhaust host memory or crash the host QEMU process.
Summary
What happened
Memory leaks in QEMU vhost-user-gpu 6.0 and earlier allow guest OS users to exhaust host memory through crafted GPU commands. Resource creation, backing attachment, and unref paths in vhost-user-gpu.c and virgl.c omit buffer or iovec release after errors and repeated operations. Access to the vhost-user GPU device is required, and repeated commands can exhaust host memory or crash the host QEMU process.
The record
- CVE
- CVE-2021-3544
- Published
- Jun 2, 2021
- Updated
- Aug 3, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
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