usb: usbtmc: check URB actual_length for interrupt-IN notifications
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ dbf3e7f654c0f06a932b8fcafac78de9d0b81d68 · < 75f6d3da2cc646983f41807ef98851569c12bca9| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
usb: usbtmc: check URB actual_length for interrupt-IN notifications
USBTMC devices can use an optional interrupt endpoint for notification messages. These typically contain two-byte headers indicating the payload format, but the driver does not check if these headers are present before accessing the data buffers. In cases where the URB actual_length is not enough to fit these headers, the driver will either cause an out-of-bounds read, or consume stale leftover data from a previous notification.
Fix by checking if actual_data contains enough bytes for the headers, otherwise resubmit URB to the interrupt endpoint.
From the CVE record · Linux
The Linux kernel USBTMC driver reads interrupt-IN notification headers without checking whether the received data is long enough. A device supplying a short notification can trigger an out-of-bounds read or cause the driver to consume stale data. The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels with the USBTMC driver should check their kernel versions; affected versions are not specified.