GHSA-538R-3FGM-PP95
Vulnerability from github – Published: 2026-10-23 15:31 – Updated: 2026-10-23 15:31In 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": [],
"aliases": [
"CVE-2026-98933"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-23T13:17:14Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nusb: hub: use shorter 120ms post resume hold for SS root hubs\n\nHolding a USB3 hub PM runtime reference for 200ms at hub resume triggers\nan AMD platform issue. Users running Android adb report crashes after\nadb has been polling and waking up the USB subsystem once a second for\nsome time. Vendors are working on a solution. Disabling USB runtime PM\nis one way to prevent this issue, but it is also proven that reducing the\nhold time to 120ms in resume also mitigates it. See Link for more\ndetails.\n\nReducing the hold time to 120ms for the USB3 roothub is in itself a valid\nchange and optimization, as the current 200ms is excessive: a root hub\nhas no upstream suspended hub whose wake propagation needs to be\naccounted for, but still need some time for USB3 link training to\ncomplete.\n\nKeep the 200ms hold for external hubs that commit 8f5b7e2bec1c\n(\"usb: hub: fix detection of high tier USB3 devices behind suspended\nhubs\") is intended for.",
"id": "GHSA-538r-3fgm-pp95",
"modified": "2026-10-23T15:31:31Z",
"published": "2026-10-23T15:31:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98933"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/29480b05e6e226594dc11ccf2a036fbd5cdd0e42"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2dc82d6a12050c2c678a328cd29837beb367df7d"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d7c4a49b41583266e1456d40f37966029f61dab9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e4df763ba3c4fdd1d9256f7a75a17ab7c5e31db6"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e9545dd8bc62596b2a20966be41f39879ea7c8d0"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.