Oval Definition:oval:com.ubuntu.bionic:def:2019159020000000
Revision Date:2019-09-04Version:1
Title:CVE-2019-15902 on Ubuntu 18.04 LTS (bionic) - 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 18.04 LTS
Product(s):
Definition Synopsis
  • Ubuntu 18.04 LTS (bionic) is installed.
  • AND Package Information
  • linux package in bionic was vulnerable but has been fixed (note: '4.15.0-66.75').
  • OR linux-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1052.54').
  • OR linux-aws-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1021.24~18.04.1').
  • OR linux-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1023.24~18.04.1').
  • OR linux-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
  • OR linux-gcp package in bionic was vulnerable but has been fixed (note: '5.0.0-1021.21~18.04.1').
  • OR linux-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
  • OR linux-gke-4.15 package in bionic was vulnerable but has been fixed (note: '4.15.0-1046.49').
  • OR linux-gke-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1023.23~18.04.2').
  • OR linux-gke-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1011.12~18.04.1').
  • OR linux-hwe package in bionic was vulnerable but has been fixed (note: '5.0.0-32.34~18.04.2').
  • OR linux-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1048.48').
  • OR linux-meta package in bionic was vulnerable but has been fixed (note: '4.15.0-66.75').
  • OR linux-meta-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1052.54').
  • OR linux-meta-aws-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1021.24~18.04.1').
  • OR linux-meta-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1023.24~18.04.1').
  • OR linux-meta-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
  • OR linux-meta-gcp package in bionic was vulnerable but has been fixed (note: '5.0.0-1021.21~18.04.1').
  • OR linux-meta-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
  • OR linux-meta-gke-4.15 package in bionic was vulnerable but has been fixed (note: '4.15.0-1046.49').
  • OR linux-meta-gke-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1023.23~18.04.2').
  • OR linux-meta-gke-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1011.12~18.04.1').
  • OR linux-meta-hwe package in bionic was vulnerable but has been fixed (note: '5.0.0-32.34~18.04.2').
  • OR linux-meta-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1048.48').
  • OR linux-meta-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1059.68').
  • OR linux-meta-oem-osp1 package in bionic was vulnerable but has been fixed (note: '5.0.0-1025.28').
  • OR linux-meta-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1027.30').
  • OR linux-meta-oracle-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
  • OR linux-meta-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1049.53').
  • OR linux-meta-raspi2-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1017.19~18.04.1').
  • OR linux-meta-snapdragon package in bionic was vulnerable but has been fixed (note: '4.15.0-1066.73').
  • OR linux-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1059.68').
  • OR linux-oem-osp1 package in bionic was vulnerable but has been fixed (note: '5.0.0-1025.28').
  • OR linux-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1027.30').
  • OR linux-oracle-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
  • OR linux-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1049.53').
  • OR linux-raspi2-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1017.19~18.04.1').
  • OR linux-signed package in bionic was vulnerable but has been fixed (note: '4.15.0-66.75').
  • OR linux-signed-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1023.24~18.04.1').
  • OR linux-signed-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
  • OR linux-signed-gcp package in bionic was vulnerable but has been fixed (note: '5.0.0-1021.21~18.04.1').
  • OR linux-signed-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
  • OR linux-signed-gke-4.15 package in bionic was vulnerable but has been fixed (note: '4.15.0-1046.49').
  • OR linux-signed-gke-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1023.23~18.04.2').
  • OR linux-signed-gke-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1011.12~18.04.1').
  • OR linux-signed-hwe package in bionic was vulnerable but has been fixed (note: '5.0.0-32.34~18.04.2').
  • OR linux-signed-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1059.68').
  • OR linux-signed-oem-osp1 package in bionic was vulnerable but has been fixed (note: '5.0.0-1025.28').
  • OR linux-signed-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1027.30').
  • OR linux-signed-oracle-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
  • OR linux-snapdragon package in bionic was vulnerable but has been fixed (note: '4.15.0-1066.73').
  • BACK