CVE-2017-10810 json
Memory leak in the virtio_gpu_object_create function in drivers/gpu/drm/virtio/virtgpu_object.c in the Linux kernel through 4.11.8 allows a…
published 9y ago modified 4mo ago also EUVD-2017-2454
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.1%
- EPSS 4.1% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
Memory leak in the virtio_gpu_object_create function in drivers/gpu/drm/virtio/virtgpu_object.c in the Linux kernel through 4.11.8 allows attackers to cause a denial of service (memory consumption) by triggering object-initialization failures.
Patch / fix
- linux linux_kernel 4.4.77, 4.9.37, 4.11.10
- linux Debian 14, Debian 13, Debian 12 4.11.11-1
debian advisories DEBIAN-CVE-2017-10810
- linux Ubuntu 16.04 LTS 4.4.0-89.112
- linux-aws Ubuntu 16.04 LTS 4.4.0-1028.37
- linux-gke Ubuntu 16.04 LTS 4.4.0-1024.24
- linux-hwe Ubuntu 16.04 LTS 4.10.0-32.36~16.04.1
- linux-raspi2 Ubuntu 16.04 LTS 4.4.0-1067.75
- linux-lts-xenial Ubuntu 14.04 LTS 4.4.0-89.112~14.04.1
- linux-snapdragon Ubuntu 16.04 LTS 4.4.0-1069.74
ubuntu advisories UBUNTU-CVE-2017-10810
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
- drm SLED 12 SP3, SLE Workstation Extension 12 SP3 4.9.33-4.11.1
- kernel-rt SLE Real Time 12 SP2 4.4.88-18.1
- kernel-syms-rt SLE Real Time 12 SP2 4.4.88-18.1
- kernel-rt_debug SLE Real Time 12 SP2 4.4.88-18.1
- kernel-source-rt SLE Real Time 12 SP2 4.4.88-18.1
- kernel-syms SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2, SLES 12 SP2 +1 more 4.4.90-92.45.1
- kernel-source SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2, SLES 12 SP2 +1 more 4.4.90-92.45.1
- kernel-default SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2, SLES 12 SP2 +3 more 4.4.90-92.45.1
suse advisories SUSE-SU-2018:0509-1SUSE-SU-2017:2956-1SUSE-SU-2017:2869-1SUSE-SU-2017:2286-1
Is CVE-2017-10810 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor 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-10810 updated cvss 4.1
Kernel: virtio-gpu: memory leakage while creating gpu object
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 moreaffected: no fix planned “Will not fix”
-
Red Hat Enterprise Linux 5 kernel Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise MRG 2 kernel-rt, mrg-rt-release, kernel-rt-trace, kernel-rt-vanilla, kernel-rt-firmwarenot 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
4.13% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:N/I:N/A:C |
Classification
- Weakness
-
- CWE-772 Missing Release of Resource after Effective Lifetime
- Technology feeds
References
-
github.com
/torvalds/linux/commit/385aee965b4e4c36551c362a334378d2985b722a
patch, third-party-advisory
-
git.kernel.org
/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=385aee965b4e4c36551c362a334378d2985b722a
mailing-list, patch, third-party-advisory
-
lkml.org
/lkml/2017/4/6/668
mailing-list, patch, third-party-advisory
-
debian.org
/security/2017/dsa-3927
vendor-advisory, third-party-advisory
-
securityfocus.com
/bid/99433
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-10810
- NVD CVE-2017-10810
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.