CVE-2026-90030usb: dwc3: clear forceRM when issuing EndTransfer
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 19, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 1e43c86d84fb0503e82a143e017f35421498fc1a before 9f1e57c484f9edeaaa5a27a03ed985e98496e81d; 1e43c86d84fb0503e82a143e017f35421498fc1a builds before 0afe5c31612de3d18cc6d16e616da4a48ba1e5a2; from 1e43c86d84fb0503e82a143e017f35421498fc1a before e01408ee52fe5cb2d0b43f47f359336af2b6c316; from 1e43c86d84fb0503e82a143e017f35421498fc1a before b58e6200450d350314db0ecda7d6d1bde3281e80; ab99c4be945724b032cc55e05c6738fe1d84bf70; from 6.6.37 before 6.7 | CNA record |
References
- https://git.kernel.org/stable/c/9f1e57c484f9edeaaa5a27a03ed985e98496e81d
- https://git.kernel.org/stable/c/0afe5c31612de3d18cc6d16e616da4a48ba1e5a2
- https://git.kernel.org/stable/c/e01408ee52fe5cb2d0b43f47f359336af2b6c316
- https://git.kernel.org/stable/c/b58e6200450d350314db0ecda7d6d1bde3281e80
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.