CVE-2025-68750
CVE-2025-68750 is a security vulnerability that is still awaiting full analysis and scoring. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.
Key facts
- EPSS exploit prediction: 0% (8th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2025-205291
- Published:
- Last modified:
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").
Frequently asked questions
- What is 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 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").
- Is CVE-2025-68750 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (8th percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2025-68750?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2025-68750 have an EU (EUVD) identifier?
- Yes. CVE-2025-68750 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-205291.
- When was CVE-2025-68750 published?
- CVE-2025-68750 was published on 2025-12-24 and last updated on 2026-06-17.
References
- https://git.kernel.org/stable/c/0861b9cb2ff519b7c5a3b1dd52a343e18c4efb24
- https://git.kernel.org/stable/c/153874010354d050f62f8ae25cbb960c17633dc5
- https://git.kernel.org/stable/c/358d5ba08f1609c34a054aed88c431844d09705a
- https://git.kernel.org/stable/c/603a83e5fee38a950bfcfb2f36449311fa00a474
- https://git.kernel.org/stable/c/620a5e1e84a3a7004270703a118d33eeb1c0f368
- https://git.kernel.org/stable/c/6722e080b5b39ab7471386c73d0c1b39572f943c
- https://git.kernel.org/stable/c/6f77e344515b5258edb3988188311464209b1c7c
- https://git.kernel.org/stable/c/a33f507f36d5881f602dab581ab0f8d22b49762c