Host process crash via uninitialized PVRDMA pointer
Published Feb 24, 2022 · Updated Aug 3, 2024
Uninitialized-pointer access in QEMU before 6.1.0 allows privileged guest OS users to crash the host QEMU process via a PVRDMA register write. In pvrdma_ring_init(), improper initialization of ring->pages can pass an uninitialized pointer to rdma_pci_dma_unmap() while handling PVRDMA_REG_DSRHIGH. The path requires high privileges inside a guest configured with the paravirtual RDMA device, and its bounded impact is interruption of that guest's host process.
Summary
What happened
Uninitialized-pointer access in QEMU before 6.1.0 allows privileged guest OS users to crash the host QEMU process via a PVRDMA register write. In pvrdma_ring_init(), improper initialization of ring->pages can pass an uninitialized pointer to rdma_pci_dma_unmap() while handling PVRDMA_REG_DSRHIGH. The path requires high privileges inside a guest configured with the paravirtual RDMA device, and its bounded impact is interruption of that guest's host process.
The record
- CVE
- CVE-2021-3608
- Published
- Feb 24, 2022
- Updated
- Aug 3, 2024
- Vendor
- QEMU Project
- Product
- QEMU
- Classifications
- CWE-824, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Feb 24, 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.1.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