================================================================== BUG: KASAN: slab-out-of-bounds in memcpy include/linux/string.h:377 [inline] BUG: KASAN: slab-out-of-bounds in udf_find_entry+0xa33/0x1070 fs/udf/namei.c:251 Write of size 105 at addr ffff8880a3181b16 by task syz-executor752/8094 CPU: 0 PID: 8094 Comm: syz-executor752 Not tainted 4.19.211-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022 Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2ef lib/dump_stack.c:118 print_address_description.cold+0x54/0x219 mm/kasan/report.c:256 kasan_report_error.cold+0x8a/0x1b9 mm/kasan/report.c:354 kasan_report+0x8f/0xa0 mm/kasan/report.c:412 memcpy+0x35/0x50 mm/kasan/kasan.c:303 memcpy include/linux/string.h:377 [inline] udf_find_entry+0xa33/0x1070 fs/udf/namei.c:251 udf_lookup fs/udf/namei.c:322 [inline] udf_lookup+0x156/0x270 fs/udf/namei.c:296 lookup_open+0x698/0x1a20 fs/namei.c:3214 do_last fs/namei.c:3327 [inline] path_openat+0x1094/0x2df0 fs/namei.c:3537 do_filp_open+0x18c/0x3f0 fs/namei.c:3567 do_sys_open+0x3b3/0x520 fs/open.c:1085 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x7f01a83bc4e9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fff2a8153c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000055 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f01a83bc4e9 RDX: 00007f01a83bc4e9 RSI: 0000000000000000 RDI: 0000000020000180 RBP: 00007f01a837bac0 R08: 0000000000000000 R09: 0000000000000000 R10: 00005555564e42c0 R11: 0000000000000246 R12: 00007f01a837bb50 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 Allocated by task 8094: kmem_cache_alloc_trace+0x12f/0x380 mm/slab.c:3625 kmalloc include/linux/slab.h:515 [inline] udf_find_entry+0xa82/0x1070 fs/udf/namei.c:241 udf_lookup fs/udf/namei.c:322 [inline] udf_lookup+0x156/0x270 fs/udf/namei.c:296 lookup_open+0x698/0x1a20 fs/namei.c:3214 do_last fs/namei.c:3327 [inline] path_openat+0x1094/0x2df0 fs/namei.c:3537 do_filp_open+0x18c/0x3f0 fs/namei.c:3567 do_sys_open+0x3b3/0x520 fs/open.c:1085 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293 entry_SYSCALL_64_after_hwframe+0x49/0xbe Freed by task 6413: __cache_free mm/slab.c:3503 [inline] kfree+0xcc/0x210 mm/slab.c:3822 __do_execve_file+0x187a/0x2360 fs/exec.c:1862 do_execveat_common fs/exec.c:1879 [inline] do_execve+0x35/0x50 fs/exec.c:1896 call_usermodehelper_exec_async+0x50e/0x6a0 kernel/umh.c:116 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415 The buggy address belongs to the object at ffff8880a3181a80 which belongs to the cache kmalloc-256 of size 256 The buggy address is located 150 bytes inside of 256-byte region [ffff8880a3181a80, ffff8880a3181b80) The buggy address belongs to the page: page:ffffea00028c6040 count:1 mapcount:0 mapping:ffff88813bff07c0 index:0xffff8880a3181080 flags: 0xfff00000000100(slab) raw: 00fff00000000100 ffffea0002d37908 ffffea0002d6e548 ffff88813bff07c0 raw: ffff8880a3181080 ffff8880a3181080 0000000100000007 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff8880a3181a00: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ffff8880a3181a80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff8880a3181b00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 ^ ffff8880a3181b80: fc fc fc fc fc fc fc fc fb fb fb fb fb fb fb fb ffff8880a3181c00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ==================================================================