======================================================= UDF-fs: error (device loop0): udf_read_tagged: tag checksum failed, block 99: 0x27 != 0x4d UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000) ================================================================== BUG: KASAN: use-after-free in udf_close_lvid+0x6a4/0x9a0 fs/udf/super.c:2073 Write of size 1 at addr ffff8880aed46b78 by task syz-executor347/3540 CPU: 0 PID: 3540 Comm: syz-executor347 Not tainted 6.1.35-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106 print_address_description mm/kasan/report.c:284 [inline] print_report+0x15f/0x4f0 mm/kasan/report.c:395 kasan_report+0x136/0x160 mm/kasan/report.c:495 udf_close_lvid+0x6a4/0x9a0 fs/udf/super.c:2073 udf_put_super+0xc9/0x160 fs/udf/super.c:2360 generic_shutdown_super+0x130/0x340 fs/super.c:501 kill_block_super+0x7a/0xe0 fs/super.c:1450 deactivate_locked_super+0xa0/0x110 fs/super.c:332 cleanup_mnt+0x490/0x520 fs/namespace.c:1186 task_work_run+0x246/0x300 kernel/task_work.c:179 exit_task_work include/linux/task_work.h:38 [inline] do_exit+0x6fb/0x2300 kernel/exit.c:869 do_group_exit+0x202/0x2b0 kernel/exit.c:1019 __do_sys_exit_group kernel/exit.c:1030 [inline] __se_sys_exit_group kernel/exit.c:1028 [inline] __x64_sys_exit_group+0x3b/0x40 kernel/exit.c:1028 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f00a3c96e19 Code: Unable to access opcode bytes at 0x7f00a3c96def. RSP: 002b:00007ffd12431cd8 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 00007f00a3d3e470 RCX: 00007f00a3c96e19 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001 RBP: 0000000000000001 R08: ffffffffffffffb8 R09: 0000000000000000 R10: 0000000000000022 R11: 0000000000000246 R12: 00007f00a3d3e470 R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001 The buggy address belongs to the physical page: page:ffffea0002bb5180 refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0xaed46 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 ffffea0002bb5188 ffffea0002bb5188 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: ffff8880aed46a00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff8880aed46a80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff8880aed46b00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff8880aed46b80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff8880aed46c00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ==================================================================