Oval Definition:oval:com.ubuntu.xenial:def:201992130000000
Revision Date:2019-03-05Version:1
Title:CVE-2019-9213 on Ubuntu 16.04 LTS (xenial) - medium.
Description:In the Linux kernel before 4.20.14, expand_downwards in mm/mmap.c lacks a check for the mmap minimum address, which makes it easier for attackers to exploit kernel NULL pointer dereferences on non-SMAP platforms. This is related to a capability check for the wrong task. Jann Horn discovered that the mmap implementation in the Linux kernel did not properly check for the mmap minimum address in some situations. A local attacker could use this to assist exploiting a kernel NULL pointer dereference vulnerability.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2019-9213
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 was vulnerable but has been fixed (note: '4.15.0-1035.37~16.04.1').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1041.45').
  • OR linux-euclid: while related to the CVE in some way, a decision has been made to ignore this issue (note: 'was needs-triage 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-1029.31~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-47.50~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 was vulnerable but has been fixed (note: '4.15.0-1035.37~16.04.1').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1041.45').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1029.31~16.04.1').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-47.50~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 was vulnerable but has been fixed (note: '4.15.0-1010.12~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 needs-triage now end-of-life').
  • OR linux-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1010.12~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-1041.45').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1029.31~16.04.1').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-47.50~16.04.1').
  • OR linux-signed-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1010.12~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1110.115').
  • BACK