# CVE-2025-37882: usb: xhci: Fix isochronous Ring Underrun/Overrun event handling

> A race condition in the Linux kernel xHCI driver can lead to use-after-free, potentially allowing code execution or system crashes.

- **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:** 9 May 2025
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-62753, AZL-70159, BELL-CVE-2025-37882, DEBIAN-CVE-2025-37882, GHSA-3qx6-96c8-pv99, ROOT-OS-DEBIAN-11-CVE-2025-37882, ROOT-OS-DEBIAN-12-CVE-2025-37882, ROOT-OS-UBUNTU-2204-CVE-2025-37882, ROOT-OS-UBUNTU-2404-CVE-2025-37882, UBUNTU-CVE-2025-37882

## What is CVE-2025-37882?

CVE-2025-37882 is a high-severity use after free vulnerability in Linux kernel, published on 9 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 isochronous Ring Underrun/Overrun event handling

The TRB pointer of these events points at enqueue at the time of error
occurrence on xHCI 1.1+ HCs or it's NULL on older ones. By the time we
are handling the event, a new TD may be queued at this ring position.

I can trigger this race by rising interrupt moderation to increase IRQ
handling delay. Similar delay may occur naturally due to system load.

If this ever happens after a Missed Service Error, missed TDs will be
skipped and the new TD processed as if it matched the event. It could
be given back prematurely, risking data loss or buffer UAF by the xHC.

Don't complete TDs on xrun events and don't warn if queued TDs don't
match the event's TRB pointer, which can be NULL or a link/no-op TRB.
Don't warn if there are no queued TDs at all.

Now that it's safe, also handle xrun events if the skip flag is clear.
This ensures completion of any TD stuck in 'error mid TD' state right
before the xrun event, which could happen if a driver submits a finite
number of URBs to a buggy HC and then an error occurs on the last TD.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2025-37882 being exploited?

There is no known exploitation of CVE-2025-37882 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-37882 and fix it if it is affected.

What it is: CVE-2025-37882 is a high-severity use after free vulnerability in Linux kernel, published on 9 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-37882 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-37882/ (Markdown: https://insights.sbomify.com/CVE-2025-37882/index.md)
```

## Sources

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

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