==================================================================
BUG: KASAN: slab-out-of-bounds in udf_write_aext+0x4c0/0x668 fs/udf/inode.c:2110
Write of size 4 at addr ffff0000cc2c03f0 by task syz.1.264/5393

CPU: 0 PID: 5393 Comm: syz.1.264 Not tainted 5.15.168-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/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+0x4c0/0x668 fs/udf/inode.c:2110
 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 1:
 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_node_trace+0x2ac/0x4c4 mm/slub.c:3275
 kmalloc_node include/linux/slab.h:609 [inline]
 kzalloc_node include/linux/slab.h:732 [inline]
 __alloc_disk_node+0x7c/0x440 block/genhd.c:1287
 __blk_mq_alloc_disk+0xe8/0x154 block/blk-mq.c:3172
 nbd_dev_add+0x338/0x9ac drivers/block/nbd.c:1728
 nbd_init+0x20c/0x254 drivers/block/nbd.c:2483
 do_one_initcall+0x234/0x990 init/main.c:1302
 do_initcall_level+0x154/0x214 init/main.c:1375
 do_initcalls+0x58/0xac init/main.c:1391
 do_basic_setup+0x8c/0xa0 init/main.c:1410
 kernel_init_freeable+0x460/0x640 init/main.c:1615
 kernel_init+0x24/0x294 init/main.c:1506
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:870

The buggy address belongs to the object at ffff0000cc2c0000
 which belongs to the cache kmalloc-512 of size 512
The buggy address is located 496 bytes to the right of
 512-byte region [ffff0000cc2c0000, ffff0000cc2c0200)
The buggy address belongs to the page:
page:00000000889fc280 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10c2c0
head:00000000889fc280 order:2 compound_mapcount:0 compound_pincount:0
flags: 0x5ffc00000010200(slab|head|node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000010200 fffffc0003214c00 0000000500000005 ffff0000c0002600
raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff0000cc2c0280: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff0000cc2c0300: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff0000cc2c0380: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
                                                             ^
 ffff0000cc2c0400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff0000cc2c0480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================