CVE-2022-50468 [Medium] | Security Vulnerability in Linux Kernel

In the Linux kernel, the following vulnerability has been resolved: platform/chrome: cros_usbpd_notify: Fix error handling in cros_usbpd_notify_init() The following WARNING message was given when rmmod cros_usbpd_notify: Unexpected driver unregister! WARNING: CPU: 0 PID: 253 at drivers/base/driver.c:270 driver_unregister+0x8a/0xb0 Modules linked in: cros_usbpd_notify(-) CPU: 0 PID: 253 Comm: rmmod Not tainted 6.1.0-rc3 #24 ... Call Trace: <TASK> cros_usbpd_notify_exit+0x11/0x1e [cros_usbpd_notify] __x64_sys_delete_module+0x3c7/0x570 ? __ia32_sys_delete_module+0x570/0x570 ? lock_is_held_type+0xe3/0x140 ? syscall_enter_from_user_mode+0x17/0x50 ? rcu_read_lock_sched_held+0xa0/0xd0 ? syscall_enter_from_user_mode+0x1c/0x50 do_syscall_64+0x37/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f333fe9b1b7 The reason is that the cros_usbpd_notify_init() does not check the return value of platform_driver_register(), and the cros_usbpd_notify can install successfully even if platform_driver_register() failed. Fix by checking the return value of platform_driver_register() and unregister cros_usbpd_notify_plat_driver when it failed.

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

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2025-10-01

—

0.02%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
5.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:N) Doesn’t really leak secrets in a meaningful way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

5.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:N): Doesn’t really leak secrets in a meaningful way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.8

3.6

[email protected]

OS Trackers for CVE-2022-50468

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2022-50468 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-50468
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-50468
`suse`	medium	—	https://www.suse.com/security/cve/CVE-2022-50468/
`ubuntu`	medium	CVE-2022-50468 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 158, not-affected 126, released 112, needs-triage 1.	https://ubuntu.com/security/CVE-2022-50468

Affected software / configurations for CVE-2022-50468

Vendor	Product	Version	Raw CPE
linux	linux_kernel	>= 5.7, < 5.10.163	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.11, < 5.15.86	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 5.16, < 6.0.16	cpe:2.3:o:linux:linux_kernel::::::::
linux	linux_kernel	>= 6.1, < 6.1.2	cpe:2.3:o:linux:linux_kernel::::::::

References for CVE-2022-50468

URL	Tags
https://git.kernel.org/stable/c/5a2d96623670155d94aca72c320c0ac27bdc6bd2	Patch
https://git.kernel.org/stable/c/5c0cacdd354987f8f5348d16908716f154047890	Patch
https://git.kernel.org/stable/c/751f12696d797e785d2611099fe9f0569d47556e	Patch
https://git.kernel.org/stable/c/7b6ee54995739202b4a0cc01b7e9269f761c573d	Patch
https://git.kernel.org/stable/c/cab345f9d51943898e406275f9607c145adb1877	Patch

URL

CVE-2022-50468 | platform/chrome: cros_usbpd_notify: Fix error handling in cros_usbpd_notify_init()

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

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

Weakness enumeration for CVE-2022-50468

OS Trackers for CVE-2022-50468

Affected software / configurations for CVE-2022-50468

References for CVE-2022-50468