USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts
Summary
| CVE | CVE-2026-43429 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-05-08 15:16:55 UTC |
| Updated | 2026-05-12 14:10:27 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts The usbtmc driver accepts timeout values specified by the user in an ioctl command, and uses these timeouts for some usb_bulk_msg() calls. Since the user can specify arbitrarily long timeouts and usb_bulk_msg() uses unkillable waits, call usb_bulk_msg_killable() instead to avoid the possibility of the user hanging a kernel thread indefinitely. |
Risk And Classification
EPSS: 0.000240000 probability, percentile 0.070360000 (date 2026-05-12)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 048c6d88a0214757926f264823829e79154fcd4f e14a0dcdf468c3ad616bb06696c7c64c36e736d8 git | Not specified |
| CNA | Linux | Linux | affected 048c6d88a0214757926f264823829e79154fcd4f 7fa72c369c23c27d1f64883c1e276af950557fb1 git | Not specified |
| CNA | Linux | Linux | affected 048c6d88a0214757926f264823829e79154fcd4f 72c0a063489be183cfb99e7050aaef503bdb6449 git | Not specified |
| CNA | Linux | Linux | affected 048c6d88a0214757926f264823829e79154fcd4f 39bd4097292fd8564cf2cfba9356f8ab11e38d12 git | Not specified |
| CNA | Linux | Linux | affected 048c6d88a0214757926f264823829e79154fcd4f 0535f84cb94c9d8bcba0a2a5b3fac81b7d97235d git | Not specified |
| CNA | Linux | Linux | affected 048c6d88a0214757926f264823829e79154fcd4f 6cb7dc91f057dd8ce44f6caa2995d8e22784ed0a git | Not specified |
| CNA | Linux | Linux | affected 048c6d88a0214757926f264823829e79154fcd4f d4f1c45bdff3f393f9ab7e76795901c442b9eb76 git | Not specified |
| CNA | Linux | Linux | affected 048c6d88a0214757926f264823829e79154fcd4f 7784caa413a89487dd14dd5c41db8753483b2acb git | Not specified |
| CNA | Linux | Linux | affected 4.19 | Not specified |
| CNA | Linux | Linux | unaffected 4.19 semver | Not specified |
| CNA | Linux | Linux | unaffected 5.10.253 5.10.* semver | Not specified |
| CNA | Linux | Linux | unaffected 5.15.203 5.15.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.167 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.130 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.78 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.19 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.19.9 6.19.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.0 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/39bd4097292fd8564cf2cfba9356f8ab11e38d12 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/7784caa413a89487dd14dd5c41db8753483b2acb | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/6cb7dc91f057dd8ce44f6caa2995d8e22784ed0a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/72c0a063489be183cfb99e7050aaef503bdb6449 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e14a0dcdf468c3ad616bb06696c7c64c36e736d8 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/0535f84cb94c9d8bcba0a2a5b3fac81b7d97235d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/7fa72c369c23c27d1f64883c1e276af950557fb1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/d4f1c45bdff3f393f9ab7e76795901c442b9eb76 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.