Oval Definition:oval:com.ubuntu.xenial:def:201710002530000000
Revision Date:2017-10-05Version:1
Title:CVE-2017-1000253 on Ubuntu 16.04 LTS (xenial) - high.
Description:Linux distributions that have not patched their long-term kernels with https://git.kernel.org/linus/a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (committed on April 14, 2015). This kernel vulnerability was fixed in April 2015 by commit a87938b2e246b81b4fb713edb371a9fa3c5c3c86 (backported to Linux 3.10.77 in May 2015), but it was not recognized as a security threat. With CONFIG_ARCH_BINFMT_ELF_RANDOMIZE_PIE enabled, and a normal top-down address allocation strategy, load_elf_binary() will attempt to map a PIE binary into an address range immediately below mm->mmap_base. Unfortunately, load_elf_ binary() does not take account of the need to allocate sufficient space for the entire binary which means that, while the first PT_LOAD segment is mapped below mm->mmap_base, the subsequent PT_LOAD segment(s) end up being mapped above mm->mmap_base into the are that is supposed to be the "gap" between the stack and the binary.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2017-1000253
Platform(s):Ubuntu 16.04 LTS
Product(s):
Definition Synopsis
  • Ubuntu 16.04 LTS (xenial) is installed.
  • AND Package Information
  • linux package in xenial, is related to the CVE in some way and has been fixed (note: '4.2.0-16.19').
  • 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: 'was needed now end-of-life').
  • 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, is related to the CVE in some way and has been fixed (note: '4.2.0-16.19').
  • 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, is related to the CVE in some way and has been fixed (note: '4.2.0-1013.19').
  • OR linux-meta-snapdragon package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1012.12').
  • 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, is related to the CVE in some way and has been fixed (note: '4.2.0-1013.19').
  • OR linux-signed package in xenial, is related to the CVE in some way and has been fixed (note: '4.2.0-16.19').
  • 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, is related to the CVE in some way and has been fixed (note: '4.4.0-1012.12').
  • BACK