Menu

Star on GitHub · 3.2k

CVE-2025-68750

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 assi…

Published Dec 24, 2025EPSS 0.20%

Overview

CVE-2025-68750 is a known-severity vulnerability. It was published on December 24, 2025.

Technical 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").

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-68750?

CVE-2025-68750 is a known-severity vulnerability. It was published on December 24, 2025.

How severe is CVE-2025-68750?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2025-68750?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-68750?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-68750 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.