CVE-2026-43428
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 5.10.253
- Linux Kernel < 5.15.203
- Linux Kernel < 6.1.167
- Linux Kernel < 6.6.130
- Linux Kernel < 6.12.78
- Linux Kernel < 6.18.19
- Linux Kernel < 6.19.9
- Linux Kernel 2.6.12
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-43428.md and follow it. Check whether this project is affected by CVE-2026-43428. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/06d2bbc4c66c6b0e8a43728c4949026026a5be67
- https://git.kernel.org/stable/c/1015c27a5e1a63efae2b18a9901494474b4d1dc3
- https://git.kernel.org/stable/c/24b31a227f679a942d820840a4dea7f0c09a387f
- https://git.kernel.org/stable/c/2d34cb4d1d6283b4be9c78f4a83ed6956d3069ec
- https://git.kernel.org/stable/c/4e86f5b79e62ded7e3c3ebd688cf5775e618148a
- https://git.kernel.org/stable/c/64f3d75633aedc12bdff220e9a4337177430bd9d
- https://git.kernel.org/stable/c/659c0c7d50a4b0f6aa197c4c098cfd91daf63862
- https://git.kernel.org/stable/c/6c62935670acdbb7687ced20494923b66fbb0367
References
- https://git.kernel.org/stable/c/06d2bbc4c66c6b0e8a43728c4949026026a5be67
- https://git.kernel.org/stable/c/1015c27a5e1a63efae2b18a9901494474b4d1dc3
- https://git.kernel.org/stable/c/24b31a227f679a942d820840a4dea7f0c09a387f
- https://git.kernel.org/stable/c/2d34cb4d1d6283b4be9c78f4a83ed6956d3069ec
- https://git.kernel.org/stable/c/4e86f5b79e62ded7e3c3ebd688cf5775e618148a
- https://git.kernel.org/stable/c/64f3d75633aedc12bdff220e9a4337177430bd9d
- https://git.kernel.org/stable/c/659c0c7d50a4b0f6aa197c4c098cfd91daf63862
- https://git.kernel.org/stable/c/6c62935670acdbb7687ced20494923b66fbb0367