Oval Definition:oval:com.ubuntu.xenial:def:2018187100000000
Revision Date:2018-10-29Version:1
Title:CVE-2018-18710 on Ubuntu 16.04 LTS (xenial) - medium.
Description:An issue was discovered in the Linux kernel through 4.19. An information leak in cdrom_ioctl_select_disc in drivers/cdrom/cdrom.c could be used by local attackers to read kernel memory because a cast from unsigned long to int interferes with bounds checking. This is similar to CVE-2018-10940 and CVE-2018-16658. It was discovered that an integer overflow vulnerability existed in the CDROM driver of the Linux kernel. A local attacker could use this to expose sensitive information (kernel memory).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2018-18710
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-141.167').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1074.84').
  • OR linux-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1031.33~16.04.1').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1036.38~16.04.1').
  • OR linux-euclid: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needs-triage ESM criteria').
  • 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 was vulnerable but has been fixed (note: '4.15.0-1026.27~16.04.1').
  • OR linux-gke: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'end-of-life').
  • OR linux-goldfish: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'end-of-life').
  • OR linux-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-43.46~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1039.45').
  • 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-141.167').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1074.84').
  • OR linux-meta-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1031.33~16.04.1').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1036.38~16.04.1').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1026.27~16.04.1').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-43.46~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1039.45').
  • OR linux-meta-oracle package in xenial, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9~16.04.1').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1102.110').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1106.111').
  • OR linux-oem: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needs-triage now end-of-life').
  • OR linux-oracle package in xenial, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9~16.04.1').
  • OR linux-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1102.110').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-141.167').
  • OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1036.38~16.04.1').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1026.27~16.04.1').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-43.46~16.04.1').
  • OR linux-signed-oracle package in xenial, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1106.111').
  • BACK