Bug 1749978 (CVE-2019-15291) - CVE-2019-15291 kernel: Null pointer dereference in the flexcop_usb_probe function in the drivers/media/usb/b2c2/flexcop-usb.c
Summary: CVE-2019-15291 kernel: Null pointer dereference in the flexcop_usb_probe func...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2019-15291
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: 1749991 1807078 1807079 1807080 1807081 1807082
Blocks: 1749993
TreeView+ depends on / blocked
 
Reported: 2019-09-07 01:26 UTC by Pedro Sampaio
Modified: 2021-10-25 09:53 UTC (History)
41 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-10-25 09:53:26 UTC
Embargoed:

Attachments (Terms of Use)

Description Pedro Sampaio 2019-09-07 01:26:58 UTC 
An issue was discovered in the Linux kernel through 5.2.9. There is a NULL pointer dereference caused by a malicious USB device in the flexcop_usb_probe function in the drivers/media/usb/b2c2/flexcop-usb.c driver.

References:

https://syzkaller.appspot.com/bug?id=c0203bd72037d07493f4b7562411e4f5f4553a8f
http://www.openwall.com/lists/oss-security/2019/08/20/2
Comment 1 Pedro Sampaio 2019-09-07 02:34:26 UTC 
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1749991]
Comment 2 Petr Matousek 2020-02-25 15:02:33 UTC 
Mitigation:

As the b2c2-flexcop-usb module will be auto-loaded when required, its use can be disabled by preventing the module from loading with the following instructions:

# echo "install b2c2-flexcop-usb /bin/true" >> /etc/modprobe.d/disable-b2c2-flexcop-usb.conf

The system will need to be restarted if the b2c2-flexcop-usb module is already loaded. In most circumstances, the b2c2-flexcop-usb kernel module will be unable to be unloaded while the device is in use. If the system requires this module to work correctly, this mitigation may not be suitable. If you need further assistance, see KCS article https://access.redhat.com/solutions/41278 or contact Red Hat Global Support Services.
Comment 4 Justin M. Forbes 2020-03-19 14:51:41 UTC 
This was fixed for Fedora with the 5.3.14 stable kernel updates.
Note You need to log in before you can comment on or make changes to this bug.