Guest-triggered host crash via virtio-net use-after-free
Published Mar 23, 2022 · Updated Aug 3, 2024
Use-after-free in QEMU virtio-net before 6.2.0 allows malicious guest drivers to crash QEMU or execute code on the host. The virtio_net_receive_rcu function writes num_buffers after unmapping descriptor scatter-gather elements, leaving freed bounce-buffer memory referenced. A guest must control virtio-net descriptors; exploitation can interrupt the emulator or run code with QEMU process privileges.
Summary
What happened
Use-after-free in QEMU virtio-net before 6.2.0 allows malicious guest drivers to crash QEMU or execute code on the host. The virtio_net_receive_rcu function writes num_buffers after unmapping descriptor scatter-gather elements, leaving freed bounce-buffer memory referenced. A guest must control virtio-net descriptors; exploitation can interrupt the emulator or run code with QEMU process privileges.
The record
- CVE
- CVE-2021-3748
- Published
- Mar 23, 2022
- Updated
- Aug 3, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-416, T1611
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 23, 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 v0.10.0 and above, Fixed In – v6.2.0-rc0 and above.
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.
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