can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 702171adeed3607ee9603ec30ce081411e36ae42 · < 68c62b3e53901846b5f68c5a8bade72a5d9c0b87| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak
Fix similar memory leak as in commit 7352e1d5932a ("can: gs_usb: gs_usb_receive_bulk_callback(): fix URB memory leak").
In ems_usb_open(), the URBs for USB-in transfers are allocated, added to the dev->rx_submitted anchor and submitted. In the complete callback ems_usb_read_bulk_callback(), the URBs are processed and resubmitted. In ems_usb_close() the URBs are freed by calling usb_kill_anchored_urbs(&dev->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 ems_usb_close().
Fix the memory leak by anchoring the URB in the ems_usb_read_bulk_callback() to the dev->rx_submitted anchor.
From the CVE record · Linux
The Linux kernel’s ems_usb driver can leak memory when a USB-in transfer completes because its URB is unanchored and is not freed when the device closes. The input does not specify an attack method, authentication requirements, or whether user interaction is needed.
Engineers running Linux kernels with the ems_usb driver should check whether their kernel includes the fix; affected versions are not specified.