Renderer crash via texture allocation double free
Published Jan 27, 2020 · Updated Aug 4, 2024
Double free in virglrenderer 0.8.1 and earlier allows local users to crash the renderer by triggering texture allocation failure. The vrend_renderer_resource_allocated_texture failure path frees a resource structure that remains owned and is later freed again by its caller. Low-privileged local access and a forced texture-allocation failure are required; the documented consequence is availability loss only.
Summary
What happened
Double free in virglrenderer 0.8.1 and earlier allows local users to crash the renderer by triggering texture allocation failure. The vrend_renderer_resource_allocated_texture failure path frees a resource structure that remains owned and is later freed again by its caller. Low-privileged local access and a forced texture-allocation failure are required; the documented consequence is availability loss only.
The record
- CVE
- CVE-2020-8003
- Published
- Jan 27, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-415, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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