CVE-2026-43327In 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_g…
Updated under an hour ago ()
Does this affect you?
It affects linux_kernel. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- CWE-667
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Not given
- NVD analysis
- Analyzed
- Record last updated
- Jun 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
linux linux_kernel linux:linux_kernel | from 3.2.97 before 3.3; from 3.16.52 before 3.17; from 4.1.46 before 4.2; from 4.4.92 before 4.5; from 4.9.55 before 4.10; from 4.14 before 5.10.253; from 5.11 before 5.15.203; from 5.16 before 6.1.168; and 11 more ranges | NVD |
References
- https://git.kernel.org/stable/c/218886b2ef2dea7627d3700ab0abaf4bf9d1161fpatch
- https://git.kernel.org/stable/c/616a63ff495df12863692ab3f9f7b84e3fa7a66dpatch
- https://git.kernel.org/stable/c/6350c7dd33ab481ef41c931a238361490c32d15cpatch
- https://git.kernel.org/stable/c/69ab97a693251d6a6093e630060a3c744fd58524patch
- https://git.kernel.org/stable/c/791966f85b439b261bf19865cf1c07c065ffb4b4patch
- https://git.kernel.org/stable/c/805b1833d6ed6da5086e610578a28e71bb54fbbbpatch
- https://git.kernel.org/stable/c/cc97fb5969177cccce2e23b31298df220fc7570dpatch
- https://git.kernel.org/stable/c/efbd9441f1e769a7aae1813d497cec09cbdff031patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.