UDF-fs: Scanning with blocksize 2048 failed
UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000)
==================================================================
BUG: KASAN: slab-out-of-bounds in udf_write_aext+0x780/0x860 fs/udf/inode.c:2065
Write of size 4 at addr ffff8880944387b0 by task syz-executor.2/2702

CPU: 0 PID: 2702 Comm: syz-executor.2 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/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 mm/kasan/report.c:412 [inline]
 __asan_report_store_n_noabort+0x8b/0xa0 mm/kasan/report.c:449
 udf_write_aext+0x780/0x860 fs/udf/inode.c:2065
 udf_add_entry+0xdab/0x2a20 fs/udf/namei.c:496
 udf_mkdir+0x145/0x650 fs/udf/namei.c:693
 vfs_mkdir+0x508/0x7a0 fs/namei.c:3819
 do_mkdirat+0x262/0x2d0 fs/namei.c:3842
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7fa8225690d9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 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 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fa820adb168 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007fa822688f80 RCX: 00007fa8225690d9
RDX: 0000000000000000 RSI: 0000000020000180 RDI: 0000000000000004
RBP: 00007fa8225c4ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffd3ba8d95f R14: 00007fa820adb300 R15: 0000000000022000

Allocated by task 2702:
 __do_kmalloc mm/slab.c:3727 [inline]
 __kmalloc+0x15a/0x3c0 mm/slab.c:3736
 kmalloc include/linux/slab.h:520 [inline]
 kzalloc include/linux/slab.h:709 [inline]
 udf_new_inode+0xbb3/0xf30 fs/udf/ialloc.c:70
 udf_mkdir+0xa8/0x650 fs/udf/namei.c:686
 vfs_mkdir+0x508/0x7a0 fs/namei.c:3819
 do_mkdirat+0x262/0x2d0 fs/namei.c:3842
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe

Freed by task 1694:
 __cache_free mm/slab.c:3503 [inline]
 kfree+0xcc/0x210 mm/slab.c:3822
 do_delayed_call include/linux/delayed_call.h:28 [inline]
 put_link fs/namei.c:883 [inline]
 step_into fs/namei.c:1773 [inline]
 do_last fs/namei.c:3386 [inline]
 path_openat+0xb09/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

The buggy address belongs to the object at ffff8880944387c0
 which belongs to the cache kmalloc-4096 of size 4096
The buggy address is located 16 bytes to the left of
 4096-byte region [ffff8880944387c0, ffff8880944397c0)
The buggy address belongs to the page:
page:ffffea0002510e00 count:1 mapcount:0 mapping:ffff88813bff0dc0 index:0x0 compound_mapcount: 0
flags: 0xfff00000008100(slab|head)
raw: 00fff00000008100 ffffea00024cbc88 ffffea00010d0d88 ffff88813bff0dc0
raw: 0000000000000000 ffff8880944387c0 0000000100000001 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff888094438680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
 ffff888094438700: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff888094438780: fc fc fc fc fc fc fc fc 00 00 00 00 00 00 00 00
                                     ^
 ffff888094438800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff888094438880: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================