Oval Definition:oval:com.ubuntu.xenial:def:2017152990000000
Revision Date:2017-10-14Version:1
Title:CVE-2017-15299 on Ubuntu 16.04 LTS (xenial) - medium.
Description:The KEYS subsystem in the Linux kernel through 4.13.7 mishandles use of add_key for a key that already exists but is uninstantiated, which allows local users to cause a denial of service (NULL pointer dereference and system crash) or possibly have unspecified other impact via a crafted system call. Eric Biggers discovered that the key management subsystem in the Linux kernel did not properly restrict adding a key that already exists but is uninstantiated. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2017-15299
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-101.124').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1041.50').
  • 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 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.13.0-1002.5').
  • OR linux-gke package in xenial was vulnerable but has been fixed (note: '4.4.0-1034.34').
  • 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-1010.15').
  • 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-101.124').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1041.50').
  • 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-1010.15').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1077.85').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1079.84').
  • 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-1077.85').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-101.124').
  • 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-1079.84').
  • BACK