Hello, syzbot found the following issue on: HEAD commit: 94ede2a3e913 profiling: remove stale percpu flip buffer va.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=12166111980000 kernel config: https://syzkaller.appspot.com/x/.config?x=2a7cf62669c9536b dashboard link: https://syzkaller.appspot.com/bug?extid=8f282cce71948071c335 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/b4adcb60c426/disk-94ede2a3.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/50bde94d1be7/vmlinux-94ede2a3.xz kernel image: https://storage.googleapis.com/syzbot-assets/0756c72c7478/bzImage-94ede2a3.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+8f282cce71948071c335@xxxxxxxxxxxxxxxxxxxxxxxxx ===================================================== BUG: KMSAN: kernel-usb-infoleak in usb_submit_urb+0x597/0x2350 drivers/usb/core/urb.c:430 usb_submit_urb+0x597/0x2350 drivers/usb/core/urb.c:430 usbtmc_generic_write+0x7b6/0xe80 drivers/usb/class/usbtmc.c:1213 usbtmc_write+0xdbd/0x1220 drivers/usb/class/usbtmc.c:1622 vfs_write+0x493/0x1550 fs/read_write.c:588 ksys_write+0x20f/0x4c0 fs/read_write.c:643 __do_sys_write fs/read_write.c:655 [inline] __se_sys_write fs/read_write.c:652 [inline] __x64_sys_write+0x93/0xe0 fs/read_write.c:652 x64_sys_call+0x3490/0x3c10 arch/x86/include/generated/asm/syscalls_64.h:2 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Uninit was created at: slab_post_alloc_hook mm/slub.c:3994 [inline] slab_alloc_node mm/slub.c:4037 [inline] __kmalloc_cache_noprof+0x4f0/0xb00 mm/slub.c:4184 kmalloc_noprof include/linux/slab.h:681 [inline] usbtmc_create_urb drivers/usb/class/usbtmc.c:757 [inline] usbtmc_generic_write+0x430/0xe80 drivers/usb/class/usbtmc.c:1176 usbtmc_write+0xdbd/0x1220 drivers/usb/class/usbtmc.c:1622 vfs_write+0x493/0x1550 fs/read_write.c:588 ksys_write+0x20f/0x4c0 fs/read_write.c:643 __do_sys_write fs/read_write.c:655 [inline] __se_sys_write fs/read_write.c:652 [inline] __x64_sys_write+0x93/0xe0 fs/read_write.c:652 x64_sys_call+0x3490/0x3c10 arch/x86/include/generated/asm/syscalls_64.h:2 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f Bytes 1-3 of 4 are uninitialized Memory access of size 4 starts at ffff88805376e000 CPU: 1 UID: 0 PID: 5623 Comm: syz.0.70 Not tainted 6.11.0-rc1-syzkaller-00043-g94ede2a3e913 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024 ===================================================== --- 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 syzkaller@xxxxxxxxxxxxxxxx. 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
