Oval Definition:	oval:com.ubuntu.xenial:def:201895170000000
Revision Date: 2018-12-07 Version: 1 Title: CVE-2018-9517 on Ubuntu 16.04 LTS (xenial) - medium. Description: In pppol2tp_connect, there is possible memory corruption due to a use after free. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Product: Android. Versions: Android kernel. Android ID: A-38159931. It was discovered that a use-after-free vulnerability existed in the PPP over L2TP implementation in the Linux kernel. A privileged local attacker could use this to possibly execute arbitrary code. Family: unix Class: vulnerability Status: Reference(s): CVE-2018-9517 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-145.171'). OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1079.89'). OR linux-aws-hwe package in xenial, is related to the CVE in some way and has been fixed (note: '4.15.0-1030.31~16.04.1'). 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: '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-24.26~16.04.1'). OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1043.49'). 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-145.171'). OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1079.89'). OR linux-meta-aws-hwe package in xenial, is related to the CVE in some way and has been fixed (note: '4.15.0-1030.31~16.04.1'). 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-1043.49'). OR linux-meta-oracle package in xenial, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9~16.04.1'). OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1106.114'). OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1110.115'). 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-oracle package in xenial, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9~16.04.1'). OR linux-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1106.114'). OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-145.171'). 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-signed-oracle package in xenial, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9~16.04.1'). OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1110.115').
BACK