Oval Definition:oval:com.ubuntu.xenial:def:2019118150000000
Revision Date:2019-05-08Version:1
Title:CVE-2019-11815 on Ubuntu 16.04 LTS (xenial) - medium.
Description:An issue was discovered in rds_tcp_kill_sock in net/rds/tcp.c in the Linux kernel before 5.0.8. There is a race condition leading to a use-after-free, related to net namespace cleanup. It was discovered that a race condition leading to a use-after-free existed in the Reliable Datagram Sockets (RDS) protocol implementation in the Linux kernel. The RDS protocol is blacklisted by default in Ubuntu. If enabled, a local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code.
Family:unixClass:vulnerability
Status:Reference(s):CVE-2019-11815
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-1051.56').
  • 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-1037.39~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-55.60~16.04.2').
  • 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-1051.56').
  • OR linux-meta-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1037.39~16.04.1').
  • OR linux-meta-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-55.60~16.04.2').
  • 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-1018.20~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-1018.20~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-1051.56').
  • OR linux-signed-gcp package in xenial was vulnerable but has been fixed (note: '4.15.0-1037.39~16.04.1').
  • OR linux-signed-hwe package in xenial was vulnerable but has been fixed (note: '4.15.0-55.60~16.04.2').
  • OR linux-signed-oracle package in xenial was vulnerable but has been fixed (note: '4.15.0-1018.20~16.04.1').
  • OR linux-snapdragon package in xenial was vulnerable but has been fixed (note: '4.4.0-1114.119').
  • BACK