Bug 1774991 (CVE-2019-19047) - CVE-2019-19047 kernel: dos in mlx5_fw_fatal_reporter_dump() function in drivers/net/ethernet/mellanox/mlx5/core/health.c
Summary: CVE-2019-19047 kernel: dos in mlx5_fw_fatal_reporter_dump() function in drive...
Alias: CVE-2019-19047
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1724336 1774992 1829237 1829238
Blocks: 1775027
TreeView+ depends on / blocked
Reported: 2019-11-21 11:10 UTC by Dhananjay Arunesh
Modified: 2023-03-24 16:08 UTC (History)
43 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the way the Mellanox 5th generation network adapters (ConnectX series) core driver in the Linux kernel handled resource cleanup in the mlx5_fw_fatal_reporter_dump function. This flaw allows an attacker with the ability to trigger errors in the mlx5_crdump_collect function to crash the system.
Clone Of:
Last Closed: 2021-10-25 22:13:47 UTC

Attachments (Terms of Use)

Description Dhananjay Arunesh 2019-11-21 11:10:54 UTC
A vulnerability was found in Linux Kernel where, a memory leak in the mlx5_fw_fatal_reporter_dump() function in drivers/net/ethernet/mellanox/mlx5/core/health.c allows attackers to cause a denial of service (memory consumption) by triggering mlx5_crdump_collect() failures.


Comment 1 Dhananjay Arunesh 2019-11-21 11:11:28 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1774992]

Comment 2 Justin M. Forbes 2019-11-21 16:34:09 UTC
This was fixed for Fedora with the 5.3.11 stable update.

Comment 5 Petr Matousek 2020-04-29 09:20:37 UTC

In order to mitigate this issue it is possible to prevent the affected code from being loaded by blacklisting the kernel module mlx5_core. For instructions relating to how to blacklist a kernel module refer to: https://access.redhat.com/solutions/41278 .

Comment 6 Petr Matousek 2020-04-29 09:21:15 UTC

This issue is rated as having Low impact because of the preconditions needed to trigger the resource cleanup code path.

Note You need to log in before you can comment on or make changes to this bug.