syzbot


WARNING in hfsplus_bnode_create (2)

Status: upstream: reported C repro on 2026/05/29 20:01
Subsystems: hfs
Labels: prio:low
[Documentation on labels]
Reported-by: syzbot+2bf21610eea63cb2ce93@syzkaller.appspotmail.com
First crash: 11d, last: 2h48m
Cause bisection: failed (error log, bisect log)
  
✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision Error
0c23ccc7-f79e-4fc5-b50c-17846b1382cc assessment-security DenialOfService: ❌ Exploitable: ❌ FilesystemTrigger: ✅ NetworkTrigger: ❌ PeripheralTrigger: ✅ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ WARNING in hfsplus_bnode_create (2) 2026/05/29 22:01 2026/05/29 22:01 2026/05/29 22:05 6b4a844333e83556da95d61d7f207e7ef5cd4bc6
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [hfs?] WARNING in hfsplus_bnode_create (2) 0 (1) 2026/05/29 20:01
Similar bugs (5)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream WARNING in hfsplus_bnode_create hfs -1 C error 1338 56d 1285d 29/29 fixed on 2026/05/21 13:51
linux-5.15 WARNING in hfsplus_bnode_create origin:upstream -1 C error 58 2d07h 1122d 0/3 upstream: reported C repro on 2023/05/13 19:31
linux-4.14 WARNING in hfsplus_bnode_create hfsplus -1 C 1 1219d 1257d 0/1 upstream: reported C repro on 2022/12/29 14:39
linux-4.19 WARNING in hfsplus_bnode_create hfsplus -1 C error 5 1218d 1287d 0/1 upstream: reported C repro on 2022/11/30 07:43
linux-6.1 WARNING in hfsplus_bnode_create origin:upstream missing-backport -1 C error 44 25d 1141d 0/3 upstream: reported C repro on 2023/04/25 07:57

Sample crash report:
WARNING: The mand mount option has been deprecated and
         and is ignored by this kernel. Remove the mand
         option from the mount to silence this warning.
=======================================================
hfsplus: new node 0 already hashed?
------------[ cut here ]------------
1
WARNING: fs/hfsplus/bnode.c:634 at hfsplus_bnode_create+0x45d/0x4f0 fs/hfsplus/bnode.c:634, CPU#0: syz.0.17/5942
Modules linked in:
CPU: 0 UID: 0 PID: 5942 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026
RIP: 0010:hfsplus_bnode_create+0x45d/0x4f0 fs/hfsplus/bnode.c:634
Code: 47 8b 89 ee e8 24 6f 83 fe e9 cf fc ff ff e8 da 88 20 ff 4c 89 f7 e8 92 d0 79 08 48 c7 c7 a0 52 47 8b 89 ee e8 04 6f 83 fe 90 <0f> 0b 90 49 c7 c5 ef ff ff ff eb a9 44 89 f9 80 e1 07 80 c1 03 38
RSP: 0018:ffffc90003a5f5a0 EFLAGS: 00010246
RAX: 0000000000000023 RBX: dffffc0000000000 RCX: 89c16ee503352d00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff5200074be65 R12: 0000000000000000
R13: ffff888039ca0000 R14: ffff888039ca00d0 R15: ffff88802808fc00
FS:  00005555881da500(0000) GS:ffff888126386000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000038b22000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 hfs_bnode_split+0xd2/0x1090 fs/hfsplus/brec.c:248
 hfsplus_brec_insert+0x3bc/0xd70 fs/hfsplus/brec.c:100
 hfsplus_create_cat+0xa64/0x11f0 fs/hfsplus/catalog.c:308
 hfsplus_mknod+0x186/0x3f0 fs/hfsplus/dir.c:538
 hfsplus_mkdir+0x2c/0x40 fs/hfsplus/dir.c:579
 vfs_mkdir+0x40b/0x630 fs/namei.c:5261
 filename_mkdirat+0x289/0x520 fs/namei.c:5294
 __do_sys_mkdirat fs/namei.c:5315 [inline]
 __se_sys_mkdirat+0x35/0x150 fs/namei.c:5312
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0x174/0x580 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7efc691dbcc7
Code: 00 66 90 48 89 f2 b9 00 01 00 00 48 89 fe bf 9c ff ff ff e9 db f7 ff ff 66 2e 0f 1f 84 00 00 00 00 00 90 b8 02 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd3adf41f8 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007ffd3adf4280 RCX: 00007efc691dbcc7
RDX: 00000000000001ff RSI: 0000200000000440 RDI: 00000000ffffff9c
RBP: 0000200000000080 R08: 0000200000000140 R09: 0000000000000000
R10: 0000200000000080 R11: 0000000000000246 R12: 0000200000000440
R13: 00007ffd3adf4240 R14: 0000000000000000 R15: 0000000000000000
 </TASK>

Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/05/28 20:52 upstream eb3f4b7426cf 681715f7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs WARNING in hfsplus_bnode_create
2026/05/28 19:39 upstream eb3f4b7426cf 681715f7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs WARNING in hfsplus_bnode_create
2026/05/28 18:17 upstream eb3f4b7426cf 681715f7 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs WARNING in hfsplus_bnode_create
2026/06/09 08:26 upstream 2d3090a8aeb5 656e94c6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in hfsplus_bnode_create
2026/06/04 13:53 upstream ba3e43a9e601 197909be .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in hfsplus_bnode_create
2026/05/28 17:04 upstream eb3f4b7426cf 681715f7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in hfsplus_bnode_create
* Struck through repros no longer work on HEAD.