Oval Definition:	oval:com.ubuntu.xenial:def:2018168710000000
Revision Date: 2019-07-30 Version: 1 Title: CVE-2018-16871 on Ubuntu 16.04 LTS (xenial) - medium. Description: A flaw was found in the Linux kernel's NFS implementation, all versions 3.x and all versions 4.x up to 4.20. An attacker, who is able to mount an exported NFS filesystem, is able to trigger a null pointer dereference by using an invalid NFS sequence. This can panic the machine and deny access to the NFS server. Any outstanding disk writes to the NFS server will be lost. Family: unix Class: vulnerability Status: Reference(s): CVE-2018-16871 Platform(s): Ubuntu 16.04 LTS Product(s): Definition Synopsis Ubuntu 16.04 LTS (xenial) is installed. AND Package Information linux package in xenial, is related to the CVE in some way and has been fixed (note: '4.2.0-16.19'). OR linux-aws package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1001.10'). OR linux-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1033.35~16.04.1'). OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1040.44'). OR linux-euclid: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needs-triage now end-of-life'). 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-1028.29~16.04.1'). OR linux-gke: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'end-of-life'). OR linux-goldfish: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'end-of-life'). OR linux-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-46.49~16.04.1'). 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-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, is related to the CVE in some way and has been fixed (note: '4.2.0-16.19'). OR linux-meta-aws package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1001.10'). OR linux-meta-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1033.35~16.04.1'). OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1040.44'). OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1028.29~16.04.1'). OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-46.49~16.04.1'). 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-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1009.11~16.04.1'). OR linux-meta-raspi2 package in xenial, is related to the CVE in some way and has been fixed (note: '4.2.0-1013.19'). OR linux-meta-snapdragon package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1012.12'). OR linux-oem: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needs-triage now end-of-life'). OR linux-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1009.11~16.04.1'). OR linux-raspi2 package in xenial, is related to the CVE in some way and has been fixed (note: '4.2.0-1013.19'). OR linux-signed package in xenial, is related to the CVE in some way and has been fixed (note: '4.2.0-16.19'). OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1040.44'). OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1028.29~16.04.1'). OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-46.49~16.04.1'). OR linux-signed-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1009.11~16.04.1'). OR linux-snapdragon package in xenial, is related to the CVE in some way and has been fixed (note: '4.4.0-1012.12').
BACK