CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's handling of the EndTransfer command in DWC3 USB controllers, specifically when the forceRM bit is incorrectly set to 1. This misconfiguration can lead to active transfers remaining unresolved, causing SMMU faults when subsequent transfers are initiated on the same endpoint. Organizations utilizing affected DWC3 USB controllers should prioritize this issue to ensure compliance with updated programming guidelines and prevent potential system instability.
Original NVD Description
In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: clear forceRM when issuing EndTransfer The forceRM bit of the DEPCMD register controls the behavior of the EndTransfer command used to stop an active transfer. Older DWC3 programming guide revisions recommended setting forceRM=1 when issuing EndTransfer. Newer programming guide revisions recommend issuing EndTransfer with forceRM cleared. With forceRM=1 on DWC_usb31 v2.00a and v2.10a controllers, a transfer aborted through the ep_dequeue path was observed to remain active after EndTransfer completion. A subsequent StartTransfer issued on the same endpoint triggered writes associated with the aborted transfer. This resulted in an SMMU fault because the transfer buffer had already been unmapped during EndTransfer command-completion cleanup. Using forceRM=0 eliminates the issue. Although older DWC3 programming guide revisions recommended setting forceRM=1, no issues are known from using forceRM=0. Clear forceRM when issuing EndTransfer to provide consistent EndTransfer behavior and align with newer programming guide recommendations.