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