CVE-2020-8003

A double-free vulnerability in vrend_renderer.c in virglrenderer through 0.8.1 allows attackers to cause a denial of service by triggering texture allocation failure, because vrend_renderer_resource_allocated_texture is not an appropriate place for a free.

Published: 2020-01-27 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-8003 is rated Low Risk (35.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.17%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-8003

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-12-09 0.03% 0.17% +0.13%
2 2025-11-21 0.07% 0.03% -0.04%
3 2025-11-18 — 0.07% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-8003

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]
2.1 2.0 LOW
AV:L/AC:L/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 3.9 2.9 [email protected]

Weakness enumeration for CVE-2020-8003

OS Trackers for CVE-2020-8003

vendor priority summary link
alpine medium CVE-2020-8003: 1 source package rows (virglrenderer); 4 state rows across 4 repos (3.10-main, 3.11-main, 3.22-community, edge-community); fixed 0, open 4. https://security.alpinelinux.org/vuln/CVE-2020-8003
debian not yet assigned CVE-2020-8003 not yet assigned priority: Debian including 1 source packages (virglrenderer), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2020-8003
ubuntu low CVE-2020-8003 low priority: Ubuntu including 1 source packages (virglrenderer), 5 status rows across 5 suites (bionic, eoan, trusty, upstream, xenial): DNE 2, not-affected 2, released 1. https://ubuntu.com/security/CVE-2020-8003

Affected software / configurations for CVE-2020-8003

Vendor Product Version Raw CPE
virglrenderer_project virglrenderer <= 0.8.1 cpe:2.3:a:virglrenderer_project:virglrenderer:*:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

References for CVE-2020-8003

cvelogic Threat Intelligence