Oval Definition:oval:com.ubuntu.xenial:def:2017108100000000
Revision Date:2017-07-04Version:1
Title:CVE-2017-10810 on Ubuntu 16.04 LTS (xenial) - low.
Description: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. 李强 discovered that the Virtio GPU driver in the Linux kernel did not properly free memory in some situations. A local attacker could use this to cause a denial of service (memory consumption).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2017-10810
Platform(s):Ubuntu 16.04 LTS
Product(s):
Definition Synopsis
  • Ubuntu 16.04 LTS (xenial) is installed.
  • AND Package Information
  • linux package in xenial was vulnerable but has been fixed (note: '4.4.0-89.112').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1028.37').
  • OR linux-azure package in xenial, is related to the CVE in some way and has been fixed (note: '4.11.0-1009.9').
  • OR linux-flo: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'abandoned').
  • OR linux-gcp package in xenial, is related to the CVE in some way and has been fixed (note: '4.10.0-1004.4').
  • OR linux-gke package in xenial was vulnerable but has been fixed (note: '4.4.0-1024.24').
  • OR linux-hwe package in xenial was vulnerable but has been fixed (note: '4.10.0-30.34~16.04.1').
  • OR linux-kvm package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1004.9').
  • OR linux-mako: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'abandoned').
  • OR linux-meta package in xenial was vulnerable but has been fixed (note: '4.4.0-89.112').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1028.37').
  • OR linux-meta-azure package in xenial, is related to the CVE in some way and has been fixed (note: '4.11.0-1009.9').
  • OR linux-meta-gcp package in xenial, is related to the CVE in some way and has been fixed (note: '4.10.0-1004.4').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.10.0-30.34~16.04.1').
  • OR linux-meta-kvm package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1004.9').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1067.75').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1069.74').
  • OR linux-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1067.75').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-89.112').
  • OR linux-signed-azure package in xenial, is related to the CVE in some way and has been fixed (note: '4.11.0-1009.9').
  • OR linux-signed-gcp package in xenial, is related to the CVE in some way and has been fixed (note: '4.10.0-1004.4').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.10.0-30.34~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1069.74').
  • BACK