Bug 1743505 (CVE-2019-14763) - CVE-2019-14763 kernel: double-locking error in drivers/usb/dwc3/gadget.c leads to denial of service
Summary: CVE-2019-14763 kernel: double-locking error in drivers/usb/dwc3/gadget.c lead...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2019-14763
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: 1743513
Blocks: 1743516
TreeView+ depends on / blocked
 
Reported: 2019-08-20 07:14 UTC by Dhananjay Arunesh
Modified: 2023-09-25 06:07 UTC (History)
45 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A vulnerability was found in the Linux kernel when using the "Synopsys DesignWare Core SuperSpeed USB 3.0 Controller", where a double-locking error in drivers/usb/dwc3/gadget.c may potentially cause a deadlock with f_hid.
Clone Of:
Environment:
Last Closed: 2019-11-21 11:06:54 UTC
Embargoed:


Attachments (Terms of Use)

Description Dhananjay Arunesh 2019-08-20 07:14:04 UTC
A vulnerability was found in the Linux kernel when using the "Synopsys DesignWare Core SuperSpeed USB 3.0 Controller" , a double-locking error in drivers/usb/dwc3/gadget.c may potentially cause a deadlock with f_hid.

Red Hat Enterprise Linux does not include this source code in its builds by default and is not affected by this flaw.

Reference:

https://www.spinics.net/lists/linux-usb/msg167355.html
https://www.spinics.net/lists/linux-usb/msg167393.html
https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.16.4

Upstream commit:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=c91815b596245fd7da349ecc43c8def670d2269e
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=072684e8c58d17e853f8e8b9f6d9ce2e58d2b036

Comment 1 Dhananjay Arunesh 2019-08-20 07:29:13 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1743513]

Comment 2 Justin M. Forbes 2019-08-20 12:41:07 UTC
This was fixed for Fedora with the 4.16.4 stable kernel update.


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