CVE-2026-98933

usb: hub: use shorter 120ms post resume hold for SS root hubs

N/A
Published: October 23, 2026 at 12:11 PM UTC
Updated: October 23, 2026 at 01:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

042959e9b479502a921109224c3abcc3d3cf09a115fea75a788681dd36a869dd90ff4f0461ea071416840c4e102ee5424ab1c49238f0bbf568d13a1c43e53eb8433c332666a222bff8e49aa03a470d0d5.10.2415.15.1905.4.2976.1.1476.12.406.15.86.166.6.1008aa04df2553f29e6249f978a29421f2744a65ffb8f5b7e2bec1c36578fdaa74a6951833541103e27aec11e5f9c452ef64e2c113637ab89a67a5ceb62e38ca702130b7d70834abdbee58135ca471b2106
Vendor states this is fixed in 6.12.113 (unaffected)
Vendor states this is fixed in 6.18.56 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)
Vendor states this is fixed in 7.2.10 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card