Hello,
syzbot found the following issue on:
HEAD commit: d7039b844a1c Linux 6.1.116
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=17f6e0c0580000
kernel config:
https://syzkaller.appspot.com/x/.config?x=e70423a11a31a773
dashboard link:
https://syzkaller.appspot.com/bug?extid=751ecf7838e3d4ecb4a7
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/3797d90cbed7/disk-d7039b84.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/9726bc0bc28f/vmlinux-d7039b84.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/0b4bbd21cac0/Image-d7039b84.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+751ecf...@syzkaller.appspotmail.com
hfsplus: bad catalog entry type
Unable to handle kernel paging request at virtual address dfff800000000008
KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]
Mem abort info:
ESR = 0x0000000096000006
EC = 0x25: DABT (current EL), IL = 32 bits
SET = 0, FnV = 0
EA = 0, S1PTW = 0
FSC = 0x06: level 2 translation fault
Data abort info:
ISV = 0, ISS = 0x00000006
CM = 0, WnR = 0
[dfff800000000008] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4542 Comm: syz-executor Not tainted 6.1.116-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : hfsplus_rename_cat+0x3e4/0xf30 fs/hfsplus/catalog.c:480
lr : hfsplus_rename_cat+0x3a0/0xf30 fs/hfsplus/catalog.c:474
sp : ffff8000232c7540
x29: ffff8000232c79a0 x28: ffff0000d8b6e718 x27: ffff0000e2ddd950
x26: 0000000000000040 x25: 1fffe0001b16dce3 x24: ffff0000f2d87000
x23: ffff700004658ec0 x22: ffff8000232c76e0 x21: dfff800000000000
x20: 00000000000000f8 x19: ffff8000232c7620 x18: ffff8000232c6fa0
x17: ffff800018abc000 x16: ffff8000121e6200 x15: 0000000000000000
x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
x11: 0000000000ff0100 x10: 0000000000000000 x9 : 0000000000000200
x8 : 0000000000000008 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff8000232c77d8 x4 : ffff0000f3f271d4 x3 : ffff8000232c7760
x2 : ffffffffffffffe8 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
hfsplus_rename_cat+0x3e4/0xf30 fs/hfsplus/catalog.c:480
hfsplus_unlink+0x278/0x6a0 fs/hfsplus/dir.c:376
vfs_unlink+0x2f0/0x508 fs/namei.c:4322
do_unlinkat+0x4cc/0x70c fs/namei.c:4390
__do_sys_unlinkat fs/namei.c:4433 [inline]
__se_sys_unlinkat fs/namei.c:4426 [inline]
__arm64_sys_unlinkat+0xcc/0xfc fs/namei.c:4426
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: f940a3f8 9101011a d343ff48 f9001fe8 (38756908)
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
0: f940a3f8 ldr x24, [sp, #320]
4: 9101011a add x26, x8, #0x40
8: d343ff48 lsr x8, x26, #3
c: f9001fe8 str x8, [sp, #56]
* 10: 38756908 ldrb w8, [x8, x21] <-- trapping instruction
---
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 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