CVE-2026-98933: usb: hub: use shorter 120ms post resume hold for SS root hubs
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.16% (FIRST EPSS).
- Fixed version: Linux Linux 29480b05e6e226594dc11ccf2a036fbd5cdd0e42, 2dc82d6a12050c2c678a328cd29837beb367df7d, 5.11.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 29480b05e6e226594dc11ccf2a036fbd5cdd0e42, 2dc82d6a12050c2c678a328cd29837beb367df7d, 5.11 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: hub: use shorter 120ms post resume hold for SS root hubs Holding a USB3 hub PM runtime reference for 200ms at hub resume triggers an AMD platform issue. Users running Android adb report crashes after adb has been polling and waking up the USB subsystem once a second for some time. Vendors are working on a solution. Disabling USB runtime PM is one way to prevent this issue, but it is also proven that reducing the hold time to 120ms in resume also mitigates it. See Link for more details. Reducing the hold time to 120ms for the USB3 roothub is in itself a valid change and optimization, as the current 200ms is excessive: a root hub has no upstream suspended hub whose wake propagation needs to be accounted for, but still need some time for USB3 link training to complete. Keep the 200ms hold for external hubs that commit 8f5b7e2bec1c ("usb: hub: fix detection of high tier USB3 devices behind suspended hubs") is intended for.
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- EPSS
- 0.1% · 6th 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
- 042959e9b479502a921109224c3abcc3d3cf09a1, 8aa04df2553f29e6249f978a29421f2744a65ffb, e38ca702130b7d70834abdbee58135ca471b2106, 43e53eb8433c332666a222bff8e49aa03a470d0d, 16840c4e102ee5424ab1c49238f0bbf568d13a1c, 6.16affected
- 15fea75a788681dd36a869dd90ff4f0461ea0714 and later · before e4df763ba3c4fdd1d9256f7a75a17ab7c5e31db6affected · git
- aec11e5f9c452ef64e2c113637ab89a67a5ceb62 and later · before 2dc82d6a12050c2c678a328cd29837beb367df7daffected · git
- 8f5b7e2bec1c36578fdaa74a6951833541103e27 and later · before e9545dd8bc62596b2a20966be41f39879ea7c8d0affected · git
- 8f5b7e2bec1c36578fdaa74a6951833541103e27 and later · before d7c4a49b41583266e1456d40f37966029f61dab9affected · git
- 8f5b7e2bec1c36578fdaa74a6951833541103e27 and later · before 29480b05e6e226594dc11ccf2a036fbd5cdd0e42affected · git
- 6.6.100 and later · before 6.6.160affected · semver
- 6.12.40 and later · before 6.12.113affected · semver
- 5.4.297 and later · before 5.5affected · semver
- 5.10.241 and later · before 5.11affected · 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: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-98931Oct 23, 2026 · mtd: spinand: fix NULL pointer dereference with no ECC engine0Monitor
- ← EarlierCVE-2026-98932Oct 23, 2026 · EDAC/altera: Fix use-after-free in error paths29Monitor
- Later →CVE-2026-98934Oct 23, 2026 · ipv6: sr: use skb_get_hash_net() in seg6_make_flowlabel()0Monitor
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 | 29480b05e6e226594dc11ccf2a036fbd5cdd0e42 | Vendor (CNA) |
| Linux Linux | 2dc82d6a12050c2c678a328cd29837beb367df7d | Vendor (CNA) |
| Linux Linux | 5.11 | Vendor (CNA) |
| Linux Linux | 5.16 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 6.12.113 | Vendor (CNA) |
| Linux Linux | 6.16 | Vendor (CNA) |
| Linux Linux | 6.2 | Vendor (CNA) |
| Linux Linux | 6.6.160 | Vendor (CNA) |
| Linux Linux | d7c4a49b41583266e1456d40f37966029f61dab9 | Vendor (CNA) |
| Linux Linux | e4df763ba3c4fdd1d9256f7a75a17ab7c5e31db6 | Vendor (CNA) |
| Linux Linux | e9545dd8bc62596b2a20966be41f39879ea7c8d0 | Vendor (CNA) |
| debian:linux | 6.12.113-1 · Debian:13 | 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
- TodayOct 30, 2026+7 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1390 · Oct 26, 2026(Linux Kernel Güvenlik Bildirimi)
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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.