Bug 1751393 (CVE-2019-16089) - CVE-2019-16089 kernel: Improper return check in nbd_genl_status function in drivers/block/nbd.c
Summary: CVE-2019-16089 kernel: Improper return check in nbd_genl_status function in d...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2019-16089
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1751394 1816335 1816336 1911200
Blocks: 1751395
TreeView+ depends on / blocked
 
Reported: 2019-09-11 22:07 UTC by Pedro Sampaio
Modified: 2021-10-27 10:55 UTC (History)
43 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
An improper return check flaw was found in the Linux kernel’s network block device driver functionality when the user call query to check the status of existing network block devices. This flaw allows a local user to crash the system.
Clone Of:
Environment:
Last Closed: 2021-10-27 10:55:12 UTC

Attachments (Terms of Use)

Description Pedro Sampaio 2019-09-11 22:07:08 UTC 
An issue was discovered in the Linux kernel through 5.2.13. nbd_genl_status in drivers/block/nbd.c does not check the nla_nest_start_noflag return value.

References:

https://lore.kernel.org/patchwork/patch/1106884/
Comment 1 Pedro Sampaio 2019-09-11 22:07:43 UTC 
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1751394]
Comment 3 Alex 2020-03-23 19:37:48 UTC 
Mitigation:

To mitigate this issue, prevent module nbd from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically.
Comment 8 Petr Matousek 2020-03-25 12:16:52 UTC 
Statement:

The impact of this issue is Low, because attack is specific for certain network block device usage and could be triggered only by local user with access to the device (resulting denial-of-service) and attack is complex, because could happen only if specific condition (out of memory) at the moment of the attack is met.
Note You need to log in before you can comment on or make changes to this bug.