[v6.1] BUG: unable to handle kernel paging request in udf_close_lvid

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 3b29299e5f60 Linux 6.1.22
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11acf3a9c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=4a782518325cb082
dashboard link: https://syzkaller.appspot.com/bug?extid=26873a72980f8fa8bc55
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1340caf1c80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10256e85c80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f6cdeb0f8946/disk-3b29299e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/cc5e0da6e9ab/vmlinux-3b29299e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9e31f151a6a5/bzImage-3b29299e.xz
mounted in repro #1: https://storage.googleapis.com/syzbot-assets/4f8f05eef8ca/mount_0.gz
mounted in repro #2: https://storage.googleapis.com/syzbot-assets/1873752259d9/mount_1.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+26873a...@syzkaller.appspotmail.com

loop0: detected capacity change from 0 to 2048
UDF-fs: INFO Mounting volume 'LinuxUDF', timestamp 2022/11/22 14:59 (1000)
BUG: unable to handle page fault for address: ffffed101b7f0ad9
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 23ffee067 P4D 23ffee067 PUD 13fff5067 PMD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 3630 Comm: syz-executor368 Not tainted 6.1.22-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:udf_close_lvid+0x148/0x9a0 fs/udf/super.c:2073
Code: dc 49 83 c4 50 0f 84 f3 00 00 00 49 8d bf c0 00 00 00 48 89 7c 24 40 31 f6 e8 14 5d 8a 07 49 8d 7c 24 18 48 89 f8 48 c1 e8 03 <42> 0f b6 04 28 84 c0 0f 85 3d 05 00 00 4c 89 7c 24 18 4c 89 74 24
RSP: 0018:ffffc90003aafa60 EFLAGS: 00010a02
RAX: 1ffff1101b7f0ad9 RBX: ffff888070c78000 RCX: 0000000000000001
RDX: 0000000000000000 RSI: ffffffff8b3cb740 RDI: ffff8880dbf856c8
RBP: ffffc90003aafb50 R08: dffffc0000000000 R09: fffffbfff1ca4d86
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880dbf856b0
R13: dffffc0000000000 R14: 1ffff92000755f58 R15: ffff88801dd5d800
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffed101b7f0ad9 CR3: 000000002805b000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
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:0x7f4c8fdcdeb9
Code: Unable to access opcode bytes at 0x7f4c8fdcde8f.
RSP: 002b:00007fff64ad4a68 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007f4c8fe623f0 RCX: 00007f4c8fdcdeb9
RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001
RBP: 0000000000000001 R08: ffffffffffffffc0 R09: 00007f4c8fe5ce40
R10: 0000000020000380 R11: 0000000000000246 R12: 00007f4c8fe623f0
R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001
</TASK>
Modules linked in:
CR2: ffffed101b7f0ad9
---[ end trace 0000000000000000 ]---
RIP: 0010:udf_close_lvid+0x148/0x9a0 fs/udf/super.c:2073
Code: dc 49 83 c4 50 0f 84 f3 00 00 00 49 8d bf c0 00 00 00 48 89 7c 24 40 31 f6 e8 14 5d 8a 07 49 8d 7c 24 18 48 89 f8 48 c1 e8 03 <42> 0f b6 04 28 84 c0 0f 85 3d 05 00 00 4c 89 7c 24 18 4c 89 74 24
RSP: 0018:ffffc90003aafa60 EFLAGS: 00010a02
RAX: 1ffff1101b7f0ad9 RBX: ffff888070c78000 RCX: 0000000000000001
RDX: 0000000000000000 RSI: ffffffff8b3cb740 RDI: ffff8880dbf856c8
RBP: ffffc90003aafb50 R08: dffffc0000000000 R09: fffffbfff1ca4d86
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff8880dbf856b0
R13: dffffc0000000000 R14: 1ffff92000755f58 R15: ffff88801dd5d800
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffed101b7f0ad9 CR3: 000000002805b000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess), 1 bytes skipped:
0: 49 83 c4 50 add $0x50,%r12
4: 0f 84 f3 00 00 00 je 0xfd
a: 49 8d bf c0 00 00 00 lea 0xc0(%r15),%rdi
11: 48 89 7c 24 40 mov %rdi,0x40(%rsp)
16: 31 f6 xor %esi,%esi
18: e8 14 5d 8a 07 callq 0x78a5d31
1d: 49 8d 7c 24 18 lea 0x18(%r12),%rdi
22: 48 89 f8 mov %rdi,%rax
25: 48 c1 e8 03 shr $0x3,%rax
* 29: 42 0f b6 04 28 movzbl (%rax,%r13,1),%eax <-- trapping instruction
2e: 84 c0 test %al,%al
30: 0f 85 3d 05 00 00 jne 0x573
36: 4c 89 7c 24 18 mov %r15,0x18(%rsp)
3b: 4c rex.WR
3c: 89 .byte 0x89
3d: 74 24 je 0x63


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches