What is CVE-2026-90030?

CVE-2026-90030 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10, affecting Linux kernel versions from 6.6.37 onward and patched in 6.12.112, 6.18.51, 7.2.5 and others. CVE-2026-90030 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-90030?

CVE-2026-90030 has a CVSS score of 7.8 out of 10, rated High severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Is there a patch available for CVE-2026-90030?

Yes, CVE-2026-90030 has been patched. Fixed versions include 6.12.112, 6.18.51, 7.2.5 and others. If you are running Linux kernel 6.6.37 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-90030 actively exploited?

CVE-2026-90030 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2026-90030

High

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.

Package Linux Kernel

Published 2026-09-16

Last modified 2026-10-03

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.8

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected versions

Linux kernel versions 6.6.37, 6.9 and later are affected. Fixed in 6.12.112, 6.18.51, 7.2.5, 7.3-rc2 and their respective stable series.

Affected from

≥ 6.6.37 ≥ 6.9

Fixed in

✓ 6.12.112 6.12.x ✓ 6.18.51 6.18.x ✓ 7.2.5 7.2.x ✓ 7.3-rc2

References

4 total

Details

CVE ID CVE-2026-90030

Severity High

CVSS score 7.8 / 10

CVSS version 3.1

Published 2026-09-16

Modified 2026-10-03

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-90030?

CVE-2026-90030 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 6.6.37 onward and has been patched in 6.12.112, 6.18.51, 7.2.5 and others. CVE-2026-90030 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-90030?

CVE-2026-90030 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Is there a patch available for CVE-2026-90030?

Yes. CVE-2026-90030 has been patched. Fixed versions include 6.12.112, 6.18.51, 7.2.5 and others. If you are running Linux kernel 6.6.37 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-90030 actively exploited?

No. CVE-2026-90030 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.