Oval Definition:oval:com.ubuntu.bionic:def:2018146780000000
Revision Date:2018-07-28Version:1
Title:CVE-2018-14678 on Ubuntu 18.04 LTS (bionic) - medium.
Description:An issue was discovered in the Linux kernel through 4.17.11, as used in Xen through 4.11.x. The xen_failsafe_callback entry point in arch/x86/entry/entry_64.S does not properly maintain RBX, which allows local users to cause a denial of service (uninitialized memory usage and system crash). Within Xen, 64-bit x86 PV Linux guest OS users can trigger a guest OS crash or possibly gain privileges. M. Vefa Bicakci and Andy Lutomirski discovered that the kernel did not properly set up all arguments to an error handler callback used when running as a paravirtualized guest. An unprivileged attacker in a paravirtualized guest VM could use this to cause a denial of service (guest VM crash).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2018-14678
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-47.50').
  • OR linux-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1035.37').
  • OR linux-azure package in bionic was vulnerable but has been fixed (note: '4.18.0-1011.11~18.04.1').
  • OR linux-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1029.31').
  • OR linux-hwe package in bionic, is related to the CVE in some way and has been fixed (note: '4.18.0-13.14~18.04.1').
  • OR linux-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1031.31').
  • OR linux-meta package in bionic was vulnerable but has been fixed (note: '4.15.0-47.50').
  • OR linux-meta-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1035.37').
  • OR linux-meta-azure package in bionic was vulnerable but has been fixed (note: '4.18.0-1011.11~18.04.1').
  • OR linux-meta-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1029.31').
  • OR linux-meta-hwe package in bionic, is related to the CVE in some way and has been fixed (note: '4.18.0-13.14~18.04.1').
  • OR linux-meta-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1031.31').
  • OR linux-meta-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1035.40').
  • OR linux-meta-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1010.12').
  • OR linux-meta-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1033.35').
  • OR linux-meta-snapdragon package in bionic, is related to the CVE in some way and has been fixed (note: '4.4.0-1077.82').
  • OR linux-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1035.40').
  • OR linux-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1010.12').
  • OR linux-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1033.35').
  • OR linux-signed package in bionic was vulnerable but has been fixed (note: '4.15.0-47.50').
  • OR linux-signed-azure package in bionic was vulnerable but has been fixed (note: '4.18.0-1011.11~18.04.1').
  • OR linux-signed-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1029.31').
  • OR linux-signed-hwe package in bionic, is related to the CVE in some way and has been fixed (note: '4.18.0-13.14~18.04.1').
  • OR linux-signed-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1035.40').
  • OR linux-signed-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1010.12').
  • OR linux-snapdragon package in bionic, is related to the CVE in some way and has been fixed (note: '4.4.0-1077.82').
  • BACK