Skip to content
Fencer Intel
medium 5.5

CVE-2017-5957 json

Stack-based buffer overflow in the vrend_decode_set_framebuffer_state function in vrend_decode.c in virglrenderer before 926b9b3460a48f6454…

published 2017-03-14 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-15026

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 33%
public exploits
0
none known

Summary

Stack-based buffer overflow in the vrend_decode_set_framebuffer_state function in vrend_decode.c in virglrenderer before 926b9b3460a48f6454d8bbe9e44313d86a65447f, as used in Quick Emulator (QEMU), allows a local guest users to cause a denial of service (application crash) via the "nr_cbufs" argument.

Patch / fix

  • virglrenderer_project virglrenderer 0.6.0
  • virglrenderer Debian 14, Debian 13, Debian 12 0.6.0-1

debian advisories DEBIAN-CVE-2017-5957

  • virglrenderer SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2, SLES 12 SP2 +2 more 0.5.0-11.1

suse advisories SUSE-SU-2017:0798-1

  • virglrenderer openSUSE Tumbleweed 0.9.1-1.3

opensuse advisories openSUSE-SU-2024:11499-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-5957 updated cvss 4.4

Virglrenderer: stack overflow in vrend_decode_set_framebuffer_state

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.