CVE-2017-6317

Memory leak in the add_shader_program function in vrend_renderer.c in virglrenderer before 0.6.0 allows local guest OS users to cause a denial of service (host memory consumption) via vectors involving the sprog variable.

Published: 2017-03-15 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-6317 is rated Low Risk (36/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.36%). 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-2017-6317

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 2026-06-15 0.06% 0.36% +0.30%
2 2023-03-07 1.03% 0.06% -0.97%
3 2022-02-04 — 1.03% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-6317

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.0 MEDIUM
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/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:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
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.
 2.0 4.0 [email protected]
4.9 2.0 MEDIUM
AV:L/AC:L/Au:N/C:N/I:N/A:C 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:C)
Complete availability impact.
 3.9 6.9 [email protected]

Weakness enumeration for CVE-2017-6317

OS Trackers for CVE-2017-6317

vendor priority summary link
debian not yet assigned CVE-2017-6317 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-2017-6317
gentoo normal CVE-2017-6317: 1 GLSA(s) (201707-06), 1 atom(s) (media-libs/virglrenderer); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2017-6317
suse low CVE-2017-6317 severity low: SUSE including 2 source package names (libvirglrenderer0-0.5.0-11.1, virglrenderer-devel-0.5.0-11.1), 15 product×package rows across 15 product lines (SUSE Linux Enterprise Desktop 12 SP2, SUSE Linux Enterprise Desktop 12 SP3, … (15 product lines)): Fixed 15. https://www.suse.com/security/cve/CVE-2017-6317/
ubuntu medium CVE-2017-6317 medium priority: Ubuntu including 1 source packages (virglrenderer), 9 status rows across 9 suites (artful, bionic, cosmic, precise, trusty, upstream, xenial, yakkety, zesty): DNE 3, ignored 3, not-affected 2, released 1. https://ubuntu.com/security/CVE-2017-6317

Affected software / configurations for CVE-2017-6317

Vendor Product Version Raw CPE
virglrenderer_project virglrenderer <= 0.5.0 cpe:2.3:a:virglrenderer_project:virglrenderer:*:*:*:*:*:*:*:*

References for CVE-2017-6317

cvelogic Threat Intelligence