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

> A null pointer dereference in the Linux kernel xHCI driver can cause a system crash when handling specific Etron USB hardware.

- **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:** 8 May 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2025-37813, DEBIAN-CVE-2025-37813, GHSA-rc74-9j9p-c3xp, ROOT-OS-UBUNTU-2404-CVE-2025-37813, UBUNTU-CVE-2025-37813

## What is CVE-2025-37813?

CVE-2025-37813 is a high-severity vulnerability in Linux kernel, published on 8 May 2025. 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: 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.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2025-37813?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-37813?

Apply the vendor's patch.

## Is CVE-2025-37813 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-37813 and fix it if it is affected.

What it is: CVE-2025-37813 is a high-severity vulnerability in Linux kernel, published on 8 May 2025. 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-2025-37813 in the wild and no public exploit code.

Affected product: Linux kernel. 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-2025-37813/ (Markdown: https://insights.sbomify.com/CVE-2025-37813/index.md)
```

## Sources

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

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