Oval Definition:oval:com.ubuntu.bionic:def:2018199850000000
Revision Date:2019-03-21Version:1
Title:CVE-2018-19985 on Ubuntu 18.04 LTS (bionic) - low.
Description:The function hso_get_config_data in drivers/net/usb/hso.c in the Linux kernel through 4.19.8 reads if_num from the USB device (as a u8) and uses it to index a small array, resulting in an object out-of-bounds (OOB) read that potentially allows arbitrary read in the kernel address space. Hui Peng and Mathias Payer discovered that the Option USB High Speed driver in the Linux kernel did not properly validate metadata received from the device. A physically proximate attacker could use this to cause a denial of service (system crash).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2018-19985
Platform(s):Ubuntu 18.04 LTS
Product(s):
Definition Synopsis
  • Ubuntu 18.04 LTS (bionic) is installed.
  • AND Package Information
  • linux package in bionic was vulnerable but has been fixed (note: '4.15.0-60.67').
  • OR linux-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1047.49').
  • OR linux-aws-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1021.24~18.04.1').
  • OR linux-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1014.14~18.04.1').
  • OR linux-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
  • OR linux-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1042.45').
  • OR linux-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
  • OR linux-gke-4.15 package in bionic was vulnerable but has been fixed (note: '4.15.0-1041.43').
  • OR linux-gke-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~18.04.1').
  • OR linux-hwe package in bionic was vulnerable but has been fixed (note: '5.0.0-23.24~18.04.1').
  • OR linux-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1043.43').
  • OR linux-meta package in bionic was vulnerable but has been fixed (note: '4.15.0-60.67').
  • OR linux-meta-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1047.49').
  • OR linux-meta-aws-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1021.24~18.04.1').
  • OR linux-meta-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1014.14~18.04.1').
  • OR linux-meta-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
  • OR linux-meta-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1042.45').
  • OR linux-meta-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
  • OR linux-meta-gke-4.15 package in bionic was vulnerable but has been fixed (note: '4.15.0-1041.43').
  • OR linux-meta-gke-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~18.04.1').
  • OR linux-meta-hwe package in bionic was vulnerable but has been fixed (note: '5.0.0-23.24~18.04.1').
  • OR linux-meta-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1043.43').
  • OR linux-meta-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1056.65').
  • OR linux-meta-oem-osp1 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
  • OR linux-meta-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1022.25').
  • OR linux-meta-oracle-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
  • OR linux-meta-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1044.47').
  • OR linux-meta-raspi2-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1017.19~18.04.1').
  • OR linux-meta-snapdragon package in bionic was vulnerable but has been fixed (note: '4.15.0-1062.69').
  • OR linux-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1056.65').
  • OR linux-oem-osp1 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
  • OR linux-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1022.25').
  • OR linux-oracle-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
  • OR linux-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1044.47').
  • OR linux-raspi2-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1017.19~18.04.1').
  • OR linux-signed package in bionic was vulnerable but has been fixed (note: '4.15.0-60.67').
  • OR linux-signed-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1014.14~18.04.1').
  • OR linux-signed-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
  • OR linux-signed-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1042.45').
  • OR linux-signed-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
  • OR linux-signed-gke-4.15 package in bionic was vulnerable but has been fixed (note: '4.15.0-1041.43').
  • OR linux-signed-gke-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~18.04.1').
  • OR linux-signed-hwe package in bionic was vulnerable but has been fixed (note: '5.0.0-23.24~18.04.1').
  • OR linux-signed-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1056.65').
  • OR linux-signed-oem-osp1 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
  • OR linux-signed-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1022.25').
  • OR linux-signed-oracle-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
  • OR linux-snapdragon package in bionic was vulnerable but has been fixed (note: '4.15.0-1062.69').
  • BACK