Oval Definition:oval:com.ubuntu.bionic:def:2019200960000000
Revision Date:2019-12-30Version:1
Title:CVE-2019-20096 on Ubuntu 18.04 LTS (bionic) - medium.
Description:In the Linux kernel before 5.1, there is a memory leak in __feat_register_sp() in net/dccp/feat.c, which may cause denial of service, aka CID-1d3ff0950e2b. It was discovered that the Datagram Congestion Control Protocol (DCCP) implementation in the Linux kernel did not properly deallocate memory in certain error conditions. An attacker could possibly use this to cause a denial of service (kernel memory exhaustion).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2019-20096
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-88.88').
  • OR linux-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1060.62').
  • OR linux-aws-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1025.28').
  • OR linux-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1032.34').
  • OR linux-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
  • OR linux-gcp package in bionic was vulnerable but has been fixed (note: '5.0.0-1031.32').
  • OR linux-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
  • OR linux-gke-4.15 package in bionic was vulnerable but has been fixed (note: '4.15.0-1052.55').
  • OR linux-gke-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1030.31').
  • OR linux-gke-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1011.12~18.04.1').
  • OR linux-hwe package in bionic was vulnerable but has been fixed (note: '5.3.0-26.28~18.04.1').
  • OR linux-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1053.53').
  • OR linux-meta package in bionic was vulnerable but has been fixed (note: '4.15.0-88.88').
  • OR linux-meta-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1060.62').
  • OR linux-meta-aws-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1025.28').
  • OR linux-meta-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1032.34').
  • OR linux-meta-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
  • OR linux-meta-gcp package in bionic was vulnerable but has been fixed (note: '5.0.0-1031.32').
  • OR linux-meta-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
  • OR linux-meta-gke-4.15 package in bionic was vulnerable but has been fixed (note: '4.15.0-1052.55').
  • OR linux-meta-gke-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1030.31').
  • OR linux-meta-gke-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1011.12~18.04.1').
  • OR linux-meta-hwe package in bionic was vulnerable but has been fixed (note: '5.3.0-26.28~18.04.1').
  • OR linux-meta-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1053.53').
  • OR linux-meta-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1073.83').
  • OR linux-meta-oem-osp1 package in bionic was vulnerable but has been fixed (note: '5.0.0-1039.44').
  • OR linux-meta-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1033.36').
  • OR linux-meta-oracle-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1011.16').
  • OR linux-meta-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1055.59').
  • OR linux-meta-raspi2-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1017.19~18.04.1').
  • OR linux-meta-snapdragon package in bionic was vulnerable but has been fixed (note: '4.15.0-1072.79').
  • OR linux-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1073.83').
  • OR linux-oem-osp1 package in bionic was vulnerable but has been fixed (note: '5.0.0-1039.44').
  • OR linux-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1033.36').
  • OR linux-oracle-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1011.16').
  • OR linux-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1055.59').
  • OR linux-raspi2-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1017.19~18.04.1').
  • OR linux-signed package in bionic was vulnerable but has been fixed (note: '4.15.0-88.88').
  • OR linux-signed-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1032.34').
  • OR linux-signed-azure-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1007.8~18.04.1').
  • OR linux-signed-gcp package in bionic was vulnerable but has been fixed (note: '5.0.0-1031.32').
  • OR linux-signed-gcp-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1008.9~18.04.1').
  • OR linux-signed-gke-4.15 package in bionic was vulnerable but has been fixed (note: '4.15.0-1052.55').
  • OR linux-signed-gke-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1030.31').
  • OR linux-signed-gke-5.3 package in bionic, is related to the CVE in some way and has been fixed (note: '5.3.0-1011.12~18.04.1').
  • OR linux-signed-hwe package in bionic was vulnerable but has been fixed (note: '5.3.0-26.28~18.04.1').
  • OR linux-signed-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1073.83').
  • OR linux-signed-oem-osp1 package in bionic was vulnerable but has been fixed (note: '5.0.0-1039.44').
  • OR linux-signed-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1033.36').
  • OR linux-signed-oracle-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1011.16').
  • OR linux-snapdragon package in bionic was vulnerable but has been fixed (note: '4.15.0-1072.79').
  • BACK