{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98933 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-98933 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-98933 and fix it if it is affected.\n\nWhat it is: CVE-2026-98933 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-98933 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98933/ (Markdown: https://insights.sbomify.com/CVE-2026-98933/index.md)","id":"CVE-2026-98933","markdown":"https://insights.sbomify.com/CVE-2026-98933/index.md","name":"CVE-2026-98933","record":{"aliases":["BELL-CVE-2026-98933","DEBIAN-CVE-2026-98933","GHSA-538r-3fgm-pp95","UBUNTU-CVE-2026-98933"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"usb: hub: use shorter 120ms post resume hold for SS root hubs","id":"CVE-2026-98933","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"ipv6: sr: use skb_get_hash_net() in seg6_make_flowlabel()","id":"CVE-2026-98934"},"packages":[],"prev":{"headline":"EDAC/altera: Fix use-after-free in error paths","id":"CVE-2026-98932"},"products":["Linux"],"published":"2026-10-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-23","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-98933/"}