| Revision Date: | 2019-11-18 | Version: | 1 | | Title: | CVE-2019-19050 on Ubuntu 16.04 LTS (xenial) - medium. | | Description: | A memory leak in the crypto_reportstat() function in crypto/crypto_user_stat.c in the Linux kernel through 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering crypto_reportstat_alg() failures, aka CID-c03b04dcdba1. It was discovered that the crypto subsystem in the Linux kernel did not properly deallocate memory in certain error conditions. A local attacker could use this to cause a denial of service (kernel memory exhaustion).
| | Family: | unix | Class: | vulnerability | | Status: | | Reference(s): | CVE-2019-19050
| | 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, 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, is related to the CVE in some way and has been fixed (note: '4.11.0-1009.9').
OR linux-gcp package in xenial, is related to the CVE in some way and has been fixed (note: '4.10.0-1004.4').
OR linux-hwe package in xenial, is related to the CVE in some way and has been fixed (note: '4.8.0-36.36~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-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, 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, is related to the CVE in some way and has been fixed (note: '4.11.0-1009.9').
OR linux-meta-gcp package in xenial, is related to the CVE in some way and has been fixed (note: '4.10.0-1004.4').
OR linux-meta-hwe package in xenial, is related to the CVE in some way and has been fixed (note: '4.8.0-36.36~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, 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, 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, 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, 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, is related to the CVE in some way and has been fixed (note: '4.11.0-1009.9').
OR linux-signed-gcp package in xenial, is related to the CVE in some way and has been fixed (note: '4.10.0-1004.4').
OR linux-signed-hwe package in xenial, is related to the CVE in some way and has been fixed (note: '4.8.0-36.36~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, is related to the CVE in some way and has been fixed (note: '4.4.0-1012.12').
|
|