LiveActive security incident?Get immediate response
CVE Record

CVE-2025-37813: usb: xhci: Fix invalid pointer dereference in Etron workaround

In the Linux kernel, the following vulnerability has been resolved: usb: xhci: Fix invalid pointer dereference in Etron workaround This check is performed before prepare_transfer() and prepare_ring(), so enqueue can already point at the final link TRB of a segment. And indeed it will, some 0.4% of times this code is called. Then enqueue + 1 is an invalid pointer. It will crash the kernel right away or load some junk which may look like a link TRB and cause the real link TRB to be replaced with a NOOP. This wouldn't end well. Use a functionally equivalent test which doesn't dereference the pointer and always gives correct result. Something has crashed my machine twice in recent days while playing with an Etron HC, and a control transfer stress test ran for confirmation has just crashed it again. The same test passes with this patch applied.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux USB host-controller bug can crash or corrupt kernel processing on systems using the affected Etron xHCI workaround. Triggering requires local access according to the CVSS vector. The supplied evidence documents repeatable crashes during control-transfer stress testing, but does not establish real-world attacks or remote exposure.

Executive priority

Prioritize confirmation and patching on systems with Etron xHCI controllers, especially shared or availability-sensitive hosts. Broader emergency action is not supported by the supplied evidence because exploitation is local, hardware-dependent, and not documented as active. Treat recurring USB-related kernel crashes as an escalation signal.

Technical view

The Etron xHCI workaround may evaluate enqueue + 1 when enqueue already references a segment’s final link TRB. That pointer is invalid and can cause an immediate kernel crash or misidentify memory as a link TRB, replacing the genuine entry with a NOOP. The correction uses an equivalent test that avoids dereferencing the invalid pointer.

Likely exposure

Exposure is concentrated on Linux systems using relevant Etron USB xHCI hardware and the affected workaround path. The bundle marks multiple kernel branches as affected, but its version presentation is ambiguous. Confirm exposure through distribution advisories, kernel package provenance, hardware inventory, and inclusion of the referenced stable fixes.

Exploitation context

CVSS 3.1 rates this 7.8 with local access, low complexity, low privileges, and no user interaction. It is not listed as KEV in the bundle. The source reports crashes reproduced by control-transfer stress testing; no supplied source confirms malicious exploitation, remote reachability, privilege escalation, or code execution.

Researcher notes

The reported faulty condition occurs when enqueue already addresses the segment’s final link TRB; the source estimates this state in roughly 0.4% of calls. Consequences described are invalid dereference, immediate crash, or TRB corruption. The supplied CVE version data is difficult to interpret safely, so commit-level or distribution-level verification is preferable.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable referenced stable fix.
  • Check Linux distribution advisories for corrected package versions and backports.
  • Prioritize exposed multi-user systems containing relevant Etron xHCI hardware.
  • Where updating is delayed, follow vendor guidance for safely limiting affected hardware use.

Validation and detection

  • Inventory kernel versions, package revisions, and Etron xHCI controller presence.
  • Confirm the installed kernel includes the applicable referenced stable commit or vendor backport.
  • Review kernel logs and crash records for xHCI or USB transfer failures.
  • After updating, repeat approved USB stability testing in a controlled environment.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-37813 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-37813Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxfbc0a0c7718a6cb1dc5e0811a4f88a2b1deedfa1, 9258c9ed32294ce3a4b58c9d92fc49ba030d35c9, 5e1c67abc9301d05130b7e267c204e7005503b33, 5e1c67abc9301d05130b7e267c204e7005503b33, 4725344ca645a98a9d8e45e25b01a2244de5b8aa, 6.6.66, 6.12.2, 6.11.11unaffected
LinuxLinux6.13, 0, 6.6.89, 6.12.26, 6.14.5, 6.15affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.