Oval Definition:oval:com.ubuntu.xenial:def:201874800000000
Revision Date:2018-02-25Version:1
Title:CVE-2018-7480 on Ubuntu 16.04 LTS (xenial) - medium.
Description:The blkcg_init_queue function in block/blk-cgroup.c in the Linux kernel before 4.11 allows local users to cause a denial of service (double free) or possibly have unspecified other impact by triggering a creation failure. It was discovered that a double free error existed in the block layer subsystem of the Linux kernel when setting up a request queue. 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-2018-7480
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-127.153').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1060.69').
  • 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-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.13.0-1002.5').
  • 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-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.13.0-26.29~16.04.2').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1026.31').
  • 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-127.153').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1060.69').
  • 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 was vulnerable but has been fixed (note: '4.13.0-1002.5').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.13.0-26.29~16.04.2').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1026.31').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1090.98').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1093.98').
  • 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-1090.98').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-127.153').
  • 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 was vulnerable but has been fixed (note: '4.13.0-1002.5').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.13.0-26.29~16.04.2').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1093.98').
  • BACK