System crashes via excessive USB3 resume hold
Published Oct 23, 2026 · Updated Oct 23, 2026
USB hub timing in Linux allows local users to crash affected AMD systems through repeated USB enumeration with runtime power management. The hub_activate() path in drivers/usb/core/hub.c retains a power-management reference for 200 ms after root-hub resume, applying a delay intended for external hubs. Repeated local USB polling, such as adb enumeration once per second, triggers crashes on affected AMD platforms when USB runtime power management is enabled.
Summary
What happened
USB hub timing in Linux allows local users to crash affected AMD systems through repeated USB enumeration with runtime power management. The hub_activate() path in drivers/usb/core/hub.c retains a power-management reference for 200 ms after root-hub resume, applying a delay intended for external hubs. Repeated local USB polling, such as adb enumeration once per second, triggers crashes on affected AMD platforms when USB runtime power management is enabled.
The record
- CVE
- CVE-2026-98933
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=042959e9b479502a921109224c3abcc3d3cf09a1
- Affected versionversion=15fea75a788681dd36a869dd90ff4f0461ea0714 <e4df763ba3c4fdd1d9256f7a75a17ab7c5e31db6
- Affected versionversion=16840c4e102ee5424ab1c49238f0bbf568d13a1c
- Affected versionversion=43e53eb8433c332666a222bff8e49aa03a470d0d
- Affected versionversion=5.10.241 <5.11
- Affected versionversion=5.15.190 <5.16
- Affected versionversion=5.4.297 <5.5
- Affected versionversion=6.1.147 <6.2
- Affected versionversion=6.12.40 <6.12.113
- Affected versionversion=6.15.8 <6.16
- Affected versionversion=6.16
- Affected versionversion=6.6.100 <6.6.160
- Affected versionversion=8aa04df2553f29e6249f978a29421f2744a65ffb
- Affected versionversion=8f5b7e2bec1c36578fdaa74a6951833541103e27 <29480b05e6e226594dc11ccf2a036fbd5cdd0e42
- Affected versionversion=8f5b7e2bec1c36578fdaa74a6951833541103e27 <d7c4a49b41583266e1456d40f37966029f61dab9
- Affected versionversion=8f5b7e2bec1c36578fdaa74a6951833541103e27 <e9545dd8bc62596b2a20966be41f39879ea7c8d0
- Affected versionversion=aec11e5f9c452ef64e2c113637ab89a67a5ceb62 <2dc82d6a12050c2c678a328cd29837beb367df7d
- Affected versionversion=e38ca702130b7d70834abdbee58135ca471b2106
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us