Oval Definition:oval:com.ubuntu.xenial:def:2019118100000000
Revision Date:2019-05-07Version:1
Title:CVE-2019-11810 on Ubuntu 16.04 LTS (xenial) - low.
Description:An issue was discovered in the Linux kernel before 5.0.7. A NULL pointer dereference can occur when megasas_create_frame_pool() fails in megasas_alloc_cmds() in drivers/scsi/megaraid/megaraid_sas_base.c. This causes a Denial of Service, related to a use-after-free. It was discovered that a null pointer dereference vulnerability existed in the LSI Logic MegaRAID driver in the Linux kernel. A local attacker could use this to cause a denial of service (system crash).
Family:unixClass:vulnerability
Status:Reference(s):CVE-2019-11810
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-150.176').
  • OR linux-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1084.94').
  • OR linux-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1047.49~16.04.1').
  • OR linux-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1056.61').
  • 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-1041.43').
  • 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-60.67~16.04.1').
  • OR linux-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1047.53').
  • 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-150.176').
  • OR linux-meta-aws package in xenial was vulnerable but has been fixed (note: '4.4.0-1084.94').
  • OR linux-meta-aws-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-1047.49~16.04.1').
  • OR linux-meta-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1056.61').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1041.43').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-60.67~16.04.1').
  • OR linux-meta-kvm package in xenial was vulnerable but has been fixed (note: '4.4.0-1047.53').
  • OR linux-meta-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1022.25~16.04.1').
  • OR linux-meta-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1110.118').
  • OR linux-meta-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1114.119').
  • 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-1022.25~16.04.1').
  • OR linux-raspi2 package in xenial was vulnerable but has been fixed (note: '4.4.0-1110.118').
  • OR linux-signed package in xenial was vulnerable but has been fixed (note: '4.4.0-150.176').
  • OR linux-signed-azure package in xenial was vulnerable but has been fixed (note: '4.15.0-1056.61').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1041.43').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-60.67~16.04.1').
  • OR linux-signed-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1022.25~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1114.119').
  • BACK