Oval Definition:oval:com.ubuntu.xenial:def:201776180000000
Revision Date:2017-04-10Version:1
Title:CVE-2017-7618 on Ubuntu 16.04 LTS (xenial) - medium.
Description:crypto/ahash.c in the Linux kernel through 4.10.9 allows attackers to cause a denial of service (API operation calling its own callback, and infinite recursion) by triggering EBUSY on a full queue. Sabrina Dubroca discovered that the asynchronous cryptographic hash (ahash) implementation in the Linux kernel did not properly handle a full request queue. A local attacker could use this to cause a denial of service (infinite recursion).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2017-7618
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-79.100').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1018.27').
  • OR linux-azure package in xenial, is related to the CVE in some way and has been fixed (note: '4.11.0-1009.9').
  • 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-gcp package in xenial, is related to the CVE in some way and has been fixed (note: '4.10.0-1004.4').
  • OR linux-gke package in xenial was vulnerable but has been fixed (note: '4.4.0-1014.14').
  • OR linux-hwe package in xenial was vulnerable but has been fixed (note: '4.10.0-27.30~16.04.2').
  • OR linux-kvm package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1004.9').
  • OR linux-meta package in xenial was vulnerable but has been fixed (note: '4.4.0-79.100').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1018.27').
  • OR linux-meta-azure package in xenial, is related to the CVE in some way and has been fixed (note: '4.11.0-1009.9').
  • OR linux-meta-gcp package in xenial, is related to the CVE in some way and has been fixed (note: '4.10.0-1004.4').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.10.0-27.30~16.04.2').
  • OR linux-meta-kvm package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1004.9').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1057.64').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1059.63').
  • 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-1057.64').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-79.100').
  • OR linux-signed-azure package in xenial, is related to the CVE in some way and has been fixed (note: '4.11.0-1009.9').
  • OR linux-signed-gcp package in xenial, is related to the CVE in some way and has been fixed (note: '4.10.0-1004.4').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.10.0-27.30~16.04.2').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1059.63').
  • BACK