Oval Definition:oval:com.ubuntu.xenial:def:201691780000000
Revision Date:2016-11-28Version:1
Title:CVE-2016-9178 on Ubuntu 16.04 LTS (xenial) - medium.
Description:The __get_user_asm_ex macro in arch/x86/include/asm/uaccess.h in the Linux kernel before 4.7.5 does not initialize a certain integer variable, which allows local users to obtain sensitive information from kernel stack memory by triggering failure of a get_user_ex call. It was discovered that an information leak existed in __get_user_asm_ex() in the Linux kernel. A local attacker could use this to expose sensitive information.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2016-9178
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-47.68').
  • OR linux-aws package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1001.10').
  • OR linux-azure package in xenial, is related to the CVE in some way and has been fixed (note: '4.11.0-1009.9').
  • OR linux-euclid package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-9019.20').
  • 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, is related to the CVE in some way and has been fixed (note: '4.10.0-1004.4').
  • OR linux-gke package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1003.3').
  • OR linux-goldfish: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'abandoned').
  • OR linux-hwe package in xenial, is related to the CVE in some way and has been fixed (note: '4.8.0-36.36~16.04.1').
  • OR linux-kvm package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1004.9').
  • 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-47.68').
  • OR linux-meta-aws package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1001.10').
  • OR linux-meta-azure package in xenial, is related to the CVE in some way and has been fixed (note: '4.11.0-1009.9').
  • OR linux-meta-gcp package in xenial, is related to the CVE in some way and has been fixed (note: '4.10.0-1004.4').
  • OR linux-meta-hwe package in xenial, is related to the CVE in some way and has been fixed (note: '4.8.0-36.36~16.04.1').
  • OR linux-meta-kvm package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1004.9').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1038.45').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1035.39').
  • 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-1038.45').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-47.68').
  • OR linux-signed-azure package in xenial, is related to the CVE in some way and has been fixed (note: '4.11.0-1009.9').
  • OR linux-signed-gcp package in xenial, is related to the CVE in some way and has been fixed (note: '4.10.0-1004.4').
  • OR linux-signed-hwe package in xenial, is related to the CVE in some way and has been fixed (note: '4.8.0-36.36~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1035.39').
  • BACK