vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2026-90030

usb: dwc3: clear forceRM when issuing EndTransfer

HIGH
7.8
CVSS Score
Published: September 16, 2026 at 10:33 AM UTC
Updated: October 21, 2026 at 01:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel· Linux
90%
1e43c86d84fb0503e82a143e017f35421498fc1a6.6.376.9ab99c4be945724b032cc55e05c6738fe1d84bf70
Vendor states this is fixed in 0afe5c31612de3d18cc6d16e616da4a48ba1e5a2 (fixed)
Vendor states this is fixed in 9f1e57c484f9edeaaa5a27a03ed985e98496e81d (fixed)
Vendor states this is fixed in b58e6200450d350314db0ecda7d6d1bde3281e80 (fixed)
Vendor states this is fixed in e01408ee52fe5cb2d0b43f47f359336af2b6c316 (fixed)
Vendor states this is fixed in 6.12.112 (unaffected)
Vendor states this is fixed in 6.18.51 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)
Affected range stops below 6.7, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.9 (unaffected)
Vendor states this is fixed in 7.2.5 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (5)

Source: cverecord
https://git.kernel.org/stable/c/0afe5c31612de3d18cc6d16e616da4a48ba1e5a2
Source: cverecord
https://git.kernel.org/stable/c/e01408ee52fe5cb2d0b43f47f359336af2b6c316
Source: cverecord
https://git.kernel.org/stable/c/b58e6200450d350314db0ecda7d6d1bde3281e80
Source: cverecord
https://git.kernel.org/stable/c/9f1e57c484f9edeaaa5a27a03ed985e98496e81d
Source: cverecord
https://git.kernel.org/stable/c/7a50e138fa28e5ba76b11af66ed41cc300c0f2be

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card