Bug 1316993 (CVE-2016-3139) - CVE-2016-3139 kernel: Crash on invalid USB device descriptors (wacom driver)
Summary: CVE-2016-3139 kernel: Crash on invalid USB device descriptors (wacom driver)
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2016-3139
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: 1283375 1283377 1317010
Blocks: 1317020
TreeView+ depends on / blocked
 
Reported: 2016-03-11 16:21 UTC by Adam Mariš
Modified: 2021-02-17 04:11 UTC (History)
34 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-15 10:56:13 UTC
Embargoed:

Attachments (Terms of Use)

Description Adam Mariš 2016-03-11 16:21:58 UTC 
Kernel crash occurs when presented a buggy USB device which requires wacom driver, causing null pointer dereference.

Product bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1283375
https://bugzilla.redhat.com/show_bug.cgi?id=1283377
Comment 2 Adam Mariš 2016-03-11 17:04:39 UTC 
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1317010]
Comment 3 Adam Mariš 2016-03-14 10:00:57 UTC 
Public via:

http://seclists.org/bugtraq/2016/Mar/60

CVE request and assignment:

http://seclists.org/oss-sec/2016/q1/606

http://seclists.org/oss-sec/2016/q1/623

Upstream commit: the upstream driver was rebased and does not have this bug, so this bug is rhel7-only and there is no upstream commit.
Comment 4 Vladis Dronov 2016-03-15 10:48:18 UTC 
Acknowledgements:

Name: Ralf Spenneberg (OpenSource Security)
Comment 5 Vladis Dronov 2016-03-15 10:51:51 UTC 
Statement:

This issue affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 5, 6, 7 and MRG-2. This has been rated as having Low security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.
Note You need to log in before you can comment on or make changes to this bug.