[moderation] [usb?] KCSAN: data-race in mon_reader_del / usb_hcd_submit_urb (5)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 81e4f8d68c66 Merge tag 'pmdomain-v6.14-rc4' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16228e98580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f33d372c4021745
dashboard link: https://syzkaller.appspot.com/bug?extid=9d5392a375a783a1b77a
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
CC: [gre...@linuxfoundation.org linux-...@vger.kernel.org linu...@vger.kernel.org]

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/5f840ef142f8/disk-81e4f8d6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7477de61c8b1/vmlinux-81e4f8d6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/25a5029b6ff3/bzImage-81e4f8d6.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+9d5392...@syzkaller.appspotmail.com

==================================================================
BUG: KCSAN: data-race in mon_reader_del / usb_hcd_submit_urb

write to 0xffff88810148d088 of 4 bytes by task 10567 on cpu 0:
mon_stop drivers/usb/mon/mon_main.c:166 [inline]
mon_reader_del+0x1bd/0x260 drivers/usb/mon/mon_main.c:73
mon_bin_release+0x66/0x120 drivers/usb/mon/mon_bin.c:793
__fput+0x2ac/0x640 fs/file_table.c:464
____fput+0x1c/0x30 fs/file_table.c:492
task_work_run+0x13a/0x1a0 kernel/task_work.c:227
resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0xa8/0x120 kernel/entry/common.c:218
do_syscall_64+0xd6/0x1c0 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f

read to 0xffff88810148d088 of 4 bytes by task 10555 on cpu 1:
usbmon_urb_submit include/linux/usb/hcd.h:723 [inline]
usb_hcd_submit_urb+0x86/0x14d0 drivers/usb/core/hcd.c:1518
usb_submit_urb+0xa80/0xb70 drivers/usb/core/urb.c:581
usb_start_wait_urb+0x91/0x190 drivers/usb/core/message.c:59
usb_internal_control_msg drivers/usb/core/message.c:103 [inline]
usb_control_msg+0x182/0x240 drivers/usb/core/message.c:154
set_port_feature drivers/usb/core/hub.c:464 [inline]
hub_suspend+0x4a2/0x560 drivers/usb/core/hub.c:3964
usb_suspend_interface drivers/usb/core/driver.c:1323 [inline]
usb_suspend_both+0x16a/0x9a0 drivers/usb/core/driver.c:1428
usb_runtime_suspend+0x4a/0xd0 drivers/usb/core/driver.c:1963
__rpm_callback+0x299/0x720 drivers/base/power/runtime.c:394
rpm_callback drivers/base/power/runtime.c:448 [inline]
rpm_suspend+0x6e4/0x1020 drivers/base/power/runtime.c:672
__pm_runtime_suspend+0xf1/0x210 drivers/base/power/runtime.c:1142
pm_runtime_put_sync_autosuspend include/linux/pm_runtime.h:524 [inline]
usb_autosuspend_device+0x40/0x50 drivers/usb/core/driver.c:1692
usbdev_release+0x291/0x4a0 drivers/usb/core/devio.c:1114
__fput+0x2ac/0x640 fs/file_table.c:464
____fput+0x1c/0x30 fs/file_table.c:492
task_work_run+0x13a/0x1a0 kernel/task_work.c:227
get_signal+0xe78/0x1000 kernel/signal.c:2809
arch_do_signal_or_restart+0x95/0x4b0 arch/x86/kernel/signal.c:337
exit_to_user_mode_loop kernel/entry/common.c:111 [inline]
exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]
__syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
syscall_exit_to_user_mode+0x62/0x120 kernel/entry/common.c:218
do_syscall_64+0xd6/0x1c0 arch/x86/entry/common.c:89
entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x00000001 -> 0x00000000

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 UID: 0 PID: 10555 Comm: syz.6.12521 Tainted: G W 6.14.0-rc7-syzkaller-00069-g81e4f8d68c66 #0
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
==================================================================


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.