Bug 1775074 (CVE-2019-19055) - CVE-2019-19055 kernel: A memory leak in the nl80211_get_ftm_responder_stats() function innet/wireless/nl80211.c allows DoS
Summary: CVE-2019-19055 kernel: A memory leak in the nl80211_get_ftm_responder_stats()...
Keywords:
Status: NEW
Alias: CVE-2019-19055
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1829289 1829290 1775116 1776606 1829291 1829292
Blocks: 1775107
TreeView+ depends on / blocked
 
Reported: 2019-11-21 12:06 UTC by msiddiqu
Modified: 2020-05-06 15:44 UTC (History)
47 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the Linux kernel. The Wireless configuration API functionality mishandles resource cleanup in nl80211_get_ftm_responder_stats function. An attacker able to trigger the resource cleanup code path could use this flaw to crash the system. The highest threat from this vulnerability is to system availability.
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description msiddiqu 2019-11-21 12:06:05 UTC
A memory leak in the nl80211_get_ftm_responder_stats() function innet/wireless/nl80211.c allows attackers tocause a denial of service (memory consumption) by triggering nl80211hdr_put() failures

Upstream commit:

https://github.com/torvalds/linux/commit/1399c59fa92984836db90538cf92397fe7caaa57

Comment 1 msiddiqu 2019-11-21 12:19:53 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1775116]

Comment 3 Petr Matousek 2020-04-29 10:53:36 UTC
Statement:

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

Comment 4 Petr Matousek 2020-04-29 10:53:41 UTC
Mitigation:

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


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