xhci: handle isoc Babble and Buffer Overrun events properly
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 04e51901dd44f40a5a385ced897f6bca87d5f40a · < 7c4650ded49e5b88929ecbbb631efb8b0838e811| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
xhci: handle isoc Babble and Buffer Overrun events properly
xHCI 4.9 explicitly forbids assuming that the xHC has released its ownership of a multi-TRB TD when it reports an error on one of the early TRBs. Yet the driver makes such assumption and releases the TD, allowing the remaining TRBs to be freed or overwritten by new TDs.
The xHC should also report completion of the final TRB due to its IOC flag being set by us, regardless of prior errors. This event cannot be recognized if the TD has already been freed earlier, resulting in "Transfer event TRB DMA ptr not part of current TD" error message.
Fix this by reusing the logic for processing isoc Transaction Errors. This also handles hosts which fail to report the final completion.
Fix transfer length reporting on Babble errors. They may be caused by device malfunction, no guarantee that the buffer has been filled.
From the CVE record · Linux
The Linux kernel xHCI driver can release an isochronous transfer descriptor before the controller has finished using it after certain transfer errors. Remaining transfer entries can then be freed or overwritten. The input does not establish an attack path, authentication requirements, or whether user interaction is needed.
Engineers running Linux kernels with the xHCI driver should check their versions; affected versions were not provided.