Oval Definition:oval:com.ubuntu.xenial:def:2019150300000000
Revision Date:2019-09-13Version:1
Title:CVE-2019-15030 on Ubuntu 16.04 LTS (xenial) - medium.
Description:In the Linux kernel through 5.2.14 on the powerpc platform, a local user can read vector registers of other users' processes via a Facility Unavailable exception. To exploit the venerability, a local user starts a transaction (via the hardware transactional memory instruction tbegin) and then accesses vector registers. At some point, the vector registers will be corrupted with the values from a different local Linux process because of a missing arch/powerpc/kernel/process.c check. It was discovered that the Linux kernel on PowerPC architectures did not properly handle Facility Unavailable exceptions in some situations. A local attacker could use this to expose sensitive information.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2019-15030
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-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1050.52~16.04.1').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1059.64').
  • OR linux-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1044.46').
  • OR linux-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-64.73~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-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-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1050.52~16.04.1').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1059.64').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1044.46').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-64.73~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-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1025.28~16.04.1').
  • 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: 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-1025.28~16.04.1').
  • 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 was vulnerable but has been fixed (note: '4.15.0-1059.64').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1044.46').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-64.73~16.04.1').
  • OR linux-signed-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1025.28~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