memory leak in __hfs_bnode_create

Status: upstream: reported C repro on 2026/04/17 01:56
Subsystems: hfs
Labels: prio:normal
[Documentation on labels]
Reported-by: syzbot+98547b0428b6a6a3467c@syzkaller.appspotmail.com
First crash: 146d, last: 5d17h
▶ ▼ ✨ AI Jobs (1)
ID Workflow Result Correct Bug Created Started Finished Revision
0e8886b9 assessment-security DenialOfService: ✅ Exploitable: ❌ FilesystemTrigger: ✅ NetworkTrigger: ❌ PeripheralTrigger: ❌ RemoteTrigger: ❌ Unprivileged: ❌ UserNamespace: ❌ VMGuestTrigger: ❌ VMHostTrigger: ❌ ❓ memory leak in __hfs_bnode_create 2026/05/21 04:05 2026/05/21 04:05 2026/05/21 04:40 cf874a1c
▶ ▼ Discussions (3)
Title Replies (including bot) Last reply
[syzbot] Monthly hfs report (Aug 2026) 0 (1) 2026/08/05 00:00
[PATCH] hfsplus: Supports freeing newly created tree head 5 (5) 2026/04/28 02:37
[syzbot] [hfs?] memory leak in __hfs_bnode_create 5 (11) 2026/04/17 06:58
▶ ▼ Last patch testing requests (13)
Created Duration User Patch Repo Result
2026/06/20 10:10 27m retest repro upstream report log
2026/06/20 10:10 25m retest repro upstream report log
2026/06/20 10:10 29m retest repro upstream report log
2026/05/31 16:20 21m retest repro upstream report log
2026/05/31 16:20 25m retest repro upstream report log
2026/05/31 16:20 25m retest repro upstream report log
2026/05/31 16:20 44m retest repro upstream report log
2026/05/31 16:20 36m retest repro upstream report log
2026/04/17 06:22 22m eadavis@qq.com patch upstream OK log
2026/04/17 06:05 24m eadavis@qq.com patch upstream OK log
2026/04/17 05:04 20m eadavis@qq.com patch upstream OK log
2026/04/17 04:52 19m eadavis@qq.com patch upstream OK log
2026/04/17 03:11 17m eadavis@qq.com patch upstream report log

Sample crash report:
BUG: memory leak
unreferenced object 0xffff888113f496c0 (size 96):
  comm "syz.0.17", pid 5921, jiffies 4294948239
  hex dump (first 32 bytes):
    00 60 e1 1b 81 88 ff ff 00 00 00 00 00 00 00 00  .`..............
    00 00 00 00 00 00 00 00 03 00 01 00 00 00 00 00  ................
  backtrace (crc 3f904499):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4696 [inline]
    slab_alloc_node mm/slub.c:4996 [inline]
    __do_kmalloc_node mm/slub.c:5413 [inline]
    __kmalloc_noprof+0x3fb/0x540 mm/slub.c:5439
    _kmalloc_noprof include/linux/slab.h:995 [inline]
    _kzalloc_noprof include/linux/slab.h:1312 [inline]
    __hfs_bnode_create+0x57/0x310 fs/hfsplus/bnode.c:476
    hfsplus_bnode_find+0x13d/0x670 fs/hfsplus/bnode.c:554
    hfsplus_btree_open+0x30b/0x5d0 fs/hfsplus/btree.c:384
    hfsplus_fill_super+0x272/0x880 fs/hfsplus/super.c:546
    get_tree_bdev_flags+0x1c0/0x290 fs/super.c:1887
    vfs_get_tree+0x30/0x120 fs/super.c:1947
    fc_mount fs/namespace.c:1198 [inline]
    do_new_mount_fc fs/namespace.c:3772 [inline]
    do_new_mount fs/namespace.c:3848 [inline]
    path_mount+0x5a9/0x13e0 fs/namespace.c:4168
    do_mount fs/namespace.c:4181 [inline]
    __do_sys_mount fs/namespace.c:4397 [inline]
    __se_sys_mount fs/namespace.c:4374 [inline]
    __x64_sys_mount+0x1a3/0x1e0 fs/namespace.c:4374
    do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
    do_syscall_64+0xe9/0x530 arch/x86/entry/syscall_64.c:84
    entry_SYSCALL_64_after_hwframe+0x77/0x7f

BUG: memory leak
unreferenced object 0xffff888113f21420 (size 96):
  comm "syz.0.18", pid 5924, jiffies 4294948242
  hex dump (first 32 bytes):
    00 60 e1 1b 81 88 ff ff 00 00 00 00 00 00 00 00  .`..............
    00 00 00 00 00 00 00 00 03 00 01 00 00 00 00 00  ................
  backtrace (crc e6e3fad3):
    kmemleak_alloc_recursive include/linux/kmemleak.h:44 [inline]
    slab_post_alloc_hook mm/slub.c:4696 [inline]
    slab_alloc_node mm/slub.c:4996 [inline]
    __do_kmalloc_node mm/slub.c:5413 [inline]
    __kmalloc_noprof+0x3fb/0x540 mm/slub.c:5439
    _kmalloc_noprof include/linux/slab.h:995 [inline]
    _kzalloc_noprof include/linux/slab.h:1312 [inline]
    __hfs_bnode_create+0x57/0x310 fs/hfsplus/bnode.c:476
    hfsplus_bnode_find+0x13d/0x670 fs/hfsplus/bnode.c:554
    hfsplus_btree_open+0x30b/0x5d0 fs/hfsplus/btree.c:384
    hfsplus_fill_super+0x272/0x880 fs/hfsplus/super.c:546
    get_tree_bdev_flags+0x1c0/0x290 fs/super.c:1887
    vfs_get_tree+0x30/0x120 fs/super.c:1947
    fc_mount fs/namespace.c:1198 [inline]
    do_new_mount_fc fs/namespace.c:3772 [inline]
    do_new_mount fs/namespace.c:3848 [inline]
    path_mount+0x5a9/0x13e0 fs/namespace.c:4168
    do_mount fs/namespace.c:4181 [inline]
    __do_sys_mount fs/namespace.c:4397 [inline]
    __se_sys_mount fs/namespace.c:4374 [inline]
    __x64_sys_mount+0x1a3/0x1e0 fs/namespace.c:4374
    do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
    do_syscall_64+0xe9/0x530 arch/x86/entry/syscall_64.c:84
    entry_SYSCALL_64_after_hwframe+0x77/0x7f

connection error: failed to recv *flatrpc.ExecutorMessageRawT: EOF

Crashes (13):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/09/02 23:42 upstream 89a312991dc6 85995287 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-leak memory leak in __hfs_bnode_create
2026/07/23 14:13 upstream 4539944e5151 71a13572 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-leak memory leak in __hfs_bnode_create
2026/06/05 20:04 upstream ddd664bbff63 48b6c3fa .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-leak memory leak in __hfs_bnode_create
2026/06/04 18:55 upstream ba3e43a9e601 197909be .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-leak memory leak in __hfs_bnode_create
2026/05/06 09:26 upstream 9207d47f966b 26da2c66 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-leak memory leak in __hfs_bnode_create
2026/04/25 09:38 upstream 27d128c1cff6 9c2d0995 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-leak memory leak in __hfs_bnode_create
2026/04/15 09:31 upstream 508fed679541 e2e976a8 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-leak memory leak in __hfs_bnode_create
2026/08/26 00:04 upstream 73ae59e97596 614e416a .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-leak memory leak in __hfs_bnode_create
2026/08/09 04:37 upstream a59f57e2aa12 5d63f80b .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-leak memory leak in __hfs_bnode_create
2026/08/09 01:47 upstream a59f57e2aa12 5d63f80b .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-leak memory leak in __hfs_bnode_create
2026/05/17 13:39 upstream 6916d5703ddf de5aae85 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-leak memory leak in __hfs_bnode_create
2026/05/10 11:25 upstream 1bfaee9d3351 29233ece .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-leak memory leak in __hfs_bnode_create
2026/05/08 12:05 upstream 917719c412c4 5633175a .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-gce-leak memory leak in __hfs_bnode_create
* Struck through repros no longer work on HEAD.