[syzbot] [input?] [usb?] memory leak in __usbhid_submit_report (2)
syzbot <[email protected]>
| Newsgroups | org.kernel.vger.linux-input,org.kernel.vger.linux-kernel,org.kernel.vger.linux-usb |
|---|---|
| Message-ID | <[email protected]> |
Hello, syzbot found the following issue on: HEAD commit: 2f1baf1fc892 Merge tag 'trace-v7.2-rc7' of git://git.kerne.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=14e2ca25580000 kernel config: https://syzkaller.appspot.com/x/.config?x=11ad91fcc8fa7933 dashboard link: https://syzkaller.appspot.com/bug?extid=e2c057ea576d2644e2be compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14c6a949580000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17f43279580000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/3bba3e686406/disk-2f1baf1f.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/b8b74261d93c/vmlinux-2f1baf1f.xz kernel image: https://storage.googleapis.com/syzbot-assets/952847c3fd89/bzImage-2f1baf1f.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: [email protected] BUG: memory leak unreferenced object 0xffff8881279df600 (size 16): comm "syz.5.22", pid 6103, jiffies 4294942311 hex dump (first 16 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 0): kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline] slab_post_alloc_hook mm/slub.c:4597 [inline] slab_alloc_node mm/slub.c:4917 [inline] __do_kmalloc_node mm/slub.c:5333 [inline] __kmalloc_noprof+0x3bf/0x550 mm/slub.c:5359 __usbhid_submit_report+0x362/0x4c0 drivers/hid/usbhid/hid-core.c:541 usbhid_submit_report drivers/hid/usbhid/hid-core.c:640 [inline] usbhid_request+0x5b/0xa0 drivers/hid/usbhid/hid-core.c:1303 hid_hw_request+0x3c/0x70 drivers/hid/hid-core.c:2521 hiddev_ioctl+0x33e/0x9d0 drivers/hid/usbhid/hiddev.c:726 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0xf4/0x140 fs/ioctl.c:583 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xf8/0x610 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF --- 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 [email protected]. 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 syzbot to run the reproducer, reply with: #syz test: git://repo/address.git branch-or-commit-hash If you attach or paste a git patch, syzbot will apply it before testing. 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