Oval Definition:oval:com.ubuntu.bionic:def:2018146100000000
Revision Date:2018-07-27Version:1
Title:CVE-2018-14610 on Ubuntu 18.04 LTS (bionic) - low.
Description:An issue was discovered in the Linux kernel through 4.17.10. There is out-of-bounds access in write_extent_buffer() when mounting and operating a crafted btrfs image, because of a lack of verification that each block group has a corresponding chunk at mount time, within btrfs_read_block_groups in fs/btrfs/extent-tree.c. Wen Xu and Po-Ning Tseng discovered that btrfs file system implementation in the Linux kernel did not properly validate metadata. An attacker could use this to construct a malicious btrfs image that, when mounted, could cause a denial of service (system crash).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2018-14610
Platform(s):Ubuntu 18.04 LTS
Product(s):
Definition Synopsis
  • Ubuntu 18.04 LTS (bionic) is installed.
  • AND Package Information
  • linux package in bionic was vulnerable but has been fixed (note: '4.15.0-58.64').
  • OR linux-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1047.49').
  • OR linux-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1014.14~18.04.1').
  • OR linux-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1040.42').
  • OR linux-gke-4.15 package in bionic was vulnerable but has been fixed (note: '4.15.0-1040.42').
  • OR linux-gke-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~18.04.1').
  • OR linux-hwe package in bionic was vulnerable but has been fixed (note: '5.0.0-23.24~18.04.1').
  • OR linux-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1042.42').
  • OR linux-meta package in bionic was vulnerable but has been fixed (note: '4.15.0-58.64').
  • OR linux-meta-aws package in bionic was vulnerable but has been fixed (note: '4.15.0-1047.49').
  • OR linux-meta-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1014.14~18.04.1').
  • OR linux-meta-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1040.42').
  • OR linux-meta-gke-4.15 package in bionic was vulnerable but has been fixed (note: '4.15.0-1040.42').
  • OR linux-meta-gke-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~18.04.1').
  • OR linux-meta-hwe package in bionic was vulnerable but has been fixed (note: '5.0.0-23.24~18.04.1').
  • OR linux-meta-kvm package in bionic was vulnerable but has been fixed (note: '4.15.0-1042.42').
  • OR linux-meta-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1050.57').
  • OR linux-meta-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1021.23').
  • OR linux-meta-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1043.46').
  • OR linux-meta-snapdragon package in bionic was vulnerable but has been fixed (note: '4.15.0-1060.66').
  • OR linux-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1050.57').
  • OR linux-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1021.23').
  • OR linux-raspi2 package in bionic was vulnerable but has been fixed (note: '4.15.0-1043.46').
  • OR linux-signed package in bionic was vulnerable but has been fixed (note: '4.15.0-58.64').
  • OR linux-signed-azure package in bionic was vulnerable but has been fixed (note: '5.0.0-1014.14~18.04.1').
  • OR linux-signed-gcp package in bionic was vulnerable but has been fixed (note: '4.15.0-1040.42').
  • OR linux-signed-gke-4.15 package in bionic was vulnerable but has been fixed (note: '4.15.0-1040.42').
  • OR linux-signed-gke-5.0 package in bionic, is related to the CVE in some way and has been fixed (note: '5.0.0-1011.11~18.04.1').
  • OR linux-signed-hwe package in bionic was vulnerable but has been fixed (note: '5.0.0-23.24~18.04.1').
  • OR linux-signed-oem package in bionic was vulnerable but has been fixed (note: '4.15.0-1050.57').
  • OR linux-signed-oracle package in bionic was vulnerable but has been fixed (note: '4.15.0-1021.23').
  • OR linux-snapdragon package in bionic was vulnerable but has been fixed (note: '4.15.0-1060.66').
  • BACK