Guest-triggered host process crash via NULL dereference
Published Jan 25, 2022 · Updated Aug 3, 2024
NULL pointer dereference in QEMU before 6.2.0 allows guest OS users to crash the host QEMU process during block mirroring. mirror_iteration() passes a NULL self pointer to mirror_wait_on_conflicts(), which dereferences it when overlapping writes reach the mirrored node. An unprivileged guest must issue writes during an active block-mirror job; the resulting SIGSEGV interrupts that virtual machine and leaves leaked clusters in its disk image.
Summary
What happened
NULL pointer dereference in QEMU before 6.2.0 allows guest OS users to crash the host QEMU process during block mirroring. mirror_iteration() passes a NULL self pointer to mirror_wait_on_conflicts(), which dereferences it when overlapping writes reach the mirrored node. An unprivileged guest must issue writes during an active block-mirror job; the resulting SIGSEGV interrupts that virtual machine and leaves leaked clusters in its disk image.
The record
- CVE
- CVE-2021-4145
- Published
- Jan 25, 2022
- Updated
- Aug 3, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 25, 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=qemu-kvm 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