Guest-triggered process crash via unchecked command pointer
Published Jun 2, 2021 · Updated Aug 4, 2024
NULL pointer dereference in QEMU's AHCI emulation allows privileged guest OS users to crash the associated QEMU process. During DMA buffer commit, ahci_commit_buf dereferences ad->cur_cmd to read and update its status field without first verifying that the command header pointer is non-NULL. The flaw requires AHCI emulation and privileged access inside a guest, and its effect is limited to terminating that guest's QEMU process.
Summary
What happened
NULL pointer dereference in QEMU's AHCI emulation allows privileged guest OS users to crash the associated QEMU process. During DMA buffer commit, ahci_commit_buf dereferences ad->cur_cmd to read and update its status field without first verifying that the command header pointer is non-NULL. The flaw requires AHCI emulation and privileged access inside a guest, and its effect is limited to terminating that guest's QEMU process.
The record
- CVE
- CVE-2019-12067
- Published
- Jun 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 2, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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