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

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 5fa4793a2d2d Linux 6.6.119
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17d05b1a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=691a6769a86ac817
dashboard link: https://syzkaller.appspot.com/bug?extid=f2643eb64ba7eca0a916
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17f983c2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=141e0b1a580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/63699875f1dd/disk-5fa4793a.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8506652fcb6f/vmlinux-5fa4793a.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1b30ceed1710/bzImage-5fa4793a.xz
mounted in repro #1: https://storage.googleapis.com/syzbot-assets/ee24ed9612d9/mount_0.gz
mounted in repro #2: https://storage.googleapis.com/syzbot-assets/e88600fa6208/mount_5.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=1514ab1a580000)

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

BUG: unable to handle page fault for address: ffffed101ebaf80c
#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: 5879 Comm: syz-executor Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:udf_close_lvid+0x152/0x990 fs/udf/super.c:2060
Code: 0f 84 f7 00 00 00 4c 89 6c 24 20 49 8d bd c0 00 00 00 48 89 7c 24 38 31 f6 e8 2a cf 78 07 49 8d 7c 24 18 48 89 f8 48 c1 e8 03 <42> 0f b6 04 38 84 c0 0f 85 07 05 00 00 4c 89 74 24 40 41 c6 44 24
RSP: 0018:ffffc90003297be0 EFLAGS: 00010a06
RAX: 1ffff1101ebaf80c RBX: ffff88805cd9564b RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8afc6f60 RDI: ffff8880f5d7c060
RBP: ffffc90003297cd8 R08: ffffffff8e4a212f R09: 1ffffffff1c94425
R10: dffffc0000000000 R11: fffffbfff1c94426 R12: ffff8880f5d7c048
R13: ffff88801b3ac800 R14: 1ffff92000652f88 R15: dffffc0000000000
FS: 000055558afac500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffed101ebaf80c CR3: 00000000275d3000 CR4: 00000000003506e0
Call Trace:
<TASK>
udf_put_super+0xcc/0x160 fs/udf/super.c:2347
generic_shutdown_super+0x134/0x2b0 fs/super.c:693
kill_block_super+0x44/0x90 fs/super.c:1660
deactivate_locked_super+0x97/0x100 fs/super.c:481
cleanup_mnt+0x429/0x4c0 fs/namespace.c:1259
task_work_run+0x1ce/0x250 kernel/task_work.c:239
resume_user_mode_work include/linux/resume_user_mode.h:49 [inline]
exit_to_user_mode_loop+0xe6/0x110 kernel/entry/common.c:177
exit_to_user_mode_prepare+0xf6/0x180 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f2657790a77
Code: a8 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 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffe9b5c7e18 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 00007f2657813d7d RCX: 00007f2657790a77
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffe9b5c7ed0
RBP: 00007ffe9b5c7ed0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffe9b5c8f60
R13: 00007f2657813d7d R14: 000000000001488d R15: 00007ffe9b5c8fa0
</TASK>
Modules linked in:
CR2: ffffed101ebaf80c
---[ end trace 0000000000000000 ]---
RIP: 0010:udf_close_lvid+0x152/0x990 fs/udf/super.c:2060
Code: 0f 84 f7 00 00 00 4c 89 6c 24 20 49 8d bd c0 00 00 00 48 89 7c 24 38 31 f6 e8 2a cf 78 07 49 8d 7c 24 18 48 89 f8 48 c1 e8 03 <42> 0f b6 04 38 84 c0 0f 85 07 05 00 00 4c 89 74 24 40 41 c6 44 24
RSP: 0018:ffffc90003297be0 EFLAGS: 00010a06
RAX: 1ffff1101ebaf80c RBX: ffff88805cd9564b RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8afc6f60 RDI: ffff8880f5d7c060
RBP: ffffc90003297cd8 R08: ffffffff8e4a212f R09: 1ffffffff1c94425
R10: dffffc0000000000 R11: fffffbfff1c94426 R12: ffff8880f5d7c048
R13: ffff88801b3ac800 R14: 1ffff92000652f88 R15: dffffc0000000000
FS: 000055558afac500(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffed101ebaf80c CR3: 00000000275d3000 CR4: 00000000003506e0
----------------
Code disassembly (best guess):
0: 0f 84 f7 00 00 00 je 0xfd
6: 4c 89 6c 24 20 mov %r13,0x20(%rsp)
b: 49 8d bd c0 00 00 00 lea 0xc0(%r13),%rdi
12: 48 89 7c 24 38 mov %rdi,0x38(%rsp)
17: 31 f6 xor %esi,%esi
19: e8 2a cf 78 07 call 0x778cf48
1e: 49 8d 7c 24 18 lea 0x18(%r12),%rdi
23: 48 89 f8 mov %rdi,%rax
26: 48 c1 e8 03 shr $0x3,%rax
* 2a: 42 0f b6 04 38 movzbl (%rax,%r15,1),%eax <-- trapping instruction
2f: 84 c0 test %al,%al
31: 0f 85 07 05 00 00 jne 0x53e
37: 4c 89 74 24 40 mov %r14,0x40(%rsp)
3c: 41 rex.B
3d: c6 .byte 0xc6
3e: 44 rex.R
3f: 24 .byte 0x24


---
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup