Bug 1759767 (CVE-2019-17075) - CVE-2019-17075 kernel: denial of service in write_tpt_entry in drivers/infiniband/hw/cxgb4/mem.c
Summary: CVE-2019-17075 kernel: denial of service in write_tpt_entry in drivers/infini...
Alias: CVE-2019-17075
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1759768
Blocks: 1759769
TreeView+ depends on / blocked
Reported: 2019-10-09 04:08 UTC by Dhananjay Arunesh
Modified: 2021-02-16 21:18 UTC (History)
46 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A denial of service (DoS) was found in the write_tpt_entry in drivers/infiniband/hw/cxgb4/mem.c in the cxgb4' Chelsio T4/T5 RDMA Driver. Some of the architectures performing the DMA operation directly from the stack variable (instead of the heap) allows an attacker in the network to cause some security threat.
Clone Of:
Last Closed: 2020-04-02 10:31:49 UTC

Attachments (Terms of Use)

Description Dhananjay Arunesh 2019-10-09 04:08:14 UTC
An issue was discovered in write_tpt_entry in drivers/infiniband/hw/cxgb4/mem.c in the Linux kernel. The cxgb4 driver is directly calling dma_map_single (a DMA function) from a stack variable. This could allow an attacker to trigger a Denial of Service, exploitable if this driver is used on an architecture for which this stack/DMA interaction has security relevance.


Comment 1 Dhananjay Arunesh 2019-10-09 04:09:04 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1759768]

Comment 2 Justin M. Forbes 2020-03-19 16:59:07 UTC
This was fixed for Fedora with the 5.3.8 stable kernel updates.

Comment 4 Rohit Keshri 2020-04-02 07:29:46 UTC

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Comment 6 Product Security DevOps Team 2020-04-02 10:31:49 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):


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