Oval Definition:oval:com.ubuntu.xenial:def:2017169110000000
Revision Date:2018-01-31Version:1
Title:CVE-2017-16911 on Ubuntu 16.04 LTS (xenial) - medium.
Description:The vhci_hcd driver in the Linux Kernel before version 4.14.8 and 4.4.114 allows allows local attackers to disclose kernel memory addresses. Successful exploitation requires that a USB device is attached over IP. It was discovered that the USB Virtual Host Controller Interface (VHCI) driver in the Linux kernel contained an information disclosure vulnerability. A physically proximate attacker could use this to expose sensitive information (kernel memory).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2017-16911
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-119.143').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1054.63').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1013.13~16.04.2').
  • OR linux-euclid: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needed 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-1014.14~16.04.1').
  • OR linux-gke: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needed now end-of-life').
  • OR linux-goldfish: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needed now end-of-life').
  • OR linux-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-24.26~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1020.25').
  • 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-119.143').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1054.63').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1013.13~16.04.2').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1014.14~16.04.1').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-24.26~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1020.25').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1086.94').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1088.93').
  • OR linux-oem: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needed now end-of-life').
  • OR linux-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1086.94').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-119.143').
  • OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1013.13~16.04.2').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1014.14~16.04.1').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-24.26~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1088.93').
  • BACK