Oval Definition:oval:com.ubuntu.xenial:def:201938820000000
Revision Date:2019-04-24Version:1
Title:CVE-2019-3882 on Ubuntu 16.04 LTS (xenial) - low.
Description:A flaw was found in the Linux kernel's vfio interface implementation that permits violation of the user's locked memory limit. If a device is bound to a vfio driver, such as vfio-pci, and the local attacker is administratively granted ownership of the device, it may cause a system memory exhaustion and thus a denial of service (DoS). Versions 3.10, 4.14 and 4.18 are vulnerable. Alex Williamson discovered that the vfio subsystem of the Linux kernel did not properly limit DMA mappings. A local attacker could use this to cause a denial of service (memory exhaustion).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2019-3882
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-148.174').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1083.93').
  • OR linux-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1039.41~16.04.1').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1045.49').
  • OR linux-euclid: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needs-triage ESM criteria').
  • 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-1032.34~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-50.54~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1046.52').
  • 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-148.174').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1083.93').
  • OR linux-meta-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1039.41~16.04.1').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1045.49').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1032.34~16.04.1').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-50.54~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1046.52').
  • OR linux-meta-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1013.15~16.04.1').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1109.117').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1113.118').
  • 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-1013.15~16.04.1').
  • OR linux-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1109.117').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-148.174').
  • OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1045.49').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1032.34~16.04.1').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-50.54~16.04.1').
  • OR linux-signed-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1013.15~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1113.118').
  • BACK