CVE-2026-98766: usb: gadget: aspeed-vhub: cancel wake work on device removal
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 0d39ac4f65f9357469518c70e42940e0d8b0e497, 20388c8d1d74c203fec8194c45cd31afdfab934e, 3aed0c86afa7877d08722233a8b15e8c1ff8bcb8; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 0d39ac4f65f9357469518c70e42940e0d8b0e497, 20388c8d1d74c203fec8194c45cd31afdfab934e, 3aed0c86afa7877d08722233a8b15e8c1ff8bcb8; 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: aspeed-vhub: cancel wake work on device removal wake_work is armed from the gadget .wakeup callback to resume suspended downstream ports, and it is never cancelled in ast_vhub_remove(), so a work item queued before or during removal can run after devm has freed vhub and its ports, a use-after-free. Cancelling the work alone is not sufficient: usb_gadget_wakeup() takes no lock and the unbind path never clears wakeup_en, so a remote-wakeup request in flight on another CPU can re-arm the work after the cancel and before vhub is freed. ast_vhub_del_dev() already clears d->registered under vhub->lock before unregistering the gadget. Refuse the wakeup in ast_vhub_udc_wakeup() once d->registered is clear: the check and the schedule_work() are then atomic against the unbind, so a wakeup that passed before the flag was cleared is drained by the cancel_work_sync() after the del_dev loop, and one that arrives later returns without arming. Also move INIT_WORK() to the top of ast_vhub_probe(), since the probe error path reuses ast_vhub_remove() and would otherwise cancel a never-initialized work item. This issue was found by an in-house static analysis tool.
- 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
- 4.18affected
- 7ecca2a4080cb6b1fa174adc588fce9e9014c43c and later · before 89b3fef8809ec1a9acf5f753eb89b9508d7e4466affected · git
- 7ecca2a4080cb6b1fa174adc588fce9e9014c43c and later · before 3aed0c86afa7877d08722233a8b15e8c1ff8bcb8affected · git
- 7ecca2a4080cb6b1fa174adc588fce9e9014c43c and later · before 552f580a18787cfbd83d28d7d76d584c29f2c4c2affected · git
- 7ecca2a4080cb6b1fa174adc588fce9e9014c43c and later · before 0d39ac4f65f9357469518c70e42940e0d8b0e497affected · git
- 7ecca2a4080cb6b1fa174adc588fce9e9014c43c and later · before f343bfa3fc9f6255602d66f4a7dbe7ddef13ba41affected · git
- 7ecca2a4080cb6b1fa174adc588fce9e9014c43c and later · before 474e9e1852fb5ba0bfb26f123dd0cb361d0f4f4daffected · git
- 7ecca2a4080cb6b1fa174adc588fce9e9014c43c and later · before c81504dfd2d93e345c98e7a012c2f2e74ce5b6a1affected · git
- 7ecca2a4080cb6b1fa174adc588fce9e9014c43c and later · before 20388c8d1d74c203fec8194c45cd31afdfab934eaffected · git
- before 4.18not affected · 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-98764Oct 18, 2026 · usb: gadget: f_fs: Fix NULL pointer dereference in FUNCTIONFS_ENDPOINT_DESC0Monitor
- ← EarlierCVE-2026-98765Oct 18, 2026 · USB: gadget: dummy-hcd: Fix wait for outstanding request completions0Monitor
- Later →CVE-2026-98767Oct 18, 2026 · usb: dwc3: gadget: fix IRQ storm on invalid event buffer count0Monitor
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 | 0d39ac4f65f9357469518c70e42940e0d8b0e497 | Vendor (CNA) |
| Linux Linux | 20388c8d1d74c203fec8194c45cd31afdfab934e | Vendor (CNA) |
| Linux Linux | 3aed0c86afa7877d08722233a8b15e8c1ff8bcb8 | Vendor (CNA) |
| Linux Linux | 474e9e1852fb5ba0bfb26f123dd0cb361d0f4f4d | Vendor (CNA) |
| Linux Linux | 552f580a18787cfbd83d28d7d76d584c29f2c4c2 | Vendor (CNA) |
| Linux Linux | 89b3fef8809ec1a9acf5f753eb89b9508d7e4466 | Vendor (CNA) |
| Linux Linux | c81504dfd2d93e345c98e7a012c2f2e74ce5b6a1 | Vendor (CNA) |
| Linux Linux | f343bfa3fc9f6255602d66f4a7dbe7ddef13ba41 | 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/20388c8d1d74c203fec8194c45cd31afdfab934e
- git.kernel.org/stable/c/3aed0c86afa7877d08722233a8b15e8c1ff8bcb8
- git.kernel.org/stable/c/474e9e1852fb5ba0bfb26f123dd0cb361d0f4f4d
- git.kernel.org/stable/c/552f580a18787cfbd83d28d7d76d584c29f2c4c2
- git.kernel.org/stable/c/89b3fef8809ec1a9acf5f753eb89b9508d7e4466
- git.kernel.org/stable/c/c81504dfd2d93e345c98e7a012c2f2e74ce5b6a1
- git.kernel.org/stable/c/f343bfa3fc9f6255602d66f4a7dbe7ddef13ba41
Vendor advisories and official records. Exploit/PoC links are deliberately left out.