CVE-2026-98765: Linux kernel · USB: gadget: dummy-hcd: Fix wait for outstanding request completions
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in b263ff9b0fc5c1f371d65c4eb196b31263d039ff : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:18 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in b263ff9b0fc5c1f371d65c4eb196b31263d039ff, 3070806a7bc7bb36ed04a21022c09dafcc5619f4, 6849e51b89de5b6fc7447dc8e612b58df19c7dea +8
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 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– |
Description
In the Linux kernel, the following vulnerability has been resolved: USB: gadget: dummy-hcd: Fix wait for outstanding request completions The dummy-hcd driver emulates synchronize_irq() by waiting until its private callback_usage counter drops to 0 (with the private lock not held). This counter is incremented whenever a gadget driver callback occurs (which requires the private lock to be dropped), but not when a request completion handler is called. This is an oversight. Request completion is triggered by timer interrupts (emulating device IRQs in a real UDC), and the interrupt handlers are supposed to have completed when the synchronize_irq() emulation routine returns -- they aren't supposed to be in the middle of a completion callback. If this happens it can lead to a gadget driver's unbind routine running before all outstanding request completions have finished, maybe even allowing the gadget driver's module to be unloaded while a completion handler is still running. Fix the oversight by incrementing the callback_usage value across request completion callbacks.
References
- git.kernel.org/stable/c/6849e51b89de5b6fc7447dc8e612b58df19c7dea (opens in a new tab)
- git.kernel.org/stable/c/7ce4dca0d53b1c3cb2b7e7bb2e42bf5db860caf2 (opens in a new tab)
- git.kernel.org/stable/c/5298c96bf0068f3160969f7ddad81976d01a9b66 (opens in a new tab)
- git.kernel.org/stable/c/3070806a7bc7bb36ed04a21022c09dafcc5619f4 (opens in a new tab)
- git.kernel.org/stable/c/b263ff9b0fc5c1f371d65c4eb196b31263d039ff (opens in a new tab)