Acknowledged
Created: Jun 18, 2025
Updated: Sep 4, 2026
Resolved Date: Jun 19, 2025
Found In Version: 10.25.33.1
Severity: Standard
Applicable for: Wind River Linux LTS 25
Component/s: Kernel
In the Linux kernel, the following vulnerability has been resolved:EOL][EOL]USB: core: Prevent nested device-reset calls[EOL][EOL]Automatic kernel fuzzing revealed a recursive locking violation in[EOL]usb-storage:[EOL][EOL]============================================[EOL]WARNING: possible recursive locking detected[EOL]5.18.0 #3 Not tainted[EOL]--------------------------------------------[EOL]kworker/1:3/1205 is trying to acquire lock:[EOL]ffff888018638db8 (&us_interface_key[i]){+.+.}-{3:3}, at:[EOL]usb_stor_pre_reset+0x35/0x40 drivers/usb/storage/usb.c:230[EOL][EOL]but task is already holding lock:[EOL]ffff888018638db8 (&us_interface_key[i]){+.+.}-{3:3}, at:[EOL]usb_stor_pre_reset+0x35/0x40 drivers/usb/storage/usb.c:230[EOL][EOL]...[EOL][EOL]stack backtrace:[EOL]CPU: 1 PID: 1205 Comm: kworker/1:3 Not tainted 5.18.0 #3[EOL]Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS[EOL]1.13.0-1ubuntu1.1 04/01/2014[EOL]Workqueue: usb_hub_wq hub_event[EOL]Call Trace:[EOL]<TASK>[EOL]__dump_stack lib/dump_stack.c:88 [inline][EOL]dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106[EOL]print_deadlock_bug kernel/locking/lockdep.c:2988 [inline][EOL]check_deadlock kernel/locking/lockdep.c:3031 [inline][EOL]validate_chain kernel/locking/lockdep.c:3816 [inline][EOL]__lock_acquire.cold+0x152/0x3ca kernel/locking/lockdep.c:5053[EOL]lock_acquire kernel/locking/lockdep.c:5665 [inline][EOL]lock_acquire+0x1ab/0x520 kernel/locking/lockdep.c:5630[EOL]__mutex_lock_common kernel/locking/mutex.c:603 [inline][EOL]__mutex_lock+0x14f/0x1610 kernel/locking/mutex.c:747[EOL]usb_stor_pre_reset+0x35/0x40 drivers/usb/storage/usb.c:230[EOL]usb_reset_device+0x37d/0x9a0 drivers/usb/core/hub.c:6109[EOL]r871xu_dev_remove+0x21a/0x270 drivers/staging/rtl8712/usb_intf.c:622[EOL]usb_unbind_interface+0x1bd/0x890 drivers/usb/core/driver.c:458[EOL]device_remove drivers/base/dd.c:545 [inline][EOL]device_remove+0x11f/0x170 drivers/base/dd.c:537[EOL]__device_release_driver drivers/base/dd.c:1222 [inline][EOL]device_release_driver_internal+0x1a7/0x2f0 drivers/base/dd.c:1248[EOL]usb_driver_release_interface+0x102/0x180 drivers/usb/core/driver.c:627[EOL]usb_forced_unbind_intf+0x4d/0xa0 drivers/usb/core/driver.c:1118[EOL]usb_reset_device+0x39b/0x9a0 drivers/usb/core/hub.c:6114[EOL][EOL]This turned out not to be an error in usb-storage but rather a nested[EOL]device reset attempt. That is, as the rtl8712 driver was being[EOL]unbound from a composite device in preparation for an unrelated USB[EOL]reset (that driver does not have pre_reset or post_reset callbacks),[EOL]its ->remove routine called usb_reset_device() -- thus nesting one[EOL]reset call within another.[EOL][EOL]Performing a reset as part of disconnect processing is a questionable[EOL]practice at best. However, the bug report points out that the USB[EOL]core does not have any protection against nested resets. Adding a[EOL]reset_in_progress flag and testing it will prevent such errors in the[EOL]future.
CREATE(Triage):(User=lchen-cn) [CVE-2022-49936 (https://nvd.nist.gov/vuln/detail/CVE-2022-49936)