CVE-2026-90030
Last modified
CVE-2026-90030 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 1e43c86d84fb0503e82a143e017f35421498fc1a, < 0afe5c31612de3d18cc6d16e616da4a48ba1e5a2; >= 1e43c86d84fb0503e82a143e017f35421498fc1a, < e01408ee52fe5cb2d0b43f47f359336af2b6c316; >= 1e43c86d84fb0503e82a143e017f35421498fc1a, < b58e6200450d350314db0ecda7d6d1bde3281e80; ab99c4be945724b032cc55e05c6738fe1d84bf70; >= 6.6.37, < 6.7 |
| Linux | Linux | 6.9 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-90030?
How severe is CVE-2026-90030?
How do I fix CVE-2026-90030?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-90025In the Linux kernel, the following vulnerability has been re…7.7
- CVE-2026-90026In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90027In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90028In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90029In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9003E-LAN Hybrid Recording System developed by TONNET has a SQL …8.7
- CVE-2026-90031In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90032In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-90033In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90034In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90035In the Linux kernel, the following vulnerability has been re…
- CVE-2026-90036In the Linux kernel, the following vulnerability has been re…9.8
Are you affected by CVE-2026-90030?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
