Guest-triggered renderer crash via missing compute shader
Published Jan 27, 2020 · Updated Aug 4, 2024
A NULL pointer dereference in vrend_renderer.c in virglrenderer through 0.8.1 allows guest OS users to crash the renderer. Grid-launch command handling dereferences the current compute-shader object without first verifying that the guest supplied a compute shader. Guest OS access is required, and successful exploitation interrupts the renderer without reported confidentiality or integrity impact.
Summary
What happened
A NULL pointer dereference in vrend_renderer.c in virglrenderer through 0.8.1 allows guest OS users to crash the renderer. Grid-launch command handling dereferences the current compute-shader object without first verifying that the guest supplied a compute shader. Guest OS access is required, and successful exploitation interrupts the renderer without reported confidentiality or integrity impact.
The record
- CVE
- CVE-2020-8002
- Published
- Jan 27, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 27, 2020CVE 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