Oval Definition:oval:com.ubuntu.xenial:def:201710002510000000
Revision Date:2017-09-12Version:1
Title:CVE-2017-1000251 on Ubuntu 16.04 LTS (xenial) - high.
Description:The native Bluetooth stack in the Linux Kernel (BlueZ), starting at the Linux kernel version 2.6.32 and up to and including 4.13.1, are vulnerable to a stack overflow vulnerability in the processing of L2CAP configuration responses resulting in Remote code execution in kernel space. It was discovered that a buffer overflow existed in the Bluetooth stack of the Linux kernel when handling L2CAP configuration responses. A physically proximate attacker could use this to cause a denial of service (system crash).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2017-1000251
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-96.119').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1035.44').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.13.0-1005.7').
  • OR linux-euclid package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-9019.20').
  • 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.10.0-1006.6').
  • OR linux-gke package in xenial was vulnerable but has been fixed (note: '4.4.0-1031.31').
  • OR linux-goldfish: 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-hwe package in xenial was vulnerable but has been fixed (note: '4.10.0-35.39~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1007.12').
  • 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-96.119').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1035.44').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.13.0-1005.7').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.10.0-1006.6').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.10.0-35.39~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1007.12').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1074.82').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1076.81').
  • OR linux-oem package in xenial, is related to the CVE in some way and has been fixed (note: '4.13.0-1008.9').
  • OR linux-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1074.82').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-96.119').
  • OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.13.0-1005.7').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.10.0-1006.6').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.10.0-35.39~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1076.81').
  • BACK