staging: gpib: Fix Oops after disconnect in agilent 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 agilent usb
If the agilent 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 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
After an Agilent USB dongle is disconnected, subsequent calls to its driver can trigger a NULL-pointer dereference and kernel Oops. The input does not specify whether an attacker can trigger those calls or what access or user interaction would be required.
Engineers running Linux kernels with the staging gpib Agilent USB driver should check their systems; affected versions are not specified.