syzbot

 sign-in | mailing list | source | docs
🐞 Open [871] ≡ Subsystems 🐞 Fixed [4872] 🐞 Invalid [11623] ⬇ Missing Backports [68] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes 💬 Send us feedback

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: 231d, last: 4d23h
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 2 18d 155d 0/3 upstream: reported C repro on 2023/06/26 13:24
▶ ▼ Last patch testing requests (1)
Created Duration User Patch Repo Result
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:
syz-executor236[5027]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
loop0: detected capacity change from 0 to 1024
hfsplus: request for non-existent node 32768 in B*Tree
hfsplus: request for non-existent node 32768 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/0xba0 fs/hfsplus/bnode.c:305
Read of size 2 at addr 000508800000103e by task syz-executor236/5027

CPU: 0 PID: 5027 Comm: syz-executor236 Not tainted 6.6.0-rc5-syzkaller-00055-g1c8b86a3799f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:88 [inline]
 dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
 print_report+0xe6/0x540 mm/kasan/report.c:478
 kasan_report+0x175/0x1b0 mm/kasan/report.c:588
 kasan_check_range+0x27e/0x290 mm/kasan/generic.c:187
 __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/0xba0 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/0x3c0 fs/hfsplus/attributes.c:378
 hfsplus_delete_cat+0xb5c/0xf90 fs/hfsplus/catalog.c:425
 hfsplus_unlink+0x363/0x790 fs/hfsplus/dir.c:385
 vfs_unlink+0x35d/0x5f0 fs/namei.c:4332
 do_unlinkat+0x4a7/0x950 fs/namei.c:4398
 __do_sys_unlink fs/namei.c:4446 [inline]
 __se_sys_unlink fs/namei.c:4444 [inline]
 __x64_sys_unlink+0x49/0x50 fs/namei.c:4444
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f05305505f9
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:00007fffd74fe128 EFLAGS: 00000246 ORIG_RAX: 0000000000000057
RAX: ffffffffffffffda RBX: 00007fffd74fe308 RCX: 00007f05305505f9
RDX: 00007f053054f8f0 RSI: 0000000000000000 RDI: 0000000020000140
RBP: 00007f05305c3610 R08: 0000000000000640 R09: 0000000000000000
R10: 00007fffd74fdff0 R11: 0000000000000246 R12: 0000000000000001
R13: 00007fffd74fe2f8 R14: 0000000000000001 R15: 0000000000000001
 </TASK>
==================================================================

Crashes (8):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
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
* Struck through repros no longer work on HEAD.