Oval Definition:oval:com.ubuntu.xenial:def:2017180750000000
Revision Date:2018-01-24Version:1
Title:CVE-2017-18075 on Ubuntu 16.04 LTS (xenial) - medium.
Description:crypto/pcrypt.c in the Linux kernel before 4.14.13 mishandles freeing instances, allowing a local user able to access the AF_ALG-based AEAD interface (CONFIG_CRYPTO_USER_API_AEAD) and pcrypt (CONFIG_CRYPTO_PCRYPT) to cause a denial of service (kfree of an incorrect pointer) or possibly have unspecified other impact by executing a crafted sequence of system calls. It was discovered that the parallel cryptography component of the Linux kernel incorrectly freed kernel memory. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2017-18075
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-119.143').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1054.63').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1013.13~16.04.2').
  • 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-1014.14~16.04.1').
  • OR linux-gke: 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.15.0-24.26~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1020.25').
  • 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-119.143').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1054.63').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1013.13~16.04.2').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1014.14~16.04.1').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-24.26~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1020.25').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1086.94').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1088.93').
  • 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-1086.94').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-119.143').
  • OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1013.13~16.04.2').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1014.14~16.04.1').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-24.26~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1088.93').
  • BACK