Oval Definition:oval:com.ubuntu.xenial:def:2017151290000000
Revision Date:2018-01-09Version:1
Title:CVE-2017-15129 on Ubuntu 16.04 LTS (xenial) - medium.
Description:A use-after-free vulnerability was found in network namespaces code affecting the Linux kernel before 4.14.11. The function get_net_ns_by_id() in net/core/net_namespace.c does not check for the net::count value after it has found a peer network in netns_ids idr, which could lead to double free and memory corruption. This vulnerability could allow an unprivileged local user to induce kernel memory corruption on the system, leading to a crash. Due to the nature of the flaw, privilege escalation cannot be fully ruled out, although it is thought to be unlikely. It was discovered that a use-after-free vulnerability existed in the network namespaces implementation in the Linux kernel. 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-15129
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-1014.17').
  • 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-1012.16').
  • 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-hwe package in xenial was vulnerable but has been fixed (note: '4.13.0-38.43~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.13.0-1014.17').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.13.0-1012.16').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.13.0-38.43~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 package in xenial was vulnerable but has been fixed (note: '4.13.0-1022.24').
  • 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-1014.17').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.13.0-1012.16').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.13.0-38.43~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1088.93').
  • BACK