Oval Definition:oval:com.ubuntu.bionic:def:2019192520000000
Revision Date:2019-11-25Version:1
Title:CVE-2019-19252 on Ubuntu 18.04 LTS (bionic) - medium.
Description:vcs_write in drivers/tty/vt/vc_screen.c in the Linux kernel through 5.3.13 does not prevent write access to vcsu devices, aka CID-0c9acb1af77a. Or Cohen discovered that the virtual console subsystem in the Linux kernel did not properly restrict writes to unimplemented vcsu (unicode) devices. A local attacker could possibly use this to cause a denial of service (system crash) or have other unspecified impacts.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2019-19252
Platform(s):Ubuntu 18.04 LTS
Product(s):
Definition Synopsis
  • Ubuntu 18.04 LTS (bionic) is installed.
  • AND Package Information
  • linux package in bionic, is related to the CVE in some way and has been fixed (note: '4.13.0-16.19').
  • OR linux-aws package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1001.1').
  • OR linux-aws-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1024.27~18.04.1').
  • OR linux-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1029.31~18.04.1').
  • OR linux-azure-5.3 package in bionic was vulnerable but has been fixed (note: '5.3.0-1013.14~18.04.1').
  • OR linux-gcp package in bionic was vulnerable but has been fixed (note: '5.0.0-1029.30~18.04.1').
  • OR linux-gcp-5.3 package in bionic was vulnerable but has been fixed (note: '5.3.0-1012.13~18.04.1').
  • OR linux-gke-4.15 package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1030.32').
  • OR linux-gke-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1029.30~18.04.1').
  • OR linux-gke-5.3 package in bionic is affected. An update containing the fix has been completed and is pending publication (note: '5.3.0-1012.13~18.04.1').
  • OR linux-hwe package in bionic was vulnerable but has been fixed (note: '5.3.0-40.32~18.04.1').
  • OR linux-kvm package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.2').
  • OR linux-meta package in bionic, is related to the CVE in some way and has been fixed (note: '4.13.0-16.19').
  • OR linux-meta-aws package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1001.1').
  • OR linux-meta-aws-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1024.27~18.04.1').
  • OR linux-meta-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1029.31~18.04.1').
  • OR linux-meta-azure-5.3 package in bionic was vulnerable but has been fixed (note: '5.3.0-1013.14~18.04.1').
  • OR linux-meta-gcp package in bionic was vulnerable but has been fixed (note: '5.0.0-1029.30~18.04.1').
  • OR linux-meta-gcp-5.3 package in bionic was vulnerable but has been fixed (note: '5.3.0-1012.13~18.04.1').
  • OR linux-meta-gke-4.15 package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1030.32').
  • OR linux-meta-gke-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1029.30~18.04.1').
  • OR linux-meta-gke-5.3 package in bionic is affected. An update containing the fix has been completed and is pending publication (note: '5.3.0-1012.13~18.04.1').
  • OR linux-meta-hwe package in bionic was vulnerable but has been fixed (note: '5.3.0-40.32~18.04.1').
  • OR linux-meta-kvm package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.2').
  • OR linux-meta-oem package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.3').
  • OR linux-meta-oem-osp1 package in bionic was vulnerable but has been fixed (note: '5.0.0-1037.42').
  • OR linux-meta-oracle package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
  • OR linux-meta-oracle-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1010.15~18.04.1').
  • OR linux-meta-raspi2 package in bionic, is related to the CVE in some way and has been fixed (note: '4.13.0-1005.5').
  • OR linux-meta-raspi2-5.3 package in bionic was vulnerable but has been fixed (note: '5.3.0-1018.20~18.04.1').
  • 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, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.3').
  • OR linux-oem-osp1 package in bionic was vulnerable but has been fixed (note: '5.0.0-1037.42').
  • OR linux-oracle package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
  • OR linux-oracle-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1010.15~18.04.1').
  • OR linux-raspi2 package in bionic, is related to the CVE in some way and has been fixed (note: '4.13.0-1005.5').
  • OR linux-raspi2-5.3 package in bionic was vulnerable but has been fixed (note: '5.3.0-1018.20~18.04.1').
  • OR linux-signed package in bionic, is related to the CVE in some way and has been fixed (note: '4.13.0-16.19').
  • OR linux-signed-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1029.31~18.04.1').
  • OR linux-signed-azure-5.3 package in bionic was vulnerable but has been fixed (note: '5.3.0-1013.14~18.04.1').
  • OR linux-signed-gcp package in bionic was vulnerable but has been fixed (note: '5.0.0-1029.30~18.04.1').
  • OR linux-signed-gcp-5.3 package in bionic was vulnerable but has been fixed (note: '5.3.0-1012.13~18.04.1').
  • OR linux-signed-gke-4.15 package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1030.32').
  • OR linux-signed-gke-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1029.30~18.04.1').
  • OR linux-signed-gke-5.3 package in bionic is affected. An update containing the fix has been completed and is pending publication (note: '5.3.0-1012.13~18.04.1').
  • OR linux-signed-hwe package in bionic was vulnerable but has been fixed (note: '5.3.0-40.32~18.04.1').
  • OR linux-signed-oem package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.3').
  • OR linux-signed-oem-osp1 package in bionic was vulnerable but has been fixed (note: '5.0.0-1037.42').
  • OR linux-signed-oracle package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
  • OR linux-signed-oracle-5.0 package in bionic was vulnerable but has been fixed (note: '5.0.0-1010.15~18.04.1').
  • 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