CVE-2022-50468 Details
Description
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.
A vulnerability exists in the Linux kernel's cros_usbpd_notify driver due to improper error handling in the initialization function. The issue arises because the driver does not verify whether the registration process was successful. As a result, the driver can be loaded even if an error occurs during registration, leading to a warning message about an unexpected driver unregistration when the module is removed. This vulnerability affects Linux kernel versions through 6.1.0-rc3.
The vulnerability has been addressed in upstream Linux kernel commits. Users can apply the latest patches available in the Linux kernel stable tree to mitigate this issue.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/5a2d96623670155d94aca72c320c0ac27bdc6bd2 | kernel.org | Patch |
| https://git.kernel.org/stable/c/5c0cacdd354987f8f5348d16908716f154047890 | kernel.org | Patch |
| https://git.kernel.org/stable/c/751f12696d797e785d2611099fe9f0569d47556e | kernel.org | Patch |
| https://git.kernel.org/stable/c/7b6ee54995739202b4a0cc01b7e9269f761c573d | kernel.org | Patch |
| https://git.kernel.org/stable/c/cab345f9d51943898e406275f9607c145adb1877 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.7, < 5.10.163 >= 5.11, < 5.15.86 >= 5.16, < 6.0.16 >= 6.1, < 6.1.2 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jan 16, 2026 | Initial Analysis | [email protected] |
| Oct 1, 2025 | New CVE Received | kernel.org |