usb: dwc3: clear forceRM when issuing EndTransfer (CVE-2026-90030) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-90030

usb: dwc3: clear forceRM when issuing EndTransfer

Answer in brief

CVE-2026-90030 records a Unknown severity vulnerability in usb: dwc3: clear forceRM when issuing EndTransfer. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 16, 2026Updated Sep 16, 2026Source checked Sep 16, 2026First seen by HOL Sep 16, 2026Material review Sep 16, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=1e43c86d84fb0503e82a143e017f35421498fc1a <0afe5c31612de3d18cc6d16e616da4a48ba1e5a2 \|\| >=1e43c86d84fb0503e82a143e017f35421498fc1a <e01408ee52fe5cb2d0b43f47f359336af2b6c316 \|\| >=1e43c86d84fb0503e82a143e017f35421498fc1a <b58e6200450d350314db0ecda7d6d1bde3281e80 \|\| ab99c4be945724b032cc55e05c6738fe1d84bf70 \|\| >=6.6.37 <6.7	0afe5c31612de3d18cc6d16e616da4a48ba1e5a2, e01408ee52fe5cb2d0b43f47f359336af2b6c316, b58e6200450d350314db0ecda7d6d1bde3281e80, 6.7
Linux/Linuxgeneric	6.9	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 0afe5c31612de3d18cc6d16e616da4a48ba1e5a2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 16, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.