[v6.1] KASAN: slab-out-of-bounds Read in dtSearch (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: e4d90d63d385 Linux 6.1.119
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13482b30580000
kernel config: https://syzkaller.appspot.com/x/.config?x=393f8074c5fb7ad6
dashboard link: https://syzkaller.appspot.com/bug?extid=988e368d0eba629196ed
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3986cbf4f35a/disk-e4d90d63.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d2963d16cebb/vmlinux-e4d90d63.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a877a1a23701/Image-e4d90d63.gz.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+988e36...@syzkaller.appspotmail.com

==================================================================
BUG: KASAN: slab-out-of-bounds in dtCompare fs/jfs/jfs_dtree.c:3317 [inline]
BUG: KASAN: slab-out-of-bounds in dtSearch+0x131c/0x1f34 fs/jfs/jfs_dtree.c:649
Read of size 1 at addr ffff0000f4638118 by task syz.0.522/8084

CPU: 1 PID: 8084 Comm: syz.0.522 Not tainted 6.1.119-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call trace:
dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:284 [inline]
print_report+0x174/0x4c0 mm/kasan/report.c:395
kasan_report+0xd4/0x130 mm/kasan/report.c:495
__asan_report_load1_noabort+0x2c/0x38 mm/kasan/report_generic.c:348
dtCompare fs/jfs/jfs_dtree.c:3317 [inline]
dtSearch+0x131c/0x1f34 fs/jfs/jfs_dtree.c:649
jfs_lookup+0x164/0x39c fs/jfs/namei.c:1459
lookup_one_qstr_excl+0x108/0x230 fs/namei.c:1605
do_renameat2+0x5b8/0xe64 fs/namei.c:4977
__do_sys_renameat2 fs/namei.c:5060 [inline]
__se_sys_renameat2 fs/namei.c:5057 [inline]
__arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5057
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

The buggy address belongs to the object at ffff0000f4638118
which belongs to the cache f2fs_free_nid of size 24
The buggy address is located 0 bytes inside of
24-byte region [ffff0000f4638118, ffff0000f4638130)

The buggy address belongs to the physical page:
page:000000009b568a76 refcount:1 mapcount:0 mapping:0000000000000000 index:0xffff0000f46380a0 pfn:0x134638
flags: 0x5ffc00000000200(slab|node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000200 0000000000000000 dead000000000122 ffff0000c740bc80
raw: ffff0000f46380a0 0000000080660061 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff0000f4638000: fb fb fb fc fc fb fb fb fc fc fb fb fb fc fc fb
ffff0000f4638080: fb fb fc fc fb fb fb fc fc fc fc fc fc fc fc fc
>ffff0000f4638100: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
^
ffff0000f4638180: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff0000f4638200: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
==================================================================
ERROR: (device loop0): dtSearch: stack overrun!

ERROR: (device loop0): remounting filesystem as read-only
btstack dump:
bn = 0, index = 0
bn = 0, index = 0
bn = 0, index = 0
bn = 0, index = 0
bn = 0, index = 0
bn = 0, index = 0
bn = 0, index = 0
bn = 0, index = 0
jfs_lookup: dtSearch returned -5


---
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]

syzbot has found a reproducer for the following issue on:

HEAD commit: e4d90d63d385 Linux 6.1.119
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=17442b30580000

kernel config: https://syzkaller.appspot.com/x/.config?x=393f8074c5fb7ad6
dashboard link: https://syzkaller.appspot.com/bug?extid=988e368d0eba629196ed
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17499c0f980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15e394df980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/3986cbf4f35a/disk-e4d90d63.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d2963d16cebb/vmlinux-e4d90d63.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a877a1a23701/Image-e4d90d63.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/9e05ff2e278f/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+988e36...@syzkaller.appspotmail.com

loop0: detected capacity change from 0 to 32768

==================================================================
BUG: KASAN: slab-out-of-bounds in dtCompare fs/jfs/jfs_dtree.c:3317 [inline]
BUG: KASAN: slab-out-of-bounds in dtSearch+0x131c/0x1f34 fs/jfs/jfs_dtree.c:649

Read of size 1 at addr ffff0000df7c4058 by task syz-executor400/4292

CPU: 0 PID: 4292 Comm: syz-executor400 Not tainted 6.1.119-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call trace:
dump_backtrace+0x1c8/0x1f4 arch/arm64/kernel/stacktrace.c:158
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:165
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
print_address_description mm/kasan/report.c:284 [inline]
print_report+0x174/0x4c0 mm/kasan/report.c:395
kasan_report+0xd4/0x130 mm/kasan/report.c:495
__asan_report_load1_noabort+0x2c/0x38 mm/kasan/report_generic.c:348
dtCompare fs/jfs/jfs_dtree.c:3317 [inline]
dtSearch+0x131c/0x1f34 fs/jfs/jfs_dtree.c:649
jfs_lookup+0x164/0x39c fs/jfs/namei.c:1459
lookup_one_qstr_excl+0x108/0x230 fs/namei.c:1605

do_renameat2+0x558/0xe64 fs/namei.c:4968

__do_sys_renameat2 fs/namei.c:5060 [inline]
__se_sys_renameat2 fs/namei.c:5057 [inline]
__arm64_sys_renameat2+0xe0/0xfc fs/namei.c:5057
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

Allocated by task 4292:
kasan_save_stack mm/kasan/common.c:45 [inline]
kasan_set_track+0x4c/0x80 mm/kasan/common.c:52
kasan_save_alloc_info+0x24/0x30 mm/kasan/generic.c:505
__kasan_slab_alloc+0x74/0x8c mm/kasan/common.c:328
kasan_slab_alloc include/linux/kasan.h:201 [inline]
slab_post_alloc_hook+0x74/0x458 mm/slab.h:737
slab_alloc_node mm/slub.c:3398 [inline]
slab_alloc mm/slub.c:3406 [inline]
__kmem_cache_alloc_lru mm/slub.c:3413 [inline]
kmem_cache_alloc_lru+0x1ac/0x2f8 mm/slub.c:3429
alloc_inode_sb include/linux/fs.h:3245 [inline]
jfs_alloc_inode+0x2c/0x68 fs/jfs/super.c:105
alloc_inode fs/inode.c:261 [inline]
new_inode_pseudo+0x68/0x1d0 fs/inode.c:1059
new_inode+0x38/0x174 fs/inode.c:1087
ialloc+0x58/0x7c0 fs/jfs/jfs_inode.c:48
jfs_create+0x190/0xa1c fs/jfs/namei.c:92
lookup_open fs/namei.c:3482 [inline]
open_last_lookups fs/namei.c:3550 [inline]
path_openat+0xeac/0x2548 fs/namei.c:3780
do_filp_open+0x1bc/0x3cc fs/namei.c:3810
do_sys_openat2+0x128/0x3e0 fs/open.c:1318
do_sys_open fs/open.c:1334 [inline]
__do_sys_openat fs/open.c:1350 [inline]
__se_sys_openat fs/open.c:1345 [inline]
__arm64_sys_openat+0x1f0/0x240 fs/open.c:1345

__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
el0_svc+0x58/0x168 arch/arm64/kernel/entry-common.c:637
el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585

The buggy address belongs to the object at ffff0000df7c3780
which belongs to the cache jfs_ip of size 2240
The buggy address is located 24 bytes to the right of
2240-byte region [ffff0000df7c3780, ffff0000df7c4040)

The buggy address belongs to the physical page:

page:00000000a2b86219 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x11f7c0
head:00000000a2b86219 order:3 compound_mapcount:0 compound_pincount:0
flags: 0x5ffc00000010200(slab|head|node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000010200 0000000000000000 dead000000000122 ffff0000c6ee5e00
raw: 0000000000000000 00000000800d000d 00000001ffffffff 0000000000000000

page dumped because: kasan: bad access detected

Memory state around the buggy address:

ffff0000df7c3f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff0000df7c3f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff0000df7c4000: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc
^
ffff0000df7c4080: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff0000df7c4100: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc

==================================================================
ERROR: (device loop0): dtSearch: stack overrun!

ERROR: (device loop0): remounting filesystem as read-only
btstack dump:
bn = 0, index = 0
bn = 0, index = 0
bn = 0, index = 0
bn = 0, index = 0
bn = 0, index = 0
bn = 0, index = 0
bn = 0, index = 0
bn = 0, index = 0
jfs_lookup: dtSearch returned -5


---

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.