CVE-2026-98933

UnknownEPSS 0.17%

Last modified

CVE-2026-98933 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.17%

6.2th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 8aa04df2553f29e6249f978a29421f2744a65ffb, < ff21323b74a876c54b1ebe9e5f8ba5abc7e07fd3; >= e38ca702130b7d70834abdbee58135ca471b2106, < 73d4fbc496935ccaffba15ca5ec33660c2b587fb; >= 43e53eb8433c332666a222bff8e49aa03a470d0d, < 86e0baedd55fca30081fcd858ab336dfc0f1cc09; >= 15fea75a788681dd36a869dd90ff4f0461ea0714, < e4df763ba3c4fdd1d9256f7a75a17ab7c5e31db6; >= aec11e5f9c452ef64e2c113637ab89a67a5ceb62, < 2dc82d6a12050c2c678a328cd29837beb367df7d; >= 8f5b7e2bec1c36578fdaa74a6951833541103e27, < e9545dd8bc62596b2a20966be41f39879ea7c8d0; >= 8f5b7e2bec1c36578fdaa74a6951833541103e27, < d7c4a49b41583266e1456d40f37966029f61dab9; >= 8f5b7e2bec1c36578fdaa74a6951833541103e27, < 29480b05e6e226594dc11ccf2a036fbd5cdd0e42; 042959e9b479502a921109224c3abcc3d3cf09a1; 16840c4e102ee5424ab1c49238f0bbf568d13a1c; >= 5.10.241, < 5.10.273; >= 5.15.190, < 5.15.224; >= 6.1.147, < 6.1.191; >= 6.6.100, < 6.6.160; >= 6.12.40, < 6.12.113; >= 5.4.297, < 5.5; >= 6.15.8, < 6.16
LinuxLinux6.16

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98933?
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.
How severe is CVE-2026-98933?
Severity scoring for CVE-2026-98933 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-98933?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-98933?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST