Host process crash via stale virtqueue element
Published Mar 16, 2022 · Updated Aug 3, 2024
Improper resource release in QEMU 6.2.0 and earlier allows guest OS users to crash the host process through a malformed vhost-vsock queue element. vhost_vsock_common_send_transport_reset() frees an invalid element without first detaching it from its virtqueue, leaving the queue's resource accounting inconsistent. Exploitation requires high privileges inside a guest configured with vhost-vsock and can retain memory or terminate that guest's QEMU host process.
Summary
What happened
Improper resource release in QEMU 6.2.0 and earlier allows guest OS users to crash the host process through a malformed vhost-vsock queue element. vhost_vsock_common_send_transport_reset() frees an invalid element without first detaching it from its virtqueue, leaving the queue's resource accounting inconsistent. Exploitation requires high privileges inside a guest configured with vhost-vsock and can retain memory or terminate that guest's QEMU host process.
The record
- CVE
- CVE-2022-26354
- Published
- Mar 16, 2022
- Updated
- Aug 3, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-772, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 16, 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=Affected QEMU versions <= 6.2.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