staging: gpib: Fix Oops after disconnect in ni_usb
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.13.116.14.26.15In the Linux kernel, the following vulnerability has been resolved:
staging: gpib: Fix Oops after disconnect in ni_usb
If the usb dongle is disconnected subsequent calls to the driver cause a NULL dereference Oops as the bus_interface is set to NULL on disconnect.
This problem was introduced by setting usb_dev from the bus_interface for dev_xxx messages.
Previously bus_interface was checked for NULL only in the the functions directly calling usb_fill_bulk_urb or usb_control_msg.
Check for valid bus_interface on all interface entry points and return -ENODEV if it is NULL.
From the CVE record · Linux
The Linux kernel's staging gpib ni_usb driver can dereference a NULL pointer after its USB dongle is disconnected. Subsequent calls to the driver can trigger a kernel Oops; the input does not specify authentication requirements.
Anyone running a Linux kernel with the staging gpib ni_usb driver should check whether their kernel is affected; no affected versions are specified.