Oval Definition:oval:com.ubuntu.xenial:def:201939000000000
Revision Date:2019-04-25Version:1
Title:CVE-2019-3900 on Ubuntu 16.04 LTS (xenial) - medium.
Description:An infinite loop issue was found in the vhost_net kernel module in Linux Kernel up to and including v5.1-rc6, while handling incoming packets in handle_rx(). It could occur if one end sends packets faster than the other end can process them. A guest user, maybe remote one, could use this flaw to stall the vhost_net kernel thread, resulting in a DoS scenario. Jason Wang discovered that an infinite loop vulnerability existed in the virtio net driver in the Linux kernel. A local attacker in a guest VM could possibly use this to cause a denial of service in the host system.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2019-3900
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-161.189').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1092.103').
  • OR linux-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1047.49~16.04.1').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1056.61').
  • OR linux-euclid: 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-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-1041.43').
  • 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-60.67~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1056.63').
  • 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-161.189').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1092.103').
  • OR linux-meta-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1047.49~16.04.1').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1056.61').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1041.43').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-60.67~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1056.63').
  • OR linux-meta-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1022.25~16.04.1').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1120.129').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1124.130').
  • 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-1022.25~16.04.1').
  • OR linux-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1120.129').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-161.189').
  • OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1056.61').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1041.43').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-60.67~16.04.1').
  • OR linux-signed-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1022.25~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1124.130').
  • BACK