Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.20% · top 91% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected c52661d60f636d17e26ad834457db333bd1df494 – < 0861b9cb2ff519b7c5a3b1dd52a343e18c4efb24
    • affected c52661d60f636d17e26ad834457db333bd1df494 – < 603a83e5fee38a950bfcfb2f36449311fa00a474
    • affected c52661d60f636d17e26ad834457db333bd1df494 – < 6f77e344515b5258edb3988188311464209b1c7c
    • affected c52661d60f636d17e26ad834457db333bd1df494 – < 6722e080b5b39ab7471386c73d0c1b39572f943c
    • affected c52661d60f636d17e26ad834457db333bd1df494 – < a33f507f36d5881f602dab581ab0f8d22b49762c
    • affected c52661d60f636d17e26ad834457db333bd1df494 – < 358d5ba08f1609c34a054aed88c431844d09705a
    • affected c52661d60f636d17e26ad834457db333bd1df494 – < 620a5e1e84a3a7004270703a118d33eeb1c0f368
    • affected c52661d60f636d17e26ad834457db333bd1df494 – < 153874010354d050f62f8ae25cbb960c17633dc5
  • Linux · Linux

    • affected 3.5
    • unaffected < 3.5
    • unaffected 5.4.296 – ≤ 5.4.*
    • unaffected 5.10.240 – ≤ 5.10.*
    • unaffected 5.15.187 – ≤ 5.15.*
    • unaffected 6.1.143 – ≤ 6.1.*
    • unaffected 6.6.96 – ≤ 6.6.*
    • unaffected 6.12.36 – ≤ 6.12.*
    • unaffected 6.15.5 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-68750 badge
[![CVE-2025-68750](https://cveledger.app/badge/CVE-2025-68750.svg)](https://cveledger.app/cve/CVE-2025-68750)

Record last updated .