USB target configuration corruption via oversized tpgt
Published Dec 24, 2025 · Updated Dec 24, 2025
Integer truncation in affected Linux kernel releases allows local users to corrupt USB gadget target configuration through an oversized tpgt name. In drivers/usb/gadget/function/f_tcm.c, usbg_make_tpg parses the numeric suffix with kstrtoul and assigns the unsigned long result to a 16-bit tport_tpgt field, wrapping values above 65535. Reaching the flaw requires local access to create a USB gadget target portal group; the documented consequence is an incorrect target identifier and associated configuration corruption.
Summary
What happened
Integer truncation in affected Linux kernel releases allows local users to corrupt USB gadget target configuration through an oversized tpgt name. In drivers/usb/gadget/function/f_tcm.c, usbg_make_tpg parses the numeric suffix with kstrtoul and assigns the unsigned long result to a 16-bit tport_tpgt field, wrapping values above 65535. Reaching the flaw requires local access to create a USB gadget target portal group; the documented consequence is an incorrect target identifier and associated configuration corruption.
The record
- CVE
- CVE-2025-68750
- Published
- Dec 24, 2025
- Updated
- Dec 24, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 24, 2025CVE publishedPublication date reported by the CVE source.
- Dec 24, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0861b9cb2ff519b7c5a3b1dd52a343e18c4efb24
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <153874010354d050f62f8ae25cbb960c17633dc5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <358d5ba08f1609c34a054aed88c431844d09705a
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <603a83e5fee38a950bfcfb2f36449311fa00a474
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <620a5e1e84a3a7004270703a118d33eeb1c0f368
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6722e080b5b39ab7471386c73d0c1b39572f943c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6f77e344515b5258edb3988188311464209b1c7c
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a33f507f36d5881f602dab581ab0f8d22b49762c
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo