Oval Definition:oval:com.ubuntu.xenial:def:2019199220000000
Revision Date:2019-12-22Version:1
Title:CVE-2019-19922 on Ubuntu 16.04 LTS (xenial) - medium.
Description:kernel/sched/fair.c in the Linux kernel before 5.3.9, when cpu.cfs_quota_us is used (e.g., with Kubernetes), allows attackers to cause a denial of service against non-cpu-bound applications by generating a workload that triggers unwanted slice expiration, aka CID-de53fd7aedb1. (In other words, although this slice expiration would typically be seen with benign workloads, it is possible that an attacker could calculate how many stray requests are required to force an entire Kubernetes cluster into a low-performance state caused by slice expiration, and ensure that a DDoS attack sent that number of stray requests. An attack does not affect the stability of the kernel; it only causes mismanagement of application execution.) It was discovered that in some situations the fair scheduler in the Linux kernel did not permit a process to use its full quota time slice. A local attacker could use this to cause a denial of service.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2019-19922
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-1054.56~16.04.1').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1063.68').
  • OR linux-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1049.52').
  • OR linux-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-69.78~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-1054.56~16.04.1').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1063.68').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1049.52').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-69.78~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-1029.32~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-1029.32~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-1063.68').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1049.52').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-69.78~16.04.1').
  • OR linux-signed-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1029.32~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