# CVE-2025-68750: usb: potential integer overflow in usbg_make_tpg()

> An integer overflow in the Linux kernel USB gadget subsystem allows local attackers to potentially escalate privileges or execute code.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-68750, DEBIAN-CVE-2025-68750, GHSA-475m-mm7r-j479, UBUNTU-CVE-2025-68750

## What is CVE-2025-68750?

CVE-2025-68750 is a vulnerability in Linux, published on 24 Dec 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: potential integer overflow in usbg_make_tpg()

The variable tpgt in usbg_make_tpg() is defined as unsigned long and is
assigned to tpgt->tport_tpgt, which is defined as u16. This may cause an
integer overflow when tpgt is greater than USHRT_MAX (65535). I
haven't tried to trigger it myself, but it is possible to trigger it
by calling usbg_make_tpg() with a large value for tpgt.

I modified the type of tpgt to match tpgt->tport_tpgt and adjusted the
relevant code accordingly.

This patch is similar to commit 59c816c1f24d ("vhost/scsi: potential
memory corruption").

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


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

Apply the vendor's patch.

## Is CVE-2025-68750 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68750 is a vulnerability in Linux, published on 24 Dec 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-68750 in the wild and no public exploit code.

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

## Sources

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

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