usb: mtu3: unmap request DMA on queue failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ df2069acb00569a6299d6e11aa1865eeba463848 · < 8c29d9cfab1c3cf0d0b7fcdf9255597be30aa3e1| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
usb: mtu3: unmap request DMA on queue failure
mtu3_gadget_queue() maps the request before checking whether the QMU GPD ring can accept another transfer. the request is returned with -EAGAIN before it is linked on the endpoint request list if mtu3_prepare_transfer() fails.
Normal completion and dequeue paths unmap requests from mtu3_req_complete(), but this error path never reaches that helper, so the DMA mapping is left active. Unmap the request before returning from the failed queue path.
From the CVE record · Linux
The Linux kernel USB mtu3 driver can leave a request’s DMA mapping active when the transfer ring cannot accept another transfer and queuing fails. The input does not describe an attacker-controlled exploit path, authentication requirements, or user interaction.
Engineers running Linux kernels with the USB mtu3 driver should check their kernel versions; affected versions were not provided.