[syzbot] [udf?] BUG: unable to handle kernel paging request in lookup_one_qstr_excl

From: syzbot
Date: Fri Feb 14 2025 - 14:58:47 EST

Next message: syzbot: "[syzbot] [block?] BUG: corrupted list in loop_process_work"
Previous message: Dave Hansen: "Re: [RFC 1/1] x86/vmemmap: Add missing update of PML4 table / PML5 table entry"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hello,

syzbot found the following issue on:

HEAD commit: 7b7a883c7f4d Add linux-next specific files for 20250213
git tree: linux-next
console+strace: https://syzkaller.appspot.com/x/log.txt?x=116913f8580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5fce2f4fd0c881e1
dashboard link: https://syzkaller.appspot.com/bug?extid=2d18bb4b8a11cab7ab13
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17f8fbdf980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=156913f8580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/f96ca702937a/disk-7b7a883c.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/901577be06a5/vmlinux-7b7a883c.xz
kernel image: https://storage.googleapis.com/syzbot-assets/61175f206a2f/bzImage-7b7a883c.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/31908970193f/mount_0.gz

The issue was bisected to:

commit 22d9d5e93d0eaf7e8662602713b24e9b6171759f
Author: NeilBrown <neilb@xxxxxxx>
Date: Fri Feb 7 03:36:48 2025 +0000

VFS: add common error checks to lookup_one_qstr_excl()

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=114ba1a4580000
final oops: https://syzkaller.appspot.com/x/report.txt?x=134ba1a4580000
console output: https://syzkaller.appspot.com/x/log.txt?x=154ba1a4580000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+2d18bb4b8a11cab7ab13@xxxxxxxxxxxxxxxxxxxxxxxxx
Fixes: 22d9d5e93d0e ("VFS: add common error checks to lookup_one_qstr_excl()")

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)
UDF-fs: error (device loop0): udf_verify_fi: directory (ino 1376) has entry where CRC length (63772) does not match entry length (28)
BUG: unable to handle page fault for address: ffffffffffffff8b
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD e93c067 P4D e93c067 PUD e93e067 PMD 0
Oops: Oops: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 0 UID: 0 PID: 5835 Comm: syz-executor196 Not tainted 6.14.0-rc2-next-20250213-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024
RIP: 0010:__d_entry_type include/linux/dcache.h:416 [inline]
RIP: 0010:d_is_miss include/linux/dcache.h:421 [inline]
RIP: 0010:d_is_negative include/linux/dcache.h:467 [inline]
RIP: 0010:lookup_one_qstr_excl+0x162/0x370 fs/namei.c:1696
Code: d3 66 90 48 85 c0 0f 85 58 01 00 00 e8 17 dd 84 ff 4c 89 f0 48 c1 e8 03 42 0f b6 04 28 84 c0 0f 85 57 01 00 00 bb 00 00 38 00 <41> 23 1e 44 89 fd 81 e5 00 00 02 00 89 de 09 ee 31 ff e8 27 e1 84
RSP: 0018:ffffc90003f2fcb8 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000380000 RCX: ffff888034c01e00
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000001
RBP: ffff888074918164 R08: ffff88807ab8fe1b R09: 1ffff1100f571fc3
R10: dffffc0000000000 R11: ffffed100f571fc4 R12: ffff88807ab8fd60
R13: dffffc0000000000 R14: ffffffffffffff8b R15: 0000000000060000
FS: 0000555565c15380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffff8b CR3: 00000000776ac000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
filename_create+0x282/0x480 fs/namei.c:4091
do_mkdirat+0xbd/0x3a0 fs/namei.c:4322
__do_sys_mkdir fs/namei.c:4350 [inline]
__se_sys_mkdir fs/namei.c:4348 [inline]
__x64_sys_mkdir+0x6c/0x80 fs/namei.c:4348
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fd68a577a57
Code: ff ff 77 07 31 c0 c3 0f 1f 40 00 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 b8 53 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:00007ffc24c81108 EFLAGS: 00000246 ORIG_RAX: 0000000000000053
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fd68a577a57
RDX: 0000000000000000 RSI: 00000000000001ff RDI: 0000400000000080
RBP: 0000400000000080 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc24c811a0 R14: 0000000000000000 R15: 0000000000000000
</TASK>
Modules linked in:
CR2: ffffffffffffff8b
---[ end trace 0000000000000000 ]---
RIP: 0010:__d_entry_type include/linux/dcache.h:416 [inline]
RIP: 0010:d_is_miss include/linux/dcache.h:421 [inline]
RIP: 0010:d_is_negative include/linux/dcache.h:467 [inline]
RIP: 0010:lookup_one_qstr_excl+0x162/0x370 fs/namei.c:1696
Code: d3 66 90 48 85 c0 0f 85 58 01 00 00 e8 17 dd 84 ff 4c 89 f0 48 c1 e8 03 42 0f b6 04 28 84 c0 0f 85 57 01 00 00 bb 00 00 38 00 <41> 23 1e 44 89 fd 81 e5 00 00 02 00 89 de 09 ee 31 ff e8 27 e1 84
RSP: 0018:ffffc90003f2fcb8 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 0000000000380000 RCX: ffff888034c01e00
RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000001
RBP: ffff888074918164 R08: ffff88807ab8fe1b R09: 1ffff1100f571fc3
R10: dffffc0000000000 R11: ffffed100f571fc4 R12: ffff88807ab8fd60
R13: dffffc0000000000 R14: ffffffffffffff8b R15: 0000000000060000
FS: 0000555565c15380(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffffffffff8b CR3: 00000000776ac000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
0: d3 66 90 shll %cl,-0x70(%rsi)
3: 48 85 c0 test %rax,%rax
6: 0f 85 58 01 00 00 jne 0x164
c: e8 17 dd 84 ff call 0xff84dd28
11: 4c 89 f0 mov %r14,%rax
14: 48 c1 e8 03 shr $0x3,%rax
18: 42 0f b6 04 28 movzbl (%rax,%r13,1),%eax
1d: 84 c0 test %al,%al
1f: 0f 85 57 01 00 00 jne 0x17c
25: bb 00 00 38 00 mov $0x380000,%ebx
* 2a: 41 23 1e and (%r14),%ebx <-- trapping instruction
2d: 44 89 fd mov %r15d,%ebp
30: 81 e5 00 00 02 00 and $0x20000,%ebp
36: 89 de mov %ebx,%esi
38: 09 ee or %ebp,%esi
3a: 31 ff xor %edi,%edi
3c: e8 .byte 0xe8
3d: 27 (bad)
3e: e1 84 loope 0xffffffc4

---
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 syzkaller@xxxxxxxxxxxxxxxx.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
For information about bisection process see: https://goo.gl/tpsmEJ#bisection

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

Next message: syzbot: "[syzbot] [block?] BUG: corrupted list in loop_process_work"
Previous message: Dave Hansen: "Re: [RFC 1/1] x86/vmemmap: Add missing update of PML4 table / PML5 table entry"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]