usb: dwc3: clear forceRM when issuing EndTransfer
CVE-2026-90030 · published 16 Sept 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-90030?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: ab99c4be945724b032cc55e05c6738fe1d84bf70 to < 7a50e138fa28e5ba76b11af66ed41cc300c0f2be, 1e43c86d84fb0503e82a143e017f35421498fc1a to < 9f1e57c484f9edeaaa5a27a03ed985e98496e81d, 1e43c86d84fb0503e82a143e017f35421498fc1a to < 0afe5c31612de3d18cc6d16e616da4a48ba1e5a2, 1e43c86d84fb0503e82a143e017f35421498fc1a to < e01408ee52fe5cb2d0b43f47f359336af2b6c316
- Linux Linux: 6.9
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/7a50e138fa28e5ba76b11af66ed41cc300c0f2be
- git.kernel.org/stable/c/9f1e57c484f9edeaaa5a27a03ed985e98496e81d
- git.kernel.org/stable/c/0afe5c31612de3d18cc6d16e616da4a48ba1e5a2
- git.kernel.org/stable/c/e01408ee52fe5cb2d0b43f47f359336af2b6c316
- git.kernel.org/stable/c/b58e6200450d350314db0ecda7d6d1bde3281e80
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON