CVE-2024-36977
usb: dwc3: Wait unconditionally after issuing EndXfer command
We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
usb: dwc3: Wait unconditionally after issuing EndXfer command
In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: Wait unconditionally after issuing EndXfer command Currently all controller IP/revisions except DWC3_usb3 >= 310a wait 1ms unconditionally for ENDXFER completion when IOC is not set. This is because DWC_usb3 controller revisions >= 3.10a supports GUCTL2[14: Rst_actbitlater] bit which allows polling CMDACT bit to know whether ENDXFER command is completed. Consider a case where an IN request was queued, and parallelly soft_disconnect was called (due to ffs_epfile_release). This eventually calls stop_active_transfer with IOC cleared, hence send_gadget_ep_cmd() skips waiting for CMDACT cleared during EndXfer. For DWC3 controllers with revisions >= 310a, we don't forcefully wait for 1ms either, and we proceed by unmapping the requests. If ENDXFER didn't complete by this time, it leads to SMMU faults since the controller would still be accessing those requests. Fix this by ensuring ENDXFER completion by adding 1ms delay in __dwc3_stop_active_transfer() unconditionally.
Reserved 2024-05-30 | Published 2024-06-18 | Updated 2024-12-19 | Assigner Linuxgit.kernel.org/...c/341eb08dbca9eae05308c442fbfab1813a44c97a
git.kernel.org/...c/ec96bcf5f96a7a5c556b0e881ac3e5c3924d542c
git.kernel.org/...c/4a387e032909c6dc2b479452c5bbe9a252057925
git.kernel.org/...c/1ba145f05b5c8f0b1a947a0633b5edff5dd1f1c5
git.kernel.org/...c/1d26ba0944d398f88aaf997bda3544646cf21945
Support options
