CVE-2022-50470 [High] | Security Vulnerability in Linux Kernel

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)

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2025-10-05	—	0.02%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-10-05

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.8	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	5.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.8

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

5.9

[email protected]

OS Trackers for CVE-2022-50470

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-50470 not yet assigned priority: Debian including 1 source packages (linux), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-50470
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-50470
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-50470/
`ubuntu`	medium	CVE-2022-50470 medium priority: Ubuntu including 158 source packages (linux, linux-allwinner-5.19, …), 1414 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): DNE 1017, ignored 161, released 148, not-affected 82, needed 5, needs-triage 1.	https://ubuntu.com/security/CVE-2022-50470

Affected software / configurations for CVE-2022-50470

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 3.2, < 4.9.332	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.10, < 4.14.298	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.15, < 4.19.264	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 4.20, < 5.4.223	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.5, < 5.10.153	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.77	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.0.7	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc1::::::
linux	linux_kernel	6.1	cpe:2.3:o:linux:linux_kernel:6.1:rc2::::::

References for CVE-2022-50470

URL	Tags
https://git.kernel.org/stable/c/3bf860a41e0f2fcea0ac3aae8f7ef887a7994b70	Patch
https://git.kernel.org/stable/c/5aed5b7c2430ce318a8e62f752f181e66f0d1053	Patch
https://git.kernel.org/stable/c/5e4ce28ad907aa54f13b21d5f1dc490525957b0c	Patch
https://git.kernel.org/stable/c/678d2cc2041cc6ce05030852dce9ad42719abcfc	Patch
https://git.kernel.org/stable/c/8f1cd9633d1f21efc13e8fc75be8f2b6bb85e38c	Patch
https://git.kernel.org/stable/c/c892a81c7424b4f6a660cb9c249d354ccf3afeca	Patch
https://git.kernel.org/stable/c/cebbc8d335d6bcc1316584f779c08f80287c6af8	Patch
https://git.kernel.org/stable/c/f0de39474078adef6ece7a183e34c15ce2c1d8d1	Patch

URL

CVE-2022-50470 | xhci: Remove device endpoints from bandwidth list when freeing the device

Exploit prediction scoring system (EPSS) score for CVE-2022-50470

Common vulnerability scoring system (CVSS) metrics for CVE-2022-50470

Weakness enumeration for CVE-2022-50470

OS Trackers for CVE-2022-50470

Affected software / configurations for CVE-2022-50470

References for CVE-2022-50470