| Revision Date: | 2019-11-18 | Version: | 1 | | Title: | CVE-2019-19047 on Ubuntu 19.04 (disco) - low. | | Description: | A memory leak in the mlx5_fw_fatal_reporter_dump() function in drivers/net/ethernet/mellanox/mlx5/core/health.c in the Linux kernel before 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering mlx5_crdump_collect() failures, aka CID-c7ed6d0183d5. It was discovered that the Mellanox Technologies ConnectX driver in the Linux kernel did not properly deallocate memory in certain failure 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-19047
| | Platform(s): | Ubuntu 19.04
| Product(s): | | | Definition Synopsis | | Ubuntu 19.04 (disco) is installed. AND Package Information
linux package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-10.11').
OR linux-aws package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1002.3').
OR linux-azure package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1003.3').
OR linux-gcp package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1002.3').
OR linux-kvm package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1003.3').
OR linux-meta package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-10.11').
OR linux-meta-aws package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1002.3').
OR linux-meta-azure package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1003.3').
OR linux-meta-gcp package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1002.3').
OR linux-meta-kvm package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1003.3').
OR linux-meta-oem package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1021.24').
OR linux-meta-oem-osp1 package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
OR linux-meta-oracle package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
OR linux-meta-raspi2 package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1005.7').
OR linux-oem package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1021.24').
OR linux-oem-osp1 package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
OR linux-oracle package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
OR linux-raspi2 package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1005.7').
OR linux-signed package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-10.11').
OR linux-signed-azure package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1003.3').
OR linux-signed-gcp package in disco, is related to the CVE in some way and has been fixed (note: '4.18.0-1002.3').
OR linux-signed-oem package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1021.24').
OR linux-signed-oem-osp1 package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.11').
OR linux-signed-oracle package in disco, is related to the CVE in some way and has been fixed (note: '4.15.0-1007.9').
OR linux-snapdragon package in disco, is related to the CVE in some way and has been fixed (note: '5.0.0-1010.10').
|
|