Oval Definition:oval:com.ubuntu.xenial:def:2017121930000000
Revision Date:2017-11-22Version:1
Title:CVE-2017-12193 on Ubuntu 16.04 LTS (xenial) - medium.
Description:The assoc_array_insert_into_terminal_node function in lib/assoc_array.c in the Linux kernel before 4.13.11 mishandles node splitting, which allows local users to cause a denial of service (NULL pointer dereference and panic) via a crafted application, as demonstrated by the keyring key type, and key addition and link creation operations. Fan Wu, Haoran Qiu, and Shixiong Zhao discovered that the associative array implementation in the Linux kernel sometimes did not properly handle adding a new entry. A local attacker could use this to cause a denial of service (system crash).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2017-12193
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-103.126').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1043.52').
  • 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 pending 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-1012.17').
  • 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-103.126').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1043.52').
  • 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-1012.17').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1079.87').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1081.86').
  • OR linux-oem package in xenial was vulnerable but has been fixed (note: '4.13.0-1010.11').
  • OR linux-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1079.87').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-103.126').
  • 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-1081.86').
  • BACK