loop4: detected capacity change from 0 to 2048
UDF-fs: INFO Mounting volume 'LiuxUDF', timestamp 2022/11/22 14:59 (1000)
==================================================================
BUG: KASAN: slab-out-of-bounds in udf_write_aext+0x4c0/0x668 fs/udf/inode.c:2105
Write of size 4 at addr ffff0000efaeeff0 by task syz.4.915/6616

CPU: 1 PID: 6616 Comm: syz.4.915 Not tainted 6.1.111-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
Call trace:
 dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
 print_address_description mm/kasan/report.c:284 [inline]
 print_report+0x174/0x4c0 mm/kasan/report.c:395
 kasan_report+0xd4/0x130 mm/kasan/report.c:495
 __asan_report_store_n_noabort+0x28/0x34 mm/kasan/report_generic.c:367
 udf_write_aext+0x4c0/0x668 fs/udf/inode.c:2105
 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:4108
 do_mkdirat+0x220/0x510 fs/namei.c:4133
 __do_sys_mkdirat fs/namei.c:4148 [inline]
 __se_sys_mkdirat fs/namei.c:4146 [inline]
 __arm64_sys_mkdirat+0x90/0xa8 fs/namei.c:4146
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

Allocated by task 123:
 kasan_save_stack mm/kasan/common.c:45 [inline]
 kasan_set_track+0x4c/0x80 mm/kasan/common.c:52
 kasan_save_alloc_info+0x24/0x30 mm/kasan/generic.c:505
 ____kasan_kmalloc mm/kasan/common.c:374 [inline]
 __kasan_kmalloc+0xac/0xc4 mm/kasan/common.c:383
 kasan_kmalloc include/linux/kasan.h:211 [inline]
 kmalloc_trace+0x7c/0x94 mm/slab_common.c:1031
 kmalloc include/linux/slab.h:557 [inline]
 tipc_sub_subscribe+0x130/0x7a0 net/tipc/subscr.c:146
 tipc_conn_rcv_sub+0x124/0x318 net/tipc/topsrv.c:377
 tipc_conn_rcv_from_sock net/tipc/topsrv.c:407 [inline]
 tipc_conn_recv_work+0x2b4/0x3b0 net/tipc/topsrv.c:423
 process_one_work+0x7ac/0x1404 kernel/workqueue.c:2292
 worker_thread+0x8e4/0xfec kernel/workqueue.c:2439
 kthread+0x250/0x2d8 kernel/kthread.c:376
 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:864

The buggy address belongs to the object at ffff0000efaeec00
 which belongs to the cache kmalloc-512 of size 512
The buggy address is located 496 bytes to the right of
 512-byte region [ffff0000efaeec00, ffff0000efaeee00)

The buggy address belongs to the physical page:
page:00000000769143c3 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x12faec
head:00000000769143c3 order:2 compound_mapcount:0 compound_pincount:0
flags: 0x5ffc00000010200(slab|head|node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000010200 fffffc0003beb700 dead000000000002 ffff0000c0002600
raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff0000efaeee80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff0000efaeef00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff0000efaeef80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
                                                             ^
 ffff0000efaef000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff0000efaef080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================