CVE-2026-90030

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 16, 2026

Last Modified

October 3, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
No patch confirmed yet.
generic

usb: dwc3: clear forceRM when issuing EndTransfer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e01408ee52fe5cb2d0b43f47f359336af2b6c316
generic

usb: dwc3: clear forceRM when issuing EndTransfer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b58e6200450d350314db0ecda7d6d1bde3281e80
generic

usb: dwc3: clear forceRM when issuing EndTransfer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0afe5c31612de3d18cc6d16e616da4a48ba1e5a2

Vendor Advisories for CVE-2026-90030(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (183 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 39× in last 7d / 109× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 109 total refreshes for this CVE.

  1. 2026-10-05 03:09 UTCEG score recompute
  2. 2026-10-05 03:09 UTCVendor advisory
  3. 2026-10-05 03:09 UTCGHSA enrichment
  4. 2026-10-04 23:22 UTCEPSS rescore
  5. 2026-10-04 13:56 UTCVendor advisory
  6. 2026-10-04 13:56 UTCGHSA enrichment
  7. 2026-10-04 00:44 UTCEG score recompute
  8. 2026-10-04 00:44 UTCVendor advisory
  9. 2026-10-04 00:44 UTCGHSA enrichment
  10. 2026-10-03 11:33 UTCVendor advisory
  11. 2026-10-03 11:33 UTCGHSA enrichment
  12. 2026-10-03 08:42 UTCVendor advisory
  13. 2026-10-03 08:42 UTCGHSA enrichment
  14. 2026-10-02 19:30 UTCEG score recompute
  15. 2026-10-02 19:30 UTCVendor advisory
  16. 2026-10-02 19:30 UTCGHSA enrichment
  17. 2026-10-02 06:18 UTCEG score recompute
  18. 2026-10-02 06:18 UTCVendor advisory
  19. 2026-10-02 06:18 UTCGHSA enrichment
  20. 2026-10-01 19:51 UTCEPSS rescore
  21. 2026-10-01 17:06 UTCVendor advisory
  22. 2026-10-01 17:06 UTCGHSA enrichment
  23. 2026-10-01 03:18 UTCEG score recompute
  24. 2026-10-01 03:18 UTCVendor advisory
  25. 2026-10-01 03:18 UTCGHSA enrichment
Show 75 more
  1. 2026-09-30 15:04 UTCEPSS rescore
  2. 2026-09-30 14:07 UTCVendor advisory
  3. 2026-09-30 14:06 UTCGHSA enrichment
  4. 2026-09-30 00:54 UTCEG score recompute
  5. 2026-09-30 00:54 UTCVendor advisory
  6. 2026-09-30 00:54 UTCGHSA enrichment
  7. 2026-09-29 08:51 UTCEG score recompute
  8. 2026-09-29 08:51 UTCVendor advisory
  9. 2026-09-29 08:51 UTCGHSA enrichment
  10. 2026-09-28 19:39 UTCEG score recompute
  11. 2026-09-28 19:39 UTCVendor advisory
  12. 2026-09-28 19:39 UTCGHSA enrichment
  13. 2026-09-28 13:52 UTCEPSS rescore
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-28 06:14 UTCVendor advisory
  16. 2026-09-28 06:14 UTCGHSA enrichment
  17. 2026-09-27 17:02 UTCEG score recompute
  18. 2026-09-27 17:02 UTCVendor advisory
  19. 2026-09-27 17:02 UTCGHSA enrichment
  20. 2026-09-27 13:49 UTCEPSS rescore
  21. 2026-09-27 03:51 UTCEG score recompute
  22. 2026-09-27 03:51 UTCVendor advisory
  23. 2026-09-27 03:51 UTCGHSA enrichment
  24. 2026-09-26 15:59 UTCEPSS rescore
  25. 2026-09-26 14:38 UTCVendor advisory
  26. 2026-09-26 14:38 UTCGHSA enrichment
  27. 2026-09-26 01:25 UTCEG score recompute
  28. 2026-09-26 01:25 UTCVendor advisory
  29. 2026-09-26 01:25 UTCGHSA enrichment
  30. 2026-09-25 12:14 UTCVendor advisory
  31. 2026-09-25 12:14 UTCGHSA enrichment
  32. 2026-09-24 23:01 UTCEG score recompute
  33. 2026-09-24 23:01 UTCVendor advisory
  34. 2026-09-24 23:01 UTCGHSA enrichment
  35. 2026-09-24 14:04 UTCEPSS rescore
  36. 2026-09-24 09:16 UTCVendor advisory
  37. 2026-09-24 09:16 UTCGHSA enrichment
  38. 2026-09-23 20:04 UTCEG score recompute
  39. 2026-09-23 20:04 UTCVendor advisory
  40. 2026-09-23 20:04 UTCGHSA enrichment
  41. 2026-09-23 17:54 UTCEPSS rescore
  42. 2026-09-23 06:53 UTCVendor advisory
  43. 2026-09-23 06:53 UTCGHSA enrichment
  44. 2026-09-22 17:41 UTCEG score recompute
  45. 2026-09-22 17:41 UTCVendor advisory
  46. 2026-09-22 17:41 UTCGHSA enrichment
  47. 2026-09-22 16:01 UTCEPSS rescore
  48. 2026-09-22 04:24 UTCEG score recompute
  49. 2026-09-22 04:24 UTCVendor advisory
  50. 2026-09-22 04:24 UTCGHSA enrichment
  51. 2026-09-21 21:09 UTCEPSS rescore
  52. 2026-09-21 15:13 UTCVendor advisory
  53. 2026-09-21 15:13 UTCGHSA enrichment
  54. 2026-09-21 02:01 UTCEG score recompute
  55. 2026-09-21 02:01 UTCVendor advisory
  56. 2026-09-21 02:01 UTCGHSA enrichment
  57. 2026-09-20 20:16 UTCEPSS rescore
  58. 2026-09-20 12:49 UTCVendor advisory
  59. 2026-09-20 12:49 UTCGHSA enrichment
  60. 2026-09-19 23:37 UTCEG score recompute
  61. 2026-09-19 23:37 UTCVendor advisory
  62. 2026-09-19 23:37 UTCGHSA enrichment
  63. 2026-09-19 10:25 UTCVendor advisory
  64. 2026-09-19 10:25 UTCGHSA enrichment
  65. 2026-09-18 21:14 UTCEG score recompute
  66. 2026-09-18 21:14 UTCVendor advisory
  67. 2026-09-18 21:14 UTCGHSA enrichment
  68. 2026-09-18 19:28 UTCEPSS rescore
  69. 2026-09-18 07:32 UTCEG score recompute
  70. 2026-09-18 07:32 UTCVendor advisory
  71. 2026-09-18 07:32 UTCGHSA enrichment
  72. 2026-09-17 19:32 UTCEPSS rescore
  73. 2026-09-17 18:19 UTCVendor advisory
  74. 2026-09-17 18:19 UTCGHSA enrichment
  75. 2026-09-17 04:33 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-90030?
CVE-2026-90030 is a high vulnerability published on September 16, 2026. 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…
When was CVE-2026-90030 disclosed?
CVE-2026-90030 was first published on September 16, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90030 actively exploited?
CVE-2026-90030 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90030?
CVE-2026-90030 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90030?
No fix for CVE-2026-90030 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90030 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-90030

Explore →

Is Your Infrastructure Affected by CVE-2026-90030?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs