================================================================== BUG: KASAN: slab-out-of-bounds in udf_write_aext+0x578/0x668 fs/udf/inode.c:2104 Write of size 4 at addr ffff0000e5502ff8 by task syz.3.547/6221 CPU: 1 PID: 6221 Comm: syz.3.547 Not tainted 5.15.167-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 Call trace: dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106 print_address_description+0x7c/0x3f0 mm/kasan/report.c:248 __kasan_report mm/kasan/report.c:434 [inline] kasan_report+0x174/0x1e4 mm/kasan/report.c:451 __asan_report_store_n_noabort+0x40/0x4c mm/kasan/report_generic.c:325 udf_write_aext+0x578/0x668 fs/udf/inode.c:2104 udf_add_entry+0x11e0/0x28b0 fs/udf/namei.c:482 udf_mkdir+0x158/0x7e0 fs/udf/namei.c:681 vfs_mkdir+0x334/0x4e4 fs/namei.c:4065 do_mkdirat+0x20c/0x610 fs/namei.c:4090 __do_sys_mkdirat fs/namei.c:4105 [inline] __se_sys_mkdirat fs/namei.c:4103 [inline] __arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4103 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584 Allocated by task 3602: kasan_save_stack mm/kasan/common.c:38 [inline] kasan_set_track mm/kasan/common.c:46 [inline] set_alloc_info mm/kasan/common.c:434 [inline] ____kasan_kmalloc+0xbc/0xfc mm/kasan/common.c:513 __kasan_kmalloc+0x10/0x1c mm/kasan/common.c:522 kasan_kmalloc include/linux/kasan.h:264 [inline] kmem_cache_alloc_trace+0x27c/0x47c mm/slub.c:3247 kmalloc include/linux/slab.h:591 [inline] kzalloc include/linux/slab.h:721 [inline] mca_alloc net/ipv6/mcast.c:880 [inline] __ipv6_dev_mc_inc+0x3f4/0xa8c net/ipv6/mcast.c:936 ipv6_dev_mc_inc+0x2c/0x3c net/ipv6/mcast.c:957 addrconf_join_solict net/ipv6/addrconf.c:2202 [inline] addrconf_dad_begin net/ipv6/addrconf.c:4019 [inline] addrconf_dad_work+0x320/0x126c net/ipv6/addrconf.c:4146 process_one_work+0x790/0x11b8 kernel/workqueue.c:2310 worker_thread+0x910/0x1034 kernel/workqueue.c:2457 kthread+0x37c/0x45c kernel/kthread.c:334 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870 The buggy address belongs to the object at ffff0000e5502c00 which belongs to the cache kmalloc-512 of size 512 The buggy address is located 504 bytes to the right of 512-byte region [ffff0000e5502c00, ffff0000e5502e00) The buggy address belongs to the page: page:000000003f1fa7c8 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x125500 head:000000003f1fa7c8 order:2 compound_mapcount:0 compound_pincount:0 flags: 0x5ffc00000010200(slab|head|node=0|zone=2|lastcpupid=0x7ff) raw: 05ffc00000010200 dead000000000100 dead000000000122 ffff0000c0002600 raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff0000e5502e80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff0000e5502f00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff0000e5502f80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ^ ffff0000e5503000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff0000e5503080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================