Oval Definition:oval:com.ubuntu.xenial:def:2017143400000000
Revision Date:2017-09-15Version:1
Title:CVE-2017-14340 on Ubuntu 16.04 LTS (xenial) - medium.
Description:The XFS_IS_REALTIME_INODE macro in fs/xfs/xfs_linux.h in the Linux kernel before 4.13.2 does not verify that a filesystem has a realtime device, which allows local users to cause a denial of service (NULL pointer dereference and OOPS) via vectors related to setting an RHINHERIT flag on a directory. Dave Chinner discovered that the XFS filesystem did not enforce that the realtime inode flag was settable only on filesystems on a realtime device. A local attacker could use this to cause a denial of service (system crash).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2017-14340
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-98.121').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1039.48').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.13.0-1005.7').
  • 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.10.0-1008.8').
  • OR linux-gke package in xenial was vulnerable but has been fixed (note: '4.4.0-1033.33').
  • 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-38.42~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1009.14').
  • 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-98.121').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1039.48').
  • 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-1008.8').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.10.0-38.42~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1009.14').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1076.84').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1078.83').
  • 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-1076.84').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-98.121').
  • 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-1008.8').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.10.0-38.42~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1078.83').
  • BACK