Oval Definition:oval:com.ubuntu.bionic:def:202000410000000
Revision Date:2020-03-10Version:1
Title:CVE-2020-0041 on Ubuntu 18.04 LTS (bionic) - medium.
Description:In binder_transaction of binder.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-145988638References: Upstream kernel
Family:unixClass:vulnerability
Status:Reference(s):CVE-2020-0041
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, is related to the CVE in some way and has been fixed (note: '5.0.0-1021.24~18.04.1').
  • OR linux-azure package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.2').
  • OR linux-azure-5.3 package in bionic is affected. An update containing the fix has been completed and is pending publication (note: '5.3.0-1013.14~18.04.1').
  • OR linux-gcp package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1001.1').
  • OR linux-gcp-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-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, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~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 is affected. An update containing the fix has been completed and is pending publication (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, is related to the CVE in some way and has been fixed (note: '5.0.0-1021.24~18.04.1').
  • OR linux-meta-azure package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.2').
  • OR linux-meta-azure-5.3 package in bionic is affected. An update containing the fix has been completed and is pending publication (note: '5.3.0-1013.14~18.04.1').
  • OR linux-meta-gcp package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1001.1').
  • OR linux-meta-gcp-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-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, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~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 is affected. An update containing the fix has been completed and is pending publication (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, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
  • 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, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
  • OR linux-meta-oracle-5.3 package in bionic is affected. An update containing the fix has been completed and is pending publication.
  • 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 is affected. An update containing the fix has been completed and is pending publication (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, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
  • 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, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
  • OR linux-oracle-5.3 package in bionic is affected. An update containing the fix has been completed and is pending publication.
  • 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 is affected. An update containing the fix has been completed and is pending publication (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, is related to the CVE in some way and has been fixed (note: '4.15.0-1002.2').
  • OR linux-signed-azure-5.3 package in bionic is affected. An update containing the fix has been completed and is pending publication (note: '5.3.0-1013.14~18.04.1').
  • OR linux-signed-gcp package in bionic, is related to the CVE in some way and has been fixed (note: '4.15.0-1001.1').
  • OR linux-signed-gcp-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-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, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~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 is affected. An update containing the fix has been completed and is pending publication (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, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
  • 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, is related to the CVE in some way and has been fixed (note: '5.0.0-1007.12~18.04.1').
  • OR linux-signed-oracle-5.3 package in bionic is affected. An update containing the fix has been completed and is pending publication.
  • 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