Hello, syzbot found the following issue on: HEAD commit: fbafc3e621c3 Merge tag 'for_linus' of git://git.kernel.org.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=10ae11cee80000 kernel config: https://syzkaller.appspot.com/x/.config?x=e81921f96ae24ec0 dashboard link: https://syzkaller.appspot.com/bug?extid=9b4adfed366b14496e7e compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1635d436e80000 C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15e8171ae80000 Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/76e4a40f41aa/disk-fbafc3e6.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/a2f88511ce98/vmlinux-fbafc3e6.xz kernel image: https://storage.googleapis.com/syzbot-assets/2b21933ed8f1/bzImage-fbafc3e6.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+9b4adfed366b14496e7e@xxxxxxxxxxxxxxxxxxxxxxxxx Warning: Permanently added '10.128.0.162' (ED25519) to the list of known hosts. executing program executing program BUG: memory leak unreferenced object 0xffff88810af03840 (size 16): comm "syz-executor111", pid 5038, jiffies 4294942820 (age 13.250s) hex dump (first 16 bytes): 80 8b 89 0b 81 88 ff ff 04 00 00 00 04 00 00 00 ................ backtrace: [<ffffffff816346ed>] kmemleak_alloc_recursive include/linux/kmemleak.h:42 [inline] [<ffffffff816346ed>] slab_post_alloc_hook mm/slab.h:766 [inline] [<ffffffff816346ed>] slab_alloc_node mm/slub.c:3478 [inline] [<ffffffff816346ed>] __kmem_cache_alloc_node+0x2dd/0x3f0 mm/slub.c:3517 [<ffffffff8157f315>] kmalloc_trace+0x25/0x90 mm/slab_common.c:1098 [<ffffffff82cfd7fa>] kmalloc include/linux/slab.h:600 [inline] [<ffffffff82cfd7fa>] kzalloc include/linux/slab.h:721 [inline] [<ffffffff82cfd7fa>] get_sg_table.isra.0+0x2a/0xe0 drivers/dma-buf/udmabuf.c:93 [<ffffffff82cfd943>] begin_cpu_udmabuf+0x63/0xa0 drivers/dma-buf/udmabuf.c:156 [<ffffffff82cf114b>] dma_buf_begin_cpu_access+0x3b/0xc0 drivers/dma-buf/dma-buf.c:1402 [<ffffffff82cf1d90>] dma_buf_ioctl+0x550/0x660 drivers/dma-buf/dma-buf.c:475 [<ffffffff816bf4a2>] vfs_ioctl fs/ioctl.c:51 [inline] [<ffffffff816bf4a2>] __do_sys_ioctl fs/ioctl.c:871 [inline] [<ffffffff816bf4a2>] __se_sys_ioctl fs/ioctl.c:857 [inline] [<ffffffff816bf4a2>] __x64_sys_ioctl+0xf2/0x140 fs/ioctl.c:857 [<ffffffff84b71e2f>] do_syscall_x64 arch/x86/entry/common.c:52 [inline] [<ffffffff84b71e2f>] do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:83 [<ffffffff84c0008b>] entry_SYSCALL_64_after_hwframe+0x63/0x6b BUG: memory leak unreferenced object 0xffff88810b898b80 (size 128): comm "syz-executor111", pid 5038, jiffies 4294942820 (age 13.250s) hex dump (first 32 bytes): c0 09 2a 04 00 ea ff ff 00 00 00 00 00 10 00 00 ..*............. 00 70 82 0a 01 00 00 00 00 10 00 00 00 00 00 00 .p.............. backtrace: [<ffffffff816346ed>] kmemleak_alloc_recursive include/linux/kmemleak.h:42 [inline] [<ffffffff816346ed>] slab_post_alloc_hook mm/slab.h:766 [inline] [<ffffffff816346ed>] slab_alloc_node mm/slub.c:3478 [inline] [<ffffffff816346ed>] __kmem_cache_alloc_node+0x2dd/0x3f0 mm/slub.c:3517 [<ffffffff8157f9bb>] __do_kmalloc_node mm/slab_common.c:1006 [inline] [<ffffffff8157f9bb>] __kmalloc+0x4b/0x150 mm/slab_common.c:1020 [<ffffffff8251661f>] kmalloc_array include/linux/slab.h:637 [inline] [<ffffffff8251661f>] sg_kmalloc lib/scatterlist.c:167 [inline] [<ffffffff8251661f>] get_next_sg lib/scatterlist.c:402 [inline] [<ffffffff8251661f>] sg_alloc_append_table_from_pages+0x35f/0x770 lib/scatterlist.c:526 [<ffffffff82516abc>] sg_alloc_table_from_pages_segment+0x8c/0x120 lib/scatterlist.c:586 [<ffffffff82cfd82e>] sg_alloc_table_from_pages include/linux/scatterlist.h:477 [inline] [<ffffffff82cfd82e>] get_sg_table.isra.0+0x5e/0xe0 drivers/dma-buf/udmabuf.c:96 [<ffffffff82cfd943>] begin_cpu_udmabuf+0x63/0xa0 drivers/dma-buf/udmabuf.c:156 [<ffffffff82cf114b>] dma_buf_begin_cpu_access+0x3b/0xc0 drivers/dma-buf/dma-buf.c:1402 [<ffffffff82cf1d90>] dma_buf_ioctl+0x550/0x660 drivers/dma-buf/dma-buf.c:475 [<ffffffff816bf4a2>] vfs_ioctl fs/ioctl.c:51 [inline] [<ffffffff816bf4a2>] __do_sys_ioctl fs/ioctl.c:871 [inline] [<ffffffff816bf4a2>] __se_sys_ioctl fs/ioctl.c:857 [inline] [<ffffffff816bf4a2>] __x64_sys_ioctl+0xf2/0x140 fs/ioctl.c:857 [<ffffffff84b71e2f>] do_syscall_x64 arch/x86/entry/common.c:52 [inline] [<ffffffff84b71e2f>] do_syscall_64+0x3f/0x110 arch/x86/entry/common.c:83 [<ffffffff84c0008b>] entry_SYSCALL_64_after_hwframe+0x63/0x6b --- 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 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
