Oval Definition:oval:com.ubuntu.xenial:def:2017114720000000
Revision Date:2017-07-20Version:1
Title:CVE-2017-11472 on Ubuntu 16.04 LTS (xenial) - low.
Description:The acpi_ns_terminate() function in drivers/acpi/acpica/nsutils.c in the Linux kernel before 4.12 does not flush the operand cache and causes a kernel stack dump, which allows local users to obtain sensitive information from kernel memory and bypass the KASLR protection mechanism (in the kernel through 4.9) via a crafted ACPI table. It was discovered that an information disclosure vulnerability existed in the ACPI implementation of the Linux kernel. A local attacker could use this to expose sensitive information (kernel memory addresses).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2017-11472
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.13.0-1005.7').
  • 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.13.0-1002.5').
  • 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.13.0-26.29~16.04.2').
  • 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.13.0-1005.7').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.13.0-1002.5').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.13.0-26.29~16.04.2').
  • 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 package in xenial, is related to the CVE in some way and has been fixed (note: '4.13.0-1008.9').
  • 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.13.0-1005.7').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.13.0-1002.5').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.13.0-26.29~16.04.2').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1088.93').
  • BACK