# CVE-2026-90030: usb: dwc3: clear forceRM when issuing EndTransfer

> A flaw in the Linux kernel DWC3 USB driver causes SMMU faults and system instability when aborting transfers, requiring a patch to clear the forceRM bit.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-101493, BELL-CVE-2026-90030, DEBIAN-CVE-2026-90030, GHSA-xj76-5wmq-jmw6, UBUNTU-CVE-2026-90030

## What is CVE-2026-90030?

CVE-2026-90030 is a high-severity denial of service vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-90030?


## How do I fix CVE-2026-90030?

Apply the vendor's patch.

## Is CVE-2026-90030 being exploited?

There is no known exploitation of CVE-2026-90030 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90030 and fix it if it is affected.

What it is: CVE-2026-90030 is a high-severity denial of service vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90030 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90030/ (Markdown: https://insights.sbomify.com/CVE-2026-90030/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90030
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90030
- OSV: https://osv.dev/vulnerability/CVE-2026-90030

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90030/
Summaries are generated and may contain mistakes; the official description above is the record.