# CVE-2025-37810: usb: dwc3: gadget: check that event count does not exceed event buffer length

> A missing bounds check in the Linux kernel DWC3 USB gadget driver allows out-of-bounds memory access, potentially causing a system crash.

- **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:** 11 May 2026
- **Also known as:** BELL-CVE-2025-37810, DEBIAN-CVE-2025-37810, GHSA-rpfr-3prf-w7f2, ROOT-OS-DEBIAN-12-CVE-2025-37810, ROOT-OS-UBUNTU-2204-CVE-2025-37810, ROOT-OS-UBUNTU-2404-CVE-2025-37810, UBUNTU-CVE-2025-37810

## What is CVE-2025-37810?

CVE-2025-37810 is a high-severity memory corruption vulnerability in Debian Debian Linux, 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: dwc3: gadget: check that event count does not exceed event buffer length

The event count is read from register DWC3_GEVNTCOUNT.
There is a check for the count being zero, but not for exceeding the
event buffer length.
Check that event count does not exceed event buffer length,
avoiding an out-of-bounds access when memcpy'ing the event.
Crash log:
Unable to handle kernel paging request at virtual address ffffffc0129be000
pc : __memcpy+0x114/0x180
lr : dwc3_check_event_buf+0xec/0x348
x3 : 0000000000000030 x2 : 000000000000dfc4
x1 : ffffffc0129be000 x0 : ffffff87aad60080
Call trace:
__memcpy+0x114/0x180
dwc3_interrupt+0x24/0x34

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2025-37810 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-37810 is a high-severity memory corruption vulnerability in Debian Debian Linux, 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-37810 in the wild and no public exploit code.

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

## Sources

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

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