Guest-triggered process crash via stale SCSI request
Published May 28, 2021 · Updated Aug 4, 2024
NULL pointer dereference in QEMU SCSI emulation before 6.0.0 allows privileged guest OS users to crash the host process. In hw/scsi/esp.c, cancellation clears current_req while buffered data remains, and the next Transfer Information command dereferences that null request. A guest must have privileged access to issue the crafted SCSI command; exploitation interrupts that virtual machine's QEMU process.
Summary
What happened
NULL pointer dereference in QEMU SCSI emulation before 6.0.0 allows privileged guest OS users to crash the host process. In hw/scsi/esp.c, cancellation clears current_req while buffered data remains, and the next Transfer Information command dereferences that null request. A guest must have privileged access to issue the crafted SCSI command; exploitation interrupts that virtual machine's QEMU process.
The record
- CVE
- CVE-2020-35504
- Published
- May 28, 2021
- Updated
- Aug 4, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 28, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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 6.0.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.
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