Hello,
syzbot found the following issue on:
HEAD commit: 3299fb36854f Linux 5.15.108
git tree: linux-5.15.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=11c7eed7c80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=7da5cf0bf5f17e50
dashboard link:
https://syzkaller.appspot.com/bug?extid=f3117ba42f5190608948
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
userspace arch: arm64
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/e9dec7cd5a48/disk-3299fb36.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/e054af719cf1/vmlinux-3299fb36.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/5ae902fb312f/Image-3299fb36.gz.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
[email protected]
REISERFS (device loop5): journal params: device loop5, size 512, journal first block 18, max trans len 256, max batch 225, max commit age 30, max trans age 30
REISERFS (device loop5): checking transaction log (loop5)
REISERFS (device loop5): Using r5 hash to sort names
==================================================================
BUG: KASAN: use-after-free in strlen+0x54/0x70 lib/string.c:566
Read of size 1 at addr ffff00012658706c by task syz-executor.5/25287
CPU: 0 PID: 25287 Comm: syz-executor.5 Not tainted 5.15.108-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/30/2023
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
print_address_description+0x7c/0x3f0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0x174/0x1e4 mm/kasan/report.c:451
__asan_report_load1_noabort+0x44/0x50 mm/kasan/report_generic.c:306
strlen+0x54/0x70 lib/string.c:566
set_de_name_and_namelen fs/reiserfs/namei.c:82 [inline]
linear_search_in_dir_item fs/reiserfs/namei.c:262 [inline]
reiserfs_find_entry+0x86c/0x1624 fs/reiserfs/namei.c:331
reiserfs_lookup+0x184/0x3c4 fs/reiserfs/namei.c:368
__lookup_slow+0x250/0x388 fs/namei.c:1659
lookup_one_len+0x178/0x28c fs/namei.c:2688
reiserfs_lookup_privroot+0x8c/0x204 fs/reiserfs/xattr.c:980
reiserfs_fill_super+0x1494/0x1e8c fs/reiserfs/super.c:2196
mount_bdev+0x26c/0x368 fs/super.c:1378
get_super_block+0x44/0x58 fs/reiserfs/super.c:2608
legacy_get_tree+0xd4/0x16c fs/fs_context.c:610
vfs_get_tree+0x90/0x274 fs/super.c:1508
do_new_mount+0x25c/0x8c8 fs/namespace.c:2994
path_mount+0x590/0x104c fs/namespace.c:3324
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount fs/namespace.c:3522 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3522
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
The buggy address belongs to the page:
page:000000003ede7d46 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x166587
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000000 fffffc0004832908 ffff0001b4816860 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff000126586f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff000126586f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff000126587000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff000126587080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff000126587100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
reiserfs: enabling write barrier flush mode
REISERFS warning: green-16003 errcatch_is_left_mergeable: Invalid item type observed, run fsck ASAP
REISERFS warning: green-16003 errcatch_is_left_mergeable: Invalid item type observed, run fsck ASAP
REISERFS warning: reiserfs-5093 is_leaf: item entry count seems wrong *3.5*[2 1 0(1) DIR], item_len 35, item_location 3937, free_space(entry_count) 2
REISERFS error (device loop5): vs-5150 search_by_key: invalid format found in block 531. Fsck?
REISERFS (device loop5): Remounting filesystem read-only
REISERFS error (device loop5): vs-13050 reiserfs_update_sd_size: i/o failure occurred trying to update [2 1 0x0 SD] stat data
REISERFS warning: reiserfs-5093 is_leaf: item entry count seems wrong *3.5*[2 1 0(1) DIR], item_len 35, item_location 3937, free_space(entry_count) 2
REISERFS error (device loop5): vs-5150 search_by_key: invalid format found in block 531. Fsck?
REISERFS error (device loop5): zam-7001 reiserfs_find_entry: io error
REISERFS warning: reiserfs-5093 is_leaf: item entry count seems wrong *3.5*[2 1 0(1) DIR], item_len 35, item_location 3937, free_space(entry_count) 2
REISERFS error (device loop5): vs-5150 search_by_key: invalid format found in block 531. Fsck?
REISERFS error (device loop5): vs-13050 reiserfs_update_sd_size: i/o failure occurred trying to update [2 1 0x0 SD] stat data
REISERFS warning (device loop5): jdm-20006 create_privroot: xattrs/ACLs enabled and couldn't find/create .reiserfs_priv. Failing mount.
REISERFS warning: reiserfs-5093 is_leaf: item entry count seems wrong *3.5*[2 1 0(1) DIR], item_len 35, item_location 3937, free_space(entry_count) 2
REISERFS error (device loop5): vs-5150 search_by_key: invalid format found in block 531. Fsck?
REISERFS error (device loop5): zam-7001 reiserfs_find_entry: io error
---
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
[email protected].
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.