Oval Definition:oval:com.ubuntu.xenial:def:2019159020000000
Revision Date:2019-09-04Version:1
Title:CVE-2019-15902 on Ubuntu 16.04 LTS (xenial) - medium.
Description:A backporting error was discovered in the Linux stable/longterm kernel 4.4.x through 4.4.190, 4.9.x through 4.9.190, 4.14.x through 4.14.141, 4.19.x through 4.19.69, and 5.2.x through 5.2.11. Misuse of the upstream "x86/ptrace: Fix possible spectre-v1 in ptrace_get_debugreg()" commit reintroduced the Spectre vulnerability that it aimed to eliminate. This occurred because the backport process depends on cherry picking specific commits, and because two (correctly ordered) code lines were swapped. Brad Spengler discovered that a Spectre mitigation was improperly implemented in the ptrace susbsystem of the Linux kernel. A local attacker could possibly use this to expose sensitive information.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2019-15902
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-166.195').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1096.107').
  • OR linux-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1052.54~16.04.1').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1061.66').
  • OR linux-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1047.50').
  • OR linux-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-66.75~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1060.67').
  • OR linux-meta package in xenial was vulnerable but has been fixed (note: '4.4.0-166.195').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1096.107').
  • OR linux-meta-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1052.54~16.04.1').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1061.66').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1047.50').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-66.75~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1060.67').
  • OR linux-meta-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1027.30~16.04.1').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1124.133').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1128.136').
  • OR linux-oem: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needs-triage now end-of-life').
  • OR linux-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1027.30~16.04.1').
  • OR linux-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1124.133').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-166.195').
  • OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1061.66').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1047.50').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-66.75~16.04.1').
  • OR linux-signed-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1027.30~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1128.136').
  • BACK