Bug 1783547 (CVE-2019-19535) - CVE-2019-19535 kernel: information leak bug caused by a malicious USB device in the drivers/net/can/usb/peak_usb/pcan_usb_fd.cdriver
Summary: CVE-2019-19535 kernel: information leak bug caused by a malicious USB device...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2019-19535
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: 1783548 1785510 1785511 1785514
Blocks: 1783549
TreeView+ depends on / blocked
 
Reported: 2019-12-13 21:38 UTC by msiddiqu
Modified: 2021-10-25 22:15 UTC (History)
42 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in the Linux kernel’s implementation of the Peak CANBUS USB device driver. An information leak caused by the device could allow a local attacker to possibly gain private information from uninitialized kernel memory.
Clone Of:
Environment:
Last Closed: 2021-10-25 22:15:07 UTC
Embargoed:

Attachments (Terms of Use)

Description msiddiqu 2019-12-13 21:38:45 UTC 
A flaw was found in the linux kernels implementation of the Peak CANBUS usb device driver in the linux kernel. An information leak caused by the device could allow for a local attacker to possibly gain private information from uninitialized kernel memory.

Upstream Patch:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=30a8beeb3042f49d0537b7050fd21b490166a3d9

References: 

https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.2.9
http://www.openwall.com/lists/oss-security/2019/12/03/4
http://seclists.org/oss-sec/2019/q4/115
Comment 1 msiddiqu 2019-12-13 21:39:09 UTC 
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1783548]
Comment 2 Justin M. Forbes 2019-12-16 17:18:30 UTC 
This was fixed for Fedora with the 5.2.9 stable kernel update.
Comment 4 Wade Mealing 2019-12-20 04:44:19 UTC 
This flaw is rated as moderate, its an information leak that only happens once at device creation time, access methods of the information is quite difficult.
Note You need to log in before you can comment on or make changes to this bug.