CVE-2026-43428: Linux kernel · USB: core: Limit the length of unkillable synchronous timeouts
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 1015c27a5e1a63efae2b18a9901494474b4d1dc3 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 15:49 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in 1015c27a5e1a63efae2b18a9901494474b4d1dc3, 659c0c7d50a4b0f6aa197c4c098cfd91daf63862, 64f3d75633aedc12bdff220e9a4337177430bd9d +5
Exploitation evidence
Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: USB: core: Limit the length of unkillable synchronous timeouts The usb_control_msg(), usb_bulk_msg(), and usb_interrupt_msg() APIs in usbcore allow unlimited timeout durations. And since they use uninterruptible waits, this leaves open the possibility of hanging a task for an indefinitely long time, with no way to kill it short of unplugging the target device. To prevent this sort of problem, enforce a maximum limit on the length of these unkillable timeouts. The limit chosen here, somewhat arbitrarily, is 60 seconds. On many systems (although not all) this is short enough to avoid triggering the kernel's hung-task detector. In addition, clear up the ambiguity of negative timeout values by treating them the same as 0, i.e., using the maximum allowed timeout.
References
- git.kernel.org/stable/c/4e86f5b79e62ded7e3c3ebd688cf5775e618148a (opens in a new tab)
- git.kernel.org/stable/c/06d2bbc4c66c6b0e8a43728c4949026026a5be67 (opens in a new tab)
- git.kernel.org/stable/c/6c62935670acdbb7687ced20494923b66fbb0367 (opens in a new tab)
- git.kernel.org/stable/c/659c0c7d50a4b0f6aa197c4c098cfd91daf63862 (opens in a new tab)
- git.kernel.org/stable/c/24b31a227f679a942d820840a4dea7f0c09a387f (opens in a new tab)
- git.kernel.org/stable/c/64f3d75633aedc12bdff220e9a4337177430bd9d (opens in a new tab)
- git.kernel.org/stable/c/2d34cb4d1d6283b4be9c78f4a83ed6956d3069ec (opens in a new tab)
- git.kernel.org/stable/c/1015c27a5e1a63efae2b18a9901494474b4d1dc3 (opens in a new tab)