Oval Definition:oval:com.ubuntu.xenial:def:201893630000000
Revision Date:2018-11-06Version:1
Title:CVE-2018-9363 on Ubuntu 16.04 LTS (xenial) - medium.
Description:In the hidp_process_report in bluetooth, there is an integer overflow. This could lead to an out of bounds write with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android Versions: Android kernel Android ID: A-65853588 References: Upstream kernel. It was discovered that an integer overflow existed in the HID Bluetooth implementation in the Linux kernel that could lead to a buffer overwrite. An attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2018-9363
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-138.164').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1070.80').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1031.32~16.04.1').
  • OR linux-euclid: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needed ESM criteria').
  • 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-1024.25~16.04.2').
  • 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-39.42~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1036.42').
  • 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-138.164').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1070.80').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1031.32~16.04.1').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1024.25~16.04.2').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-39.42~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1036.42').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1099.107').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1103.108').
  • OR linux-oem: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needed now end-of-life').
  • OR linux-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1099.107').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-138.164').
  • OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1031.32~16.04.1').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1024.25~16.04.2').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-39.42~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1103.108').
  • BACK