CVE-2016-10028 json
The virgl_cmd_get_capset function in hw/display/virtio-gpu-3d.c in QEMU (aka Quick Emulator) built with Virtio GPU Device emulator support…
published 2017-02-27 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-1225
- 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 37%
- public exploits
- 0
- none known
Summary
The virgl_cmd_get_capset function in hw/display/virtio-gpu-3d.c in QEMU (aka Quick Emulator) built with Virtio GPU Device emulator support allows local guest OS users to cause a denial of service (out-of-bounds read and process crash) via a VIRTIO_GPU_CMD_GET_CAPSET command with a maximum capabilities size with a value of 0.
Patch / fix
- qemu Debian 14, Debian 13, Debian 12 1:2.10.0-1
debian advisories DEBIAN-CVE-2016-10028
- qemu Ubuntu 16.04 LTS 1:2.5+dfsg-5ubuntu10.11
ubuntu advisories UBUNTU-CVE-2016-10028
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- qemu SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2, SLES 12 SP2 +1 more 2.6.2-41.16.1
- qemu SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2, SLES 12 SP2 +1 more 2.6.2-41.9.1
suse advisories SUSE-SU-2017:1774-1SUSE-SU-2017:0625-1
- qemu openSUSE Tumbleweed 6.1.0-32.1
opensuse advisories openSUSE-SU-2024:11287-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-2016-10028 updated cvss 5.4
Qemu: display: virtio-gpu-3d: OOB access while reading virgl capabilities
-
Red Hat Enterprise Linux 5 kvm, xen Red Hat Enterprise Linux 6 qemu-img, qemu-kvm, qemu-kvm-tools, qemu-guest-agent, qemu-guest-agent-win32 Red Hat Enterprise Linux 7 qemu-img, qemu-kvm, libcacard, qemu-kvm-rhev, qemu-kvm-tools, libcacard-tools, +2 more Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) qemu-kvm-rhev Red Hat Enterprise Linux OpenStack Platform 6 (Juno) qemu-kvm-rhev Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) qemu-img-rhev, qemu-kvm-rhev, libcacard-rhev, qemu-kvm-tools-rhev, libcacard-devel-rhev, libcacard-tools-rhev, +1 morenot affected: vulnerable code not present
+4 more productsfewer
Red Hat OpenStack Platform 8 (Liberty) qemu-img-rhev, qemu-kvm-rhev, libcacard-rhev, qemu-kvm-tools-rhev, libcacard-devel-rhev, libcacard-tools-rhev, +1 more Red Hat OpenStack Platform 9 (Mitaka) qemu-img-rhev, qemu-kvm-rhev, libcacard-rhev, qemu-kvm-tools-rhev, libcacard-devel-rhev, libcacard-tools-rhev, +1 more Red Hat OpenStack Platform 10 (Newton) qemu-img-rhev, qemu-kvm-rhev, qemu-kvm-tools-rhev, qemu-kvm-common-rhev Red Hat OpenStack Platform 11 (Ocata) qemu-kvm-rhev
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.43% chance of exploitation in the next 30 days, higher than 37% 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
-
- CWE-125 Out-of-bounds Read
References
-
lists.gnu.org
/archive/html/qemu-devel/2016-12/msg01903.html
mailing-list, patch, vendor-advisory
-
openwall.com
/lists/oss-security/2016/12/20/1
mailing-list, patch, third-party-advisory
-
openwall.com
/lists/oss-security/2016/12/22/14
mailing-list, patch, third-party-advisory
-
security.gentoo.org
/glsa/201701-49
vendor-advisory, third-party-advisory
- git.qemu-project.org /?p=qemu.git%3Ba=commit%3Bh=abd7f08b2353f43274b785db8c7224f082ef4d31
-
securitytracker.com
/id/1037525
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/94981
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2016-10028
- NVD CVE-2016-10028
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.