==================================================================
BUG: KASAN: use-after-free in udf_close_lvid+0x6a8/0x9a0 fs/udf/super.c:2035
Write of size 1 at addr ffff8880991993e8 by task syz-executor.4/5058

CPU: 1 PID: 5058 Comm: syz-executor.4 Not tainted 6.5.0-rc7-syzkaller-00004-gf7757129e3de #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 print_address_description mm/kasan/report.c:364 [inline]
 print_report+0x163/0x540 mm/kasan/report.c:475
 kasan_report+0x175/0x1b0 mm/kasan/report.c:588
 udf_close_lvid+0x6a8/0x9a0 fs/udf/super.c:2035
 udf_put_super+0xcd/0x160 fs/udf/super.c:2322
 generic_shutdown_super+0x134/0x340 fs/super.c:499
 kill_block_super+0x68/0xa0 fs/super.c:1417
 deactivate_locked_super+0xa4/0x110 fs/super.c:330
 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1254
 task_work_run+0x24a/0x300 kernel/task_work.c:179
 resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
 exit_to_user_mode_loop+0xd9/0x100 kernel/entry/common.c:171
 exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:204
 __syscall_exit_to_user_mode_work kernel/entry/common.c:286 [inline]
 syscall_exit_to_user_mode+0x64/0x280 kernel/entry/common.c:297
 do_syscall_64+0x4d/0xc0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f4e8a07de17
Code: b0 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 b0 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffcf90cebd8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f4e8a07de17
RDX: 0000000000000000 RSI: 000000000000000a RDI: 00007ffcf90cec90
RBP: 00007ffcf90cec90 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffcf90cfd50
R13: 00007f4e8a0c73b9 R14: 00000000000af9e8 R15: 000000000000001e
 </TASK>

The buggy address belongs to the physical page:
page:ffffea0002646640 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x99199
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
page_type: 0xffffffff()
raw: 00fff00000000000 ffffea0002646648 ffffea0002646648 0000000000000000
raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner info is not present (never set?)

Memory state around the buggy address:
 ffff888099199280: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff888099199300: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff888099199380: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                                                          ^
 ffff888099199400: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff888099199480: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================