Linux kernel buffer overflow in xHCI bounce buffer handling
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
usb: xhci: Fix bounce buffer overflow
High-speed devices with out of spec 1024 byte bulk endpoints exist and are allowed by USB core, but xhci-hcd always sets packet size to 512. The exact nature of these devices isn't documented, commit fb5ee84ea72c ("USB: Accept bulk endpoints with 1024-byte maxpacket") only states that they "don't work with xHCI host controllers", whatever it means.
But somebody (or a malicious device) can try, and then the driver will allocate a 512 byte bounce buffer for this endpoint and may write up to 1024 bytes into it if particular scatter-gather URBs are used, because xhci_align_td() obtains packet size from the descriptor. Fix this.
As a side effect, TRBs will be aligned to the packet size chosen by the driver on all endpoints of all speeds. Alignment serves the xHC, not device, so this is fine. Only out of spec devices are affected anyway.
From the CVE record · Linux
The Linux kernel xHCI driver can allocate a 512-byte bounce buffer for a high-speed USB device with an out-of-spec 1024-byte bulk endpoint. A malicious device may cause the driver to write up to 1024 bytes into that buffer when particular scatter-gather URBs are used; this requires the device to be connected.
Engineers running Linux kernels with the xHCI driver should check their kernel vendor's advisory; affected versions were not provided.