CVE-2022-50470xhci: Remove device endpoints from bandwidth list when freeing the device
- 7.8HighCVSS base score
- 0.17%Exploitation in 30 daysEPSS · top 93% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: xhci: Remove device endpoints from bandwidth list when freeing the device Endpoints are normally deleted from the bandwidth list when they are dropped, before the virt device is freed. If xHC host is dying or being removed then the endpoints aren't dropped cleanly due to functions returning early to avoid interacting with a non-accessible host controller. So check and delete endpoints that are still on the bandwidth list when freeing the virt device. Solves a list_del corruption kernel crash when unbinding xhci-pci, caused by xhci_mem_cleanup() when it later tried to delete already freed endpoints from the bandwidth list. This only affects hosts that use software bandwidth checking, which currenty is only the xHC in intel Panther Point PCH (Ivy Bridge)
Timeline
ID reserved
By Linux
Published
- 13 months later
· 13 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.17% · top 93% of all CVEs (12 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 2e27980e6eb78114c4ecbaad1ba71836e3887d18 – < 5e4ce28ad907aa54f13b21d5f1dc490525957b0c
- affected 2e27980e6eb78114c4ecbaad1ba71836e3887d18 – < f0de39474078adef6ece7a183e34c15ce2c1d8d1
- affected 2e27980e6eb78114c4ecbaad1ba71836e3887d18 – < cebbc8d335d6bcc1316584f779c08f80287c6af8
- affected 2e27980e6eb78114c4ecbaad1ba71836e3887d18 – < 8f1cd9633d1f21efc13e8fc75be8f2b6bb85e38c
- affected 2e27980e6eb78114c4ecbaad1ba71836e3887d18 – < 678d2cc2041cc6ce05030852dce9ad42719abcfc
- affected 2e27980e6eb78114c4ecbaad1ba71836e3887d18 – < c892a81c7424b4f6a660cb9c249d354ccf3afeca
- affected 2e27980e6eb78114c4ecbaad1ba71836e3887d18 – < 3bf860a41e0f2fcea0ac3aae8f7ef887a7994b70
- affected 2e27980e6eb78114c4ecbaad1ba71836e3887d18 – < 5aed5b7c2430ce318a8e62f752f181e66f0d1053
- affected 3.2
- unaffected < 3.2
- unaffected 4.9.332 – ≤ 4.9.*
- unaffected 4.14.298 – ≤ 4.14.*
- unaffected 4.19.264 – ≤ 4.19.*
- unaffected 5.4.223 – ≤ 5.4.*
- unaffected 5.10.153 – ≤ 5.10.*
- unaffected 5.15.77 – ≤ 5.15.*
- unaffected 6.0.7 – ≤ 6.0.*
- unaffected 6.1 – ≤ *
References
References8
- https://git.kernel.org/stable/c/5e4ce28ad907aa54f13b21d5f1dc490525957b0c (opens in a new tab)
- https://git.kernel.org/stable/c/f0de39474078adef6ece7a183e34c15ce2c1d8d1 (opens in a new tab)
- https://git.kernel.org/stable/c/cebbc8d335d6bcc1316584f779c08f80287c6af8 (opens in a new tab)
- https://git.kernel.org/stable/c/8f1cd9633d1f21efc13e8fc75be8f2b6bb85e38c (opens in a new tab)
- https://git.kernel.org/stable/c/678d2cc2041cc6ce05030852dce9ad42719abcfc (opens in a new tab)
- https://git.kernel.org/stable/c/c892a81c7424b4f6a660cb9c249d354ccf3afeca (opens in a new tab)
- https://git.kernel.org/stable/c/3bf860a41e0f2fcea0ac3aae8f7ef887a7994b70 (opens in a new tab)
- https://git.kernel.org/stable/c/5aed5b7c2430ce318a8e62f752f181e66f0d1053 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-32373 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-50470)Record last updated .