Hello, syzbot found the following issue on: HEAD commit: 28bbe4ea686a Merge tag 'i2c-for-6.11-rc1-second-batch' of .. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=1519f2b1980000 kernel config: https://syzkaller.appspot.com/x/.config?x=fcd331f2f7452dee dashboard link: https://syzkaller.appspot.com/bug?extid=9d34f80f841e948c3fdb compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 userspace arch: i386 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/5547f17fee20/disk-28bbe4ea.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/d509f262f4fb/vmlinux-28bbe4ea.xz kernel image: https://storage.googleapis.com/syzbot-assets/1b4cf478d209/bzImage-28bbe4ea.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+9d34f80f841e948c3fdb@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_write+0xc32/0x1220 drivers/usb/class/usbtmc.c:1606 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] __ia32_sys_write+0x91/0xe0 fs/read_write.c:652 ia32_sys_call+0x2e34/0x40d0 arch/x86/include/generated/asm/syscalls_32.h:5 do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline] __do_fast_syscall_32+0xb0/0x110 arch/x86/entry/common.c:386 do_fast_syscall_32+0x38/0x80 arch/x86/entry/common.c:411 do_SYSENTER_32+0x1f/0x30 arch/x86/entry/common.c:449 entry_SYSENTER_compat_after_hwframe+0x84/0x8e 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_write+0x3d3/0x1220 drivers/usb/class/usbtmc.c:1547 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] __ia32_sys_write+0x91/0xe0 fs/read_write.c:652 ia32_sys_call+0x2e34/0x40d0 arch/x86/include/generated/asm/syscalls_32.h:5 do_syscall_32_irqs_on arch/x86/entry/common.c:165 [inline] __do_fast_syscall_32+0xb0/0x110 arch/x86/entry/common.c:386 do_fast_syscall_32+0x38/0x80 arch/x86/entry/common.c:411 do_SYSENTER_32+0x1f/0x30 arch/x86/entry/common.c:449 entry_SYSENTER_compat_after_hwframe+0x84/0x8e Byte 3587 of 3588 is uninitialized Memory access of size 3588 starts at ffff88804d338000 CPU: 0 UID: 0 PID: 5392 Comm: syz.1.48 Not tainted 6.10.0-syzkaller-12084-g28bbe4ea686a #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
