[v6.6] KASAN: slab-out-of-bounds Read in dtInsertEntry
1 view
Skip to first unread message
syzbot
Jul 5, 2025, 11:47:28 AM7/5/25
to syzkaller...@googlegroups.com
Hello,
syzbot found the following issue on:
HEAD commit: 3f5b4c104b7d Linux 6.6.95
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=110d2c8c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=747dbf84b0ecd30c
dashboard link: https://syzkaller.appspot.com/bug?extid=8573e4c1627aa4c9aa59
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/421f6e2d0cd1/disk-3f5b4c10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90250695b20b/vmlinux-3f5b4c10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/32250e77bce9/bzImage-3f5b4c10.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8573e4...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: slab-out-of-bounds in dtInsertEntry+0xe8b/0x13e0 fs/jfs/jfs_dtree.c:3753
Read of size 4 at addr ffff88805d58404c by task syz.0.107/6327
CPU: 1 PID: 6327 Comm: syz.0.107 Not tainted 6.6.95-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:364 [inline]
print_report+0xac/0x230 mm/kasan/report.c:475
kasan_report+0x117/0x150 mm/kasan/report.c:588
dtInsertEntry+0xe8b/0x13e0 fs/jfs/jfs_dtree.c:3753
dtSplitPage+0x2a66/0x3b10 fs/jfs/jfs_dtree.c:1596
dtSplitUp fs/jfs/jfs_dtree.c:1092 [inline]
dtInsert+0x108f/0x5f40 fs/jfs/jfs_dtree.c:871
jfs_symlink+0x719/0xe50 fs/jfs/namei.c:1019
vfs_symlink+0x138/0x2b0 fs/namei.c:4473
do_symlinkat+0x1b2/0x3f0 fs/namei.c:4499
__do_sys_symlink fs/namei.c:4520 [inline]
__se_sys_symlink fs/namei.c:4518 [inline]
__x64_sys_symlink+0x7e/0x90 fs/namei.c:4518
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f09aa18e929
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f09ab000038 EFLAGS: 00000246 ORIG_RAX: 0000000000000058
RAX: ffffffffffffffda RBX: 00007f09aa3b5fa0 RCX: 00007f09aa18e929
RDX: 0000000000000000 RSI: 0000200000000040 RDI: 0000200000000080
RBP: 00007f09aa210b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f09aa3b5fa0 R15: 00007ffe4a657448
</TASK>
Allocated by task 6327:
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4e/0x70 mm/kasan/common.c:52
__kasan_slab_alloc+0x6c/0x80 mm/kasan/common.c:328
kasan_slab_alloc include/linux/kasan.h:188 [inline]
slab_post_alloc_hook+0x6e/0x4d0 mm/slab.h:767
slab_alloc_node mm/slub.c:3485 [inline]
slab_alloc mm/slub.c:3493 [inline]
__kmem_cache_alloc_lru mm/slub.c:3500 [inline]
kmem_cache_alloc_lru+0x115/0x2e0 mm/slub.c:3516
alloc_inode_sb include/linux/fs.h:2946 [inline]
jfs_alloc_inode+0x28/0x60 fs/jfs/super.c:105
alloc_inode fs/inode.c:261 [inline]
iget_locked+0x1ad/0x840 fs/inode.c:1359
jfs_iget+0x24/0x3c0 fs/jfs/inode.c:29
jfs_lookup+0x1c6/0x380 fs/jfs/namei.c:1467
__lookup_slow+0x281/0x3b0 fs/namei.c:1694
lookup_slow+0x53/0x70 fs/namei.c:1711
walk_component+0x2be/0x3f0 fs/namei.c:2002
lookup_last fs/namei.c:2459 [inline]
path_lookupat+0x169/0x440 fs/namei.c:2483
filename_lookup+0x1f4/0x510 fs/namei.c:2512
user_path_at_empty+0x42/0x60 fs/namei.c:2909
user_path_at include/linux/namei.h:57 [inline]
__do_sys_chdir fs/open.c:551 [inline]
__se_sys_chdir+0x95/0x290 fs/open.c:545
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
The buggy address belongs to the object at ffff88805d583780
which belongs to the cache jfs_ip of size 2240
The buggy address is located 12 bytes to the right of
allocated 2240-byte region [ffff88805d583780, ffff88805d584040)
The buggy address belongs to the physical page:
page:ffffea0001756000 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x5d580
head:ffffea0001756000 order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0
memcg:ffff88807d771c01
flags: 0xfff00000000840(slab|head|node=0|zone=1|lastcpupid=0x7ff)
page_type: 0xffffffff()
raw: 00fff00000000840 ffff888142af3b40 dead000000000122 0000000000000000
raw: 0000000000000000 00000000800d000d 00000001ffffffff ffff88807d771c01
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 3, migratetype Reclaimable, gfp_mask 0x1d2050(__GFP_IO|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC|__GFP_HARDWALL|__GFP_RECLAIMABLE), pid 6327, tgid 6326 (syz.0.107), ts 120661407800, free_ts 26514902233
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x1cd/0x210 mm/page_alloc.c:1554
prep_new_page mm/page_alloc.c:1561 [inline]
get_page_from_freelist+0x195c/0x19f0 mm/page_alloc.c:3191
__alloc_pages+0x1e3/0x460 mm/page_alloc.c:4457
alloc_slab_page+0x5d/0x170 mm/slub.c:1876
allocate_slab mm/slub.c:2023 [inline]
new_slab+0x87/0x2e0 mm/slub.c:2076
___slab_alloc+0xc6d/0x12f0 mm/slub.c:3230
__slab_alloc mm/slub.c:3329 [inline]
__slab_alloc_node mm/slub.c:3382 [inline]
slab_alloc_node mm/slub.c:3475 [inline]
slab_alloc mm/slub.c:3493 [inline]
__kmem_cache_alloc_lru mm/slub.c:3500 [inline]
kmem_cache_alloc_lru+0x1ae/0x2e0 mm/slub.c:3516
alloc_inode_sb include/linux/fs.h:2946 [inline]
jfs_alloc_inode+0x28/0x60 fs/jfs/super.c:105
alloc_inode fs/inode.c:261 [inline]
new_inode_pseudo+0x63/0x1d0 fs/inode.c:1049
new_inode+0x22/0x1b0 fs/inode.c:1075
jfs_fill_super+0x396/0xac0 fs/jfs/super.c:544
mount_bdev+0x22b/0x2d0 fs/super.c:1643
legacy_get_tree+0xea/0x180 fs/fs_context.c:662
vfs_get_tree+0x8c/0x280 fs/super.c:1764
do_new_mount+0x24b/0xa40 fs/namespace.c:3366
do_mount fs/namespace.c:3706 [inline]
__do_sys_mount fs/namespace.c:3915 [inline]
__se_sys_mount+0x2da/0x3c0 fs/namespace.c:3892
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1154 [inline]
free_unref_page_prepare+0x7ce/0x8e0 mm/page_alloc.c:2336
free_unref_page+0x32/0x2e0 mm/page_alloc.c:2429
free_contig_range+0xa1/0x160 mm/page_alloc.c:6369
destroy_args+0x87/0x770 mm/debug_vm_pgtable.c:1015
debug_vm_pgtable+0x3cc/0x410 mm/debug_vm_pgtable.c:1395
do_one_initcall+0x1fd/0x750 init/main.c:1238
do_initcall_level+0x137/0x1f0 init/main.c:1300
do_initcalls+0x69/0xd0 init/main.c:1316
kernel_init_freeable+0x3d2/0x570 init/main.c:1553
kernel_init+0x1d/0x1c0 init/main.c:1443
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
Memory state around the buggy address:
ffff88805d583f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff88805d583f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff88805d584000: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc
^
ffff88805d584080: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff88805d584100: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================
---
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
syzbot found the following issue on:
HEAD commit: 3f5b4c104b7d Linux 6.6.95
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=110d2c8c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=747dbf84b0ecd30c
dashboard link: https://syzkaller.appspot.com/bug?extid=8573e4c1627aa4c9aa59
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/421f6e2d0cd1/disk-3f5b4c10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90250695b20b/vmlinux-3f5b4c10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/32250e77bce9/bzImage-3f5b4c10.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8573e4...@syzkaller.appspotmail.com
==================================================================
BUG: KASAN: slab-out-of-bounds in dtInsertEntry+0xe8b/0x13e0 fs/jfs/jfs_dtree.c:3753
Read of size 4 at addr ffff88805d58404c by task syz.0.107/6327
CPU: 1 PID: 6327 Comm: syz.0.107 Not tainted 6.6.95-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:364 [inline]
print_report+0xac/0x230 mm/kasan/report.c:475
kasan_report+0x117/0x150 mm/kasan/report.c:588
dtInsertEntry+0xe8b/0x13e0 fs/jfs/jfs_dtree.c:3753
dtSplitPage+0x2a66/0x3b10 fs/jfs/jfs_dtree.c:1596
dtSplitUp fs/jfs/jfs_dtree.c:1092 [inline]
dtInsert+0x108f/0x5f40 fs/jfs/jfs_dtree.c:871
jfs_symlink+0x719/0xe50 fs/jfs/namei.c:1019
vfs_symlink+0x138/0x2b0 fs/namei.c:4473
do_symlinkat+0x1b2/0x3f0 fs/namei.c:4499
__do_sys_symlink fs/namei.c:4520 [inline]
__se_sys_symlink fs/namei.c:4518 [inline]
__x64_sys_symlink+0x7e/0x90 fs/namei.c:4518
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f09aa18e929
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f09ab000038 EFLAGS: 00000246 ORIG_RAX: 0000000000000058
RAX: ffffffffffffffda RBX: 00007f09aa3b5fa0 RCX: 00007f09aa18e929
RDX: 0000000000000000 RSI: 0000200000000040 RDI: 0000200000000080
RBP: 00007f09aa210b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f09aa3b5fa0 R15: 00007ffe4a657448
</TASK>
Allocated by task 6327:
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4e/0x70 mm/kasan/common.c:52
__kasan_slab_alloc+0x6c/0x80 mm/kasan/common.c:328
kasan_slab_alloc include/linux/kasan.h:188 [inline]
slab_post_alloc_hook+0x6e/0x4d0 mm/slab.h:767
slab_alloc_node mm/slub.c:3485 [inline]
slab_alloc mm/slub.c:3493 [inline]
__kmem_cache_alloc_lru mm/slub.c:3500 [inline]
kmem_cache_alloc_lru+0x115/0x2e0 mm/slub.c:3516
alloc_inode_sb include/linux/fs.h:2946 [inline]
jfs_alloc_inode+0x28/0x60 fs/jfs/super.c:105
alloc_inode fs/inode.c:261 [inline]
iget_locked+0x1ad/0x840 fs/inode.c:1359
jfs_iget+0x24/0x3c0 fs/jfs/inode.c:29
jfs_lookup+0x1c6/0x380 fs/jfs/namei.c:1467
__lookup_slow+0x281/0x3b0 fs/namei.c:1694
lookup_slow+0x53/0x70 fs/namei.c:1711
walk_component+0x2be/0x3f0 fs/namei.c:2002
lookup_last fs/namei.c:2459 [inline]
path_lookupat+0x169/0x440 fs/namei.c:2483
filename_lookup+0x1f4/0x510 fs/namei.c:2512
user_path_at_empty+0x42/0x60 fs/namei.c:2909
user_path_at include/linux/namei.h:57 [inline]
__do_sys_chdir fs/open.c:551 [inline]
__se_sys_chdir+0x95/0x290 fs/open.c:545
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
The buggy address belongs to the object at ffff88805d583780
which belongs to the cache jfs_ip of size 2240
The buggy address is located 12 bytes to the right of
allocated 2240-byte region [ffff88805d583780, ffff88805d584040)
The buggy address belongs to the physical page:
page:ffffea0001756000 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x5d580
head:ffffea0001756000 order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0
memcg:ffff88807d771c01
flags: 0xfff00000000840(slab|head|node=0|zone=1|lastcpupid=0x7ff)
page_type: 0xffffffff()
raw: 00fff00000000840 ffff888142af3b40 dead000000000122 0000000000000000
raw: 0000000000000000 00000000800d000d 00000001ffffffff ffff88807d771c01
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 3, migratetype Reclaimable, gfp_mask 0x1d2050(__GFP_IO|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC|__GFP_HARDWALL|__GFP_RECLAIMABLE), pid 6327, tgid 6326 (syz.0.107), ts 120661407800, free_ts 26514902233
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x1cd/0x210 mm/page_alloc.c:1554
prep_new_page mm/page_alloc.c:1561 [inline]
get_page_from_freelist+0x195c/0x19f0 mm/page_alloc.c:3191
__alloc_pages+0x1e3/0x460 mm/page_alloc.c:4457
alloc_slab_page+0x5d/0x170 mm/slub.c:1876
allocate_slab mm/slub.c:2023 [inline]
new_slab+0x87/0x2e0 mm/slub.c:2076
___slab_alloc+0xc6d/0x12f0 mm/slub.c:3230
__slab_alloc mm/slub.c:3329 [inline]
__slab_alloc_node mm/slub.c:3382 [inline]
slab_alloc_node mm/slub.c:3475 [inline]
slab_alloc mm/slub.c:3493 [inline]
__kmem_cache_alloc_lru mm/slub.c:3500 [inline]
kmem_cache_alloc_lru+0x1ae/0x2e0 mm/slub.c:3516
alloc_inode_sb include/linux/fs.h:2946 [inline]
jfs_alloc_inode+0x28/0x60 fs/jfs/super.c:105
alloc_inode fs/inode.c:261 [inline]
new_inode_pseudo+0x63/0x1d0 fs/inode.c:1049
new_inode+0x22/0x1b0 fs/inode.c:1075
jfs_fill_super+0x396/0xac0 fs/jfs/super.c:544
mount_bdev+0x22b/0x2d0 fs/super.c:1643
legacy_get_tree+0xea/0x180 fs/fs_context.c:662
vfs_get_tree+0x8c/0x280 fs/super.c:1764
do_new_mount+0x24b/0xa40 fs/namespace.c:3366
do_mount fs/namespace.c:3706 [inline]
__do_sys_mount fs/namespace.c:3915 [inline]
__se_sys_mount+0x2da/0x3c0 fs/namespace.c:3892
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1154 [inline]
free_unref_page_prepare+0x7ce/0x8e0 mm/page_alloc.c:2336
free_unref_page+0x32/0x2e0 mm/page_alloc.c:2429
free_contig_range+0xa1/0x160 mm/page_alloc.c:6369
destroy_args+0x87/0x770 mm/debug_vm_pgtable.c:1015
debug_vm_pgtable+0x3cc/0x410 mm/debug_vm_pgtable.c:1395
do_one_initcall+0x1fd/0x750 init/main.c:1238
do_initcall_level+0x137/0x1f0 init/main.c:1300
do_initcalls+0x69/0xd0 init/main.c:1316
kernel_init_freeable+0x3d2/0x570 init/main.c:1553
kernel_init+0x1d/0x1c0 init/main.c:1443
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
Memory state around the buggy address:
ffff88805d583f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff88805d583f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff88805d584000: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc
^
ffff88805d584080: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff88805d584100: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================
---
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
syzbot
Jul 5, 2025, 7:28:33 PM7/5/25
to syzkaller...@googlegroups.com
syzbot has found a reproducer for the following issue on:
HEAD commit: 3f5b4c104b7d Linux 6.6.95
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13e10bd4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1184fc8c580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/421f6e2d0cd1/disk-3f5b4c10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90250695b20b/vmlinux-3f5b4c10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/32250e77bce9/bzImage-3f5b4c10.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/aa476f3b4750/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=12f19c8c580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8573e4...@syzkaller.appspotmail.com
read_mapping_page failed!
ERROR: (device loop0): txCommit:
read_mapping_page failed!
ERROR: (device loop0): txCommit:
CPU: 0 PID: 5950 Comm: syz.0.16 Not tainted 6.6.95-syzkaller #0
RAX: ffffffffffffffda RBX: 00007f82849b5fa0 RCX: 00007f828478e929
</TASK>
Allocated by task 5950:
The buggy address belongs to the object at ffff888060c12e40
The buggy address belongs to the physical page:
page:ffffea0001830400 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x60c10
head:ffffea0001830400 order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0
memcg:ffff888078d3cb01
raw: 0000000000000000 00000000800d000d 00000001ffffffff ffff888078d3cb01
jfs_mount+0x73/0x860 fs/jfs/jfs_mount.c:87
jfs_fill_super+0x4e2/0xac0 fs/jfs/super.c:556
kcov_put kernel/kcov.c:438 [inline]
kcov_close+0x2b/0x50 kernel/kcov.c:534
__fput+0x234/0x970 fs/file_table.c:384
task_work_run+0x1ce/0x250 kernel/task_work.c:239
exit_task_work include/linux/task_work.h:43 [inline]
do_exit+0x90b/0x23c0 kernel/exit.c:883
do_group_exit+0x21b/0x2d0 kernel/exit.c:1024
get_signal+0x12fc/0x1400 kernel/signal.c:2902
arch_do_signal_or_restart+0x96/0x780 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
Memory state around the buggy address:
ffff888060c13600: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff888060c13680: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888060c13700: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
^
ffff888060c13780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff888060c13800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
HEAD commit: 3f5b4c104b7d Linux 6.6.95
git tree: linux-6.6.y
kernel config: https://syzkaller.appspot.com/x/.config?x=747dbf84b0ecd30c
dashboard link: https://syzkaller.appspot.com/bug?extid=8573e4c1627aa4c9aa59
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=116ca582580000
dashboard link: https://syzkaller.appspot.com/bug?extid=8573e4c1627aa4c9aa59
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1184fc8c580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/421f6e2d0cd1/disk-3f5b4c10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/90250695b20b/vmlinux-3f5b4c10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/32250e77bce9/bzImage-3f5b4c10.xz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=12f19c8c580000)
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8573e4...@syzkaller.appspotmail.com
ERROR: (device loop0): txCommit:
read_mapping_page failed!
ERROR: (device loop0): txCommit:
==================================================================
BUG: KASAN: slab-out-of-bounds in dtInsertEntry+0xe8b/0x13e0 fs/jfs/jfs_dtree.c:3753
Read of size 4 at addr ffff888060c1370c by task syz.0.16/5950
BUG: KASAN: slab-out-of-bounds in dtInsertEntry+0xe8b/0x13e0 fs/jfs/jfs_dtree.c:3753
CPU: 0 PID: 5950 Comm: syz.0.16 Not tainted 6.6.95-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:364 [inline]
print_report+0xac/0x230 mm/kasan/report.c:475
kasan_report+0x117/0x150 mm/kasan/report.c:588
dtInsertEntry+0xe8b/0x13e0 fs/jfs/jfs_dtree.c:3753
dtSplitPage+0x2a66/0x3b10 fs/jfs/jfs_dtree.c:1596
dtSplitUp fs/jfs/jfs_dtree.c:1092 [inline]
dtInsert+0x108f/0x5f40 fs/jfs/jfs_dtree.c:871
jfs_symlink+0x719/0xe50 fs/jfs/namei.c:1019
vfs_symlink+0x138/0x2b0 fs/namei.c:4473
do_symlinkat+0x1b2/0x3f0 fs/namei.c:4499
__do_sys_symlink fs/namei.c:4520 [inline]
__se_sys_symlink fs/namei.c:4518 [inline]
__x64_sys_symlink+0x7e/0x90 fs/namei.c:4518
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7f828478e929
Call Trace:
<TASK>
dump_stack_lvl+0x16c/0x230 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:364 [inline]
print_report+0xac/0x230 mm/kasan/report.c:475
kasan_report+0x117/0x150 mm/kasan/report.c:588
dtInsertEntry+0xe8b/0x13e0 fs/jfs/jfs_dtree.c:3753
dtSplitPage+0x2a66/0x3b10 fs/jfs/jfs_dtree.c:1596
dtSplitUp fs/jfs/jfs_dtree.c:1092 [inline]
dtInsert+0x108f/0x5f40 fs/jfs/jfs_dtree.c:871
jfs_symlink+0x719/0xe50 fs/jfs/namei.c:1019
vfs_symlink+0x138/0x2b0 fs/namei.c:4473
do_symlinkat+0x1b2/0x3f0 fs/namei.c:4499
__do_sys_symlink fs/namei.c:4520 [inline]
__se_sys_symlink fs/namei.c:4518 [inline]
__x64_sys_symlink+0x7e/0x90 fs/namei.c:4518
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd84558a48 EFLAGS: 00000246 ORIG_RAX: 0000000000000058
RAX: ffffffffffffffda RBX: 00007f82849b5fa0 RCX: 00007f828478e929
RDX: 0000000000000000 RSI: 0000200000000040 RDI: 0000200000000080
RBP: 00007f8284810b39 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f82849b5fa0 R14: 00007f82849b5fa0 R15: 0000000000000002
</TASK>
Allocated by task 5950:
which belongs to the cache jfs_ip of size 2240
The buggy address is located 12 bytes to the right of
allocated 2240-byte region [ffff888060c12e40, ffff888060c13700)
The buggy address is located 12 bytes to the right of
The buggy address belongs to the physical page:
head:ffffea0001830400 order:3 entire_mapcount:0 nr_pages_mapped:0 pincount:0
memcg:ffff888078d3cb01
flags: 0xfff00000000840(slab|head|node=0|zone=1|lastcpupid=0x7ff)
page_type: 0xffffffff()
raw: 00fff00000000840 ffff888142eb3b40 dead000000000122 0000000000000000
page_type: 0xffffffff()
raw: 0000000000000000 00000000800d000d 00000001ffffffff ffff888078d3cb01
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 3, migratetype Reclaimable, gfp_mask 0x1d2050(__GFP_IO|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP|__GFP_NOMEMALLOC|__GFP_HARDWALL|__GFP_RECLAIMABLE), pid 5950, tgid 5950 (syz.0.16), ts 84736685196, free_ts 74014082038
page_owner tracks the page as allocated
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x1cd/0x210 mm/page_alloc.c:1554
prep_new_page mm/page_alloc.c:1561 [inline]
get_page_from_freelist+0x195c/0x19f0 mm/page_alloc.c:3191
__alloc_pages+0x1e3/0x460 mm/page_alloc.c:4457
alloc_slab_page+0x5d/0x170 mm/slub.c:1876
allocate_slab mm/slub.c:2023 [inline]
new_slab+0x87/0x2e0 mm/slub.c:2076
___slab_alloc+0xc6d/0x12f0 mm/slub.c:3230
__slab_alloc mm/slub.c:3329 [inline]
__slab_alloc_node mm/slub.c:3382 [inline]
slab_alloc_node mm/slub.c:3475 [inline]
slab_alloc mm/slub.c:3493 [inline]
__kmem_cache_alloc_lru mm/slub.c:3500 [inline]
kmem_cache_alloc_lru+0x1ae/0x2e0 mm/slub.c:3516
alloc_inode_sb include/linux/fs.h:2946 [inline]
jfs_alloc_inode+0x28/0x60 fs/jfs/super.c:105
alloc_inode fs/inode.c:261 [inline]
new_inode_pseudo+0x63/0x1d0 fs/inode.c:1049
new_inode+0x22/0x1b0 fs/inode.c:1075
diReadSpecial+0x52/0x6f0 fs/jfs/jfs_imap.c:426
post_alloc_hook+0x1cd/0x210 mm/page_alloc.c:1554
prep_new_page mm/page_alloc.c:1561 [inline]
get_page_from_freelist+0x195c/0x19f0 mm/page_alloc.c:3191
__alloc_pages+0x1e3/0x460 mm/page_alloc.c:4457
alloc_slab_page+0x5d/0x170 mm/slub.c:1876
allocate_slab mm/slub.c:2023 [inline]
new_slab+0x87/0x2e0 mm/slub.c:2076
___slab_alloc+0xc6d/0x12f0 mm/slub.c:3230
__slab_alloc mm/slub.c:3329 [inline]
__slab_alloc_node mm/slub.c:3382 [inline]
slab_alloc_node mm/slub.c:3475 [inline]
slab_alloc mm/slub.c:3493 [inline]
__kmem_cache_alloc_lru mm/slub.c:3500 [inline]
kmem_cache_alloc_lru+0x1ae/0x2e0 mm/slub.c:3516
alloc_inode_sb include/linux/fs.h:2946 [inline]
jfs_alloc_inode+0x28/0x60 fs/jfs/super.c:105
alloc_inode fs/inode.c:261 [inline]
new_inode_pseudo+0x63/0x1d0 fs/inode.c:1049
new_inode+0x22/0x1b0 fs/inode.c:1075
jfs_mount+0x73/0x860 fs/jfs/jfs_mount.c:87
jfs_fill_super+0x4e2/0xac0 fs/jfs/super.c:556
mount_bdev+0x22b/0x2d0 fs/super.c:1643
legacy_get_tree+0xea/0x180 fs/fs_context.c:662
vfs_get_tree+0x8c/0x280 fs/super.c:1764
legacy_get_tree+0xea/0x180 fs/fs_context.c:662
vfs_get_tree+0x8c/0x280 fs/super.c:1764
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1154 [inline]
free_unref_page_prepare+0x7ce/0x8e0 mm/page_alloc.c:2336
free_unref_page+0x32/0x2e0 mm/page_alloc.c:2429
vfree+0x1a6/0x320 mm/vmalloc.c:2860
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1154 [inline]
free_unref_page_prepare+0x7ce/0x8e0 mm/page_alloc.c:2336
free_unref_page+0x32/0x2e0 mm/page_alloc.c:2429
kcov_put kernel/kcov.c:438 [inline]
kcov_close+0x2b/0x50 kernel/kcov.c:534
__fput+0x234/0x970 fs/file_table.c:384
task_work_run+0x1ce/0x250 kernel/task_work.c:239
exit_task_work include/linux/task_work.h:43 [inline]
do_exit+0x90b/0x23c0 kernel/exit.c:883
do_group_exit+0x21b/0x2d0 kernel/exit.c:1024
get_signal+0x12fc/0x1400 kernel/signal.c:2902
arch_do_signal_or_restart+0x96/0x780 arch/x86/kernel/signal.c:310
exit_to_user_mode_loop+0x70/0x110 kernel/entry/common.c:174
exit_to_user_mode_prepare+0xb1/0x140 kernel/entry/common.c:210
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x1a/0x50 kernel/entry/common.c:302
do_syscall_64+0x61/0xb0 arch/x86/entry/common.c:87
entry_SYSCALL_64_after_hwframe+0x68/0xd2
Memory state around the buggy address:
ffff888060c13680: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888060c13700: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
^
ffff888060c13780: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff888060c13800: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
==================================================================
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
Reply all
Reply to author
Forward
0 new messages