CVE-2026-98765: USB: gadget: dummy-hcd: Fix wait for outstanding request completions
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 3.17, 3.3, 3070806a7bc7bb36ed04a21022c09dafcc5619f4; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 3.17, 3.3, 3070806a7bc7bb36ed04a21022c09dafcc5619f4; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 7b416b9dac6ede26d4ca0c1a88b448b543623ff3, 8590bc1da625dd4a589eac0fc3aa3cf4f400424d, a867d5b932ac4911d3f8a1e63505061b0c81f889, e84b4a008365b7edbd842a063ae28d040a98db25, e39b17143a5b5aac81f066d455e5d3a9877eb3ae, 4f8ae1fcb0dfbb72a7678f81bf01fb7fc85c6715, 4.14affected
- 7dbd8f4cabd96db5a50513de9d83a8105a5ffc81 and later · before 32721319e89a2be610b0518b88f0d188ce878063affected · git
- 7dbd8f4cabd96db5a50513de9d83a8105a5ffc81 and later · before 48ef54100ceffbd1a055f193873574c45f408eb5affected · git
- 7dbd8f4cabd96db5a50513de9d83a8105a5ffc81 and later · before d77cc7c0d739fb17413714c5c4914bd396502e20affected · git
- 7dbd8f4cabd96db5a50513de9d83a8105a5ffc81 and later · before 6849e51b89de5b6fc7447dc8e612b58df19c7deaaffected · git
- 7dbd8f4cabd96db5a50513de9d83a8105a5ffc81 and later · before 7ce4dca0d53b1c3cb2b7e7bb2e42bf5db860caf2affected · git
- 7dbd8f4cabd96db5a50513de9d83a8105a5ffc81 and later · before 5298c96bf0068f3160969f7ddad81976d01a9b66affected · git
- 7dbd8f4cabd96db5a50513de9d83a8105a5ffc81 and later · before 3070806a7bc7bb36ed04a21022c09dafcc5619f4affected · git
- 7dbd8f4cabd96db5a50513de9d83a8105a5ffc81 and later · before b263ff9b0fc5c1f371d65c4eb196b31263d039ffaffected · git
- 3.2.97 and later · before 3.3affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.10-1 | 7.2.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98763Oct 18, 2026 · usb: core: clear both ep_in and ep_out for non-ep0 control endpoints0Monitor
- ← EarlierCVE-2026-98764Oct 18, 2026 · usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC0Monitor
- Later →CVE-2026-98766Oct 18, 2026 · usb: gadget: aspeed-vhub: cancel wake work on device removal0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3.17 | Vendor (CNA) |
| Linux Linux | 3.3 | Vendor (CNA) |
| Linux Linux | 3070806a7bc7bb36ed04a21022c09dafcc5619f4 | Vendor (CNA) |
| Linux Linux | 32721319e89a2be610b0518b88f0d188ce878063 | Vendor (CNA) |
| Linux Linux | 4.10 | Vendor (CNA) |
| Linux Linux | 4.14 | Vendor (CNA) |
| Linux Linux | 4.2 | Vendor (CNA) |
| Linux Linux | 4.5 | Vendor (CNA) |
| Linux Linux | 48ef54100ceffbd1a055f193873574c45f408eb5 | Vendor (CNA) |
| Linux Linux | 5298c96bf0068f3160969f7ddad81976d01a9b66 | Vendor (CNA) |
| Linux Linux | 6849e51b89de5b6fc7447dc8e612b58df19c7dea | Vendor (CNA) |
| Linux Linux | 7ce4dca0d53b1c3cb2b7e7bb2e42bf5db860caf2 | Vendor (CNA) |
| Linux Linux | b263ff9b0fc5c1f371d65c4eb196b31263d039ff | Vendor (CNA) |
| Linux Linux | d77cc7c0d739fb17413714c5c4914bd396502e20 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 6, 2026+19 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/32721319e89a2be610b0518b88f0d188ce878063
- git.kernel.org/stable/c/48ef54100ceffbd1a055f193873574c45f408eb5
- git.kernel.org/stable/c/5298c96bf0068f3160969f7ddad81976d01a9b66
- git.kernel.org/stable/c/6849e51b89de5b6fc7447dc8e612b58df19c7dea
- git.kernel.org/stable/c/7ce4dca0d53b1c3cb2b7e7bb2e42bf5db860caf2
- git.kernel.org/stable/c/b263ff9b0fc5c1f371d65c4eb196b31263d039ff
- git.kernel.org/stable/c/d77cc7c0d739fb17413714c5c4914bd396502e20
Vendor advisories and official records. Exploit/PoC links are deliberately left out.