CVE-2026-90030usb: dwc3: clear forceRM when issuing EndTransfer
- 7.8HighCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 35 days later
· 35 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected ab99c4be945724b032cc55e05c6738fe1d84bf70 – < 7a50e138fa28e5ba76b11af66ed41cc300c0f2be
- affected 1e43c86d84fb0503e82a143e017f35421498fc1a – < 9f1e57c484f9edeaaa5a27a03ed985e98496e81d
- affected 1e43c86d84fb0503e82a143e017f35421498fc1a – < 0afe5c31612de3d18cc6d16e616da4a48ba1e5a2
- affected 1e43c86d84fb0503e82a143e017f35421498fc1a – < e01408ee52fe5cb2d0b43f47f359336af2b6c316
- affected 1e43c86d84fb0503e82a143e017f35421498fc1a – < b58e6200450d350314db0ecda7d6d1bde3281e80
- affected 6.6.37 – < 6.6.160
- affected 6.9
- unaffected < 6.9
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.51 – ≤ 6.18.*
- unaffected 7.2.5 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/7a50e138fa28e5ba76b11af66ed41cc300c0f2be (opens in a new tab)
- https://git.kernel.org/stable/c/9f1e57c484f9edeaaa5a27a03ed985e98496e81d (opens in a new tab)
- https://git.kernel.org/stable/c/0afe5c31612de3d18cc6d16e616da4a48ba1e5a2 (opens in a new tab)
- https://git.kernel.org/stable/c/e01408ee52fe5cb2d0b43f47f359336af2b6c316 (opens in a new tab)
- https://git.kernel.org/stable/c/b58e6200450d350314db0ecda7d6d1bde3281e80 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-80638 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90030)Record last updated .