syzbot


KASAN: wild-memory-access Read in hfsplus_bnode_dump

Status: upstream: reported C repro on 2023/04/17 05:34
Subsystems: hfs
[Documentation on labels]
Reported-by: syzbot+f687659f3c2acfa34201@syzkaller.appspotmail.com
First crash: 370d, last: 22d
Cause bisection: failed (error log, bisect log)
  
Fix bisection: failed (error log, bisect log)
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [hfs?] KASAN: wild-memory-access Read in hfsplus_bnode_dump 0 (2) 2023/05/25 20:03
Similar bugs (1)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 KASAN: wild-memory-access Read in hfsplus_bnode_dump origin:upstream C 6 28d 295d 0/3 upstream: reported C repro on 2023/06/26 13:24
Last patch testing requests (6)
Created Duration User Patch Repo Result
2024/04/08 21:25 23m retest repro upstream error OK
2024/03/06 21:15 19m retest repro git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci report log
2024/02/21 20:26 11m retest repro upstream report log
2024/01/03 23:58 49m retest repro upstream report log
2023/12/16 08:46 12m retest repro upstream report log
2023/10/25 23:35 16m retest repro upstream report log
Fix bisection attempts (3)
Created Duration User Patch Repo Result
2023/10/07 08:15 21m bisect fix upstream error job log (0)
2023/09/03 04:58 1h24m bisect fix upstream job log (0) log
2023/06/26 23:43 1h02m bisect fix upstream job log (0) log

Sample crash report:
hfsplus: request for non-existent node 65030 in B*Tree
hfsplus: request for non-existent node 65030 in B*Tree
==================================================================
BUG: KASAN: wild-memory-access in memcpy_from_page include/linux/highmem.h:417 [inline]
BUG: KASAN: wild-memory-access in hfsplus_bnode_read fs/hfsplus/bnode.c:32 [inline]
BUG: KASAN: wild-memory-access in hfsplus_bnode_read_u16 fs/hfsplus/bnode.c:45 [inline]
BUG: KASAN: wild-memory-access in hfsplus_bnode_dump+0x403/0xbb0 fs/hfsplus/bnode.c:305
Read of size 2 at addr 000508800000103e by task syz-executor348/5062

CPU: 1 PID: 5062 Comm: syz-executor348 Not tainted 6.8.0-rc3-syzkaller-00010-g6d280f4d760e #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2e0 lib/dump_stack.c:106
 print_report+0xe6/0x540 mm/kasan/report.c:491
 kasan_report+0x142/0x180 mm/kasan/report.c:601
 kasan_check_range+0x282/0x290 mm/kasan/generic.c:189
 __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105
 memcpy_from_page include/linux/highmem.h:417 [inline]
 hfsplus_bnode_read fs/hfsplus/bnode.c:32 [inline]
 hfsplus_bnode_read_u16 fs/hfsplus/bnode.c:45 [inline]
 hfsplus_bnode_dump+0x403/0xbb0 fs/hfsplus/bnode.c:305
 hfsplus_brec_remove+0x42c/0x4f0 fs/hfsplus/brec.c:229
 __hfsplus_delete_attr+0x275/0x450 fs/hfsplus/attributes.c:299
 hfsplus_delete_all_attrs+0x26b/0x3d0 fs/hfsplus/attributes.c:378
 hfsplus_delete_cat+0xb37/0xf70 fs/hfsplus/catalog.c:425
 hfsplus_unlink+0x363/0x790 fs/hfsplus/dir.c:385
 hfsplus_rename+0xc8/0x1c0 fs/hfsplus/dir.c:547
 vfs_rename+0xbdb/0xf00 fs/namei.c:4879
 do_renameat2+0xd94/0x13f0 fs/namei.c:5036
 __do_sys_renameat2 fs/namei.c:5070 [inline]
 __se_sys_renameat2 fs/namei.c:5067 [inline]
 __x64_sys_renameat2+0xd2/0xf0 fs/namei.c:5067
 do_syscall_64+0xf9/0x240
 entry_SYSCALL_64_after_hwframe+0x6f/0x77
RIP: 0033:0x7f37761df679
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 61 17 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 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:00007fff93de14b8 EFLAGS: 00000246 ORIG_RAX: 000000000000013c
RAX: ffffffffffffffda RBX: 00007fff93de1688 RCX: 00007f37761df679
RDX: 0000000000000004 RSI: 00000000200000c0 RDI: 0000000000000005
RBP: 00007f3776252610 R08: 0000000000000000 R09: 00007fff93de1688
R10: 0000000020000180 R11: 0000000000000246 R12: 0000000000000001
R13: 00007fff93de1678 R14: 0000000000000001 R15: 0000000000000001
 </TASK>
==================================================================

Crashes (14):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/02/07 13:12 upstream 6d280f4d760e 6404acf9 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs KASAN: wild-memory-access Read in hfsplus_bnode_dump
2023/10/11 18:14 upstream 1c8b86a3799f 83165b57 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-smack-root KASAN: wild-memory-access Read in hfsplus_bnode_dump
2023/05/25 20:03 upstream 933174ae28ba 0513b3e6 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs KASAN: wild-memory-access Read in hfsplus_bnode_dump
2024/02/04 21:40 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 41bccc98fb79 a67b2c42 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-arm64 KASAN: use-after-free Read in hfsplus_bnode_dump
2024/03/25 16:04 upstream fe46a7dd189e 0ea90952 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: wild-memory-access Read in hfsplus_bnode_dump
2024/03/18 16:14 upstream fe46a7dd189e d615901c .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root KASAN: wild-memory-access Read in hfsplus_bnode_dump
2024/01/13 07:20 upstream 052d534373b7 551587c1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: wild-memory-access Read in hfsplus_bnode_dump
2023/11/24 02:33 upstream d3fa86b1a7b4 5b429f39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: wild-memory-access Read in hfsplus_bnode_dump
2023/05/25 19:47 upstream 933174ae28ba 0513b3e6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: wild-memory-access Read in hfsplus_bnode_dump
2023/05/10 04:20 upstream 1dc3731daf1f 30aa2a7e .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: wild-memory-access Read in hfsplus_bnode_dump
2023/04/23 11:54 upstream 622322f53c6d 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: wild-memory-access Read in hfsplus_bnode_dump
2023/04/22 23:27 upstream 2caeeb9d4a1b 2b32bd34 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: wild-memory-access Read in hfsplus_bnode_dump
2023/04/11 17:45 upstream 0d3eb744aed4 49faf98d .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs KASAN: wild-memory-access Read in hfsplus_bnode_dump
2024/02/04 21:24 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 41bccc98fb79 a67b2c42 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 KASAN: use-after-free Read in hfsplus_bnode_dump
* Struck through repros no longer work on HEAD.