syzbot

loop0: detected capacity change from 0 to 2048
UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000)
==================================================================
BUG: KASAN: use-after-free in udf_close_lvid.isra.0+0x4a7/0x550 fs/udf/super.c:2072
Write of size 1 at addr ffff888158290aa8 by task syz-executor364/5062

CPU: 1 PID: 5062 Comm: syz-executor364 Not tainted 6.1.0-syzkaller-11674-g84e57d292203 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0xd1/0x138 lib/dump_stack.c:106
 print_address_description mm/kasan/report.c:306 [inline]
 print_report+0x15e/0x45d mm/kasan/report.c:417
 kasan_report+0xbf/0x1f0 mm/kasan/report.c:517
 udf_close_lvid.isra.0+0x4a7/0x550 fs/udf/super.c:2072
 udf_put_super+0x1bb/0x230 fs/udf/super.c:2359
 generic_shutdown_super+0x158/0x410 fs/super.c:492
 kill_block_super+0x9b/0xf0 fs/super.c:1386
 deactivate_locked_super+0x98/0x160 fs/super.c:332
 deactivate_super+0xb1/0xd0 fs/super.c:363
 cleanup_mnt+0x2ae/0x3d0 fs/namespace.c:1291
 task_work_run+0x16f/0x270 kernel/task_work.c:179
 exit_task_work include/linux/task_work.h:38 [inline]
 do_exit+0xaa8/0x2950 kernel/exit.c:867
 do_group_exit+0xd4/0x2a0 kernel/exit.c:1010
 __do_sys_exit_group kernel/exit.c:1021 [inline]
 __se_sys_exit_group kernel/exit.c:1019 [inline]
 __x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1019
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f2aba16e009
Code: Unable to access opcode bytes at 0x7f2aba16dfdf.
RSP: 002b:00007ffc88061b88 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f2aba1de350 RCX: 00007f2aba16e009
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 0000000000000001 R08: ffffffffffffffc0 R09: 000000000000000c
R10: 000080001d00c0d0 R11: 0000000000000246 R12: 00007f2aba1de350
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
 </TASK>

The buggy address belongs to the physical page:
page:ffffea000560a400 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x158290
flags: 0x57ff00000000000(node=1|zone=2|lastcpupid=0x7ff)
raw: 057ff00000000000 ffffea000560a408 ffffea000560a408 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:
 ffff888158290980: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff888158290a00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff888158290a80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                                  ^
 ffff888158290b00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff888158290b80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================