CVEvulnerability
CVE-2026-90030
7.8 HIGH
Official page ↗
- Status
- Received
- Published
- 2026-09-16
- Last modified
- 2026-10-21
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
- 7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
References
- https://git.kernel.org/stable/c/0afe5c31612de3d18cc6d16e616da4a48ba1e5a2 git.kernel.org
- https://git.kernel.org/stable/c/7a50e138fa28e5ba76b11af66ed41cc300c0f2be git.kernel.org
- https://git.kernel.org/stable/c/9f1e57c484f9edeaaa5a27a03ed985e98496e81d git.kernel.org
- https://git.kernel.org/stable/c/b58e6200450d350314db0ecda7d6d1bde3281e80 git.kernel.org
- https://git.kernel.org/stable/c/e01408ee52fe5cb2d0b43f47f359336af2b6c316 git.kernel.org