can: gs_usb: gs_usb_open/close(): fix memory leak
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d08e973a77d128b25e01a08c34d89593fdf222da · < 0e60230bc64355c80abe993d1719fdb318094e20| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
can: gs_usb: gs_usb_open/close(): fix memory leak
The gs_usb driver appears to suffer from a malady common to many USB CAN adapter drivers in that it performs usb_alloc_coherent() to allocate a number of USB request blocks (URBs) for RX, and then later relies on usb_kill_anchored_urbs() to free them, but this doesn't actually free them. As a result, this may be leaking DMA memory that's been used by the driver.
This commit is an adaptation of the techniques found in the esd_usb2 driver where a similar design pattern led to a memory leak. It explicitly frees the RX URBs and their DMA memory via a call to usb_free_coherent(). Since the RX URBs were allocated in the gs_can_open(), we remove them in gs_can_close() rather than in the disconnect function as was done in esd_usb2.
For more information, see the 928150fad41b ("can: esd_usb2: fix memory leak").
From the CVE record · Linux
The Linux kernel's gs_usb driver can leak DMA memory when a USB CAN adapter is opened and closed because RX buffers are not freed. The input does not specify whether an attacker can trigger this remotely or locally, whether authentication is needed, or whether user interaction is required.
Engineers running Linux kernels that use the gs_usb driver should check their kernel version; affected versions are not specified.