Oval Definition:oval:com.ubuntu.xenial:def:2017183440000000
Revision Date:2018-07-26Version:1
Title:CVE-2017-18344 on Ubuntu 16.04 LTS (xenial) - high.
Description:The timer_create syscall implementation in kernel/time/posix-timers.c in the Linux kernel before 4.14.8 doesn't properly validate the sigevent->sigev_notify field, which leads to out-of-bounds access in the show_timer function (called when /proc/$PID/timers is read). This allows userspace applications to read arbitrary kernel memory (on a kernel built with CONFIG_POSIX_TIMERS and CONFIG_CHECKPOINT_RESTORE). Andrey Konovalov discovered an out-of-bounds read in the POSIX timers subsystem in the Linux kernel. A local attacker could use this to cause a denial of service (system crash) or expose sensitive information.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2017-18344
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-121.145').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1055.64').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1013.13~16.04.2').
  • OR linux-euclid package in xenial was vulnerable but has been fixed (note: '4.4.0-9029.31').
  • 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.15.0-1014.14~16.04.1').
  • OR linux-gke: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'end-of-life').
  • OR linux-goldfish: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'end-of-life').
  • OR linux-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-24.26~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1021.26').
  • 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-121.145').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1055.64').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1013.13~16.04.2').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1014.14~16.04.1').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-24.26~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1021.26').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1087.95').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1090.95').
  • OR linux-oem: 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-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1087.95').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-121.145').
  • OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1013.13~16.04.2').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1014.14~16.04.1').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-24.26~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1090.95').
  • BACK