can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d08e973a77d128b25e01a08c34d89593fdf222da · < 7352e1d5932a0e777e39fa4b619801191f57e603| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak
In gs_can_open(), the URBs for USB-in transfers are allocated, added to the parent->rx_submitted anchor and submitted. In the complete callback gs_usb_receive_bulk_callback(), the URB is processed and resubmitted. In gs_can_close() the URBs are freed by calling usb_kill_anchored_urbs(parent->rx_submitted).
However, this does not take into account that the USB framework unanchors the URB before the complete function is called. This means that once an in-URB has been completed, it is no longer anchored and is ultimately not released in gs_can_close().
Fix the memory leak by anchoring the URB in the gs_usb_receive_bulk_callback() to the parent->rx_submitted anchor.
From the CVE record · Linux
The Linux kernel's gs_usb CAN driver can leak USB receive URBs because completed URBs are no longer anchored when the device is closed. The input does not establish whether an attacker can trigger the leak or specify any network, authentication, or user-interaction conditions.
Engineers running Linux kernels with the gs_usb CAN driver should check whether their kernel is affected; affected versions were not provided.