==================================================================
BUG: KASAN: use-after-free in udf_close_lvid+0x6a8/0x9a0 fs/udf/super.c:2039
Write of size 1 at addr ffff88808bec9708 by task syz-executor.3/5120

CPU: 0 PID: 5120 Comm: syz-executor.3 Not tainted 6.3.0-rc2-syzkaller-00016-g4979bf866825 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/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:319 [inline]
 print_report+0x163/0x540 mm/kasan/report.c:430
 kasan_report+0x176/0x1b0 mm/kasan/report.c:536
 udf_close_lvid+0x6a8/0x9a0 fs/udf/super.c:2039
 udf_put_super+0xcd/0x160 fs/udf/super.c:2326
 generic_shutdown_super+0x134/0x340 fs/super.c:491
 kill_block_super+0x7e/0xe0 fs/super.c:1398
 deactivate_locked_super+0xa4/0x110 fs/super.c:331
 cleanup_mnt+0x426/0x4c0 fs/namespace.c:1177
 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:203
 __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]
 syscall_exit_to_user_mode+0x64/0x2e0 kernel/entry/common.c:296
 do_syscall_64+0x4d/0xc0 arch/x86/entry/common.c:86
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7feca148d567
Code: ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 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 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffda91c0fb8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007feca148d567
RDX: 00007ffda91c108b RSI: 000000000000000a RDI: 00007ffda91c1080
RBP: 00007ffda91c1080 R08: 00000000ffffffff R09: 00007ffda91c0e50
R10: 00005555556b98d3 R11: 0000000000000246 R12: 00007feca14e6b74
R13: 00007ffda91c2140 R14: 00005555556b9810 R15: 00007ffda91c2180
 </TASK>

The buggy address belongs to the physical page:
page:ffffea00022fb240 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x8bec9
flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000000 ffffea00022fb248 ffffea00022fb248 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:
 ffff88808bec9600: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88808bec9680: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff88808bec9700: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                      ^
 ffff88808bec9780: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff88808bec9800: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================