REISERFS (device loop1): using 3.5.x disk format
==================================================================
REISERFS error (device loop2): vs-5150 search_by_key: invalid format found in block 15767. Fsck?
BUG: KASAN: use-after-free in bin_search_in_dir_item fs/reiserfs/namei.c:40 [inline]
BUG: KASAN: use-after-free in search_by_entry_key+0xcda/0xf30 fs/reiserfs/namei.c:164
Read of size 4 at addr ffff888074f59004 by task syz-executor.0/8166

CPU: 1 PID: 8166 Comm: syz-executor.0 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
Call Trace:
REISERFS error (device loop2): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1 2 0x0 SD]
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
 print_address_description.cold+0x54/0x219 mm/kasan/report.c:256
 kasan_report_error.cold+0x8a/0x1b9 mm/kasan/report.c:354
 kasan_report mm/kasan/report.c:412 [inline]
 __asan_report_load_n_noabort+0x8b/0xa0 mm/kasan/report.c:443
 bin_search_in_dir_item fs/reiserfs/namei.c:40 [inline]
 search_by_entry_key+0xcda/0xf30 fs/reiserfs/namei.c:164
 reiserfs_find_entry.part.0+0x142/0x1480 fs/reiserfs/namei.c:321
REISERFS warning (device loop2):  reiserfs_fill_super: corrupt root inode, run fsck
 reiserfs_find_entry fs/reiserfs/namei.c:367 [inline]
 reiserfs_lookup+0x24a/0x490 fs/reiserfs/namei.c:367
 __lookup_slow+0x246/0x4a0 fs/namei.c:1672
 lookup_one_len+0x163/0x190 fs/namei.c:2544
 reiserfs_lookup_privroot+0x92/0x280 fs/reiserfs/xattr.c:970
 reiserfs_fill_super+0x18e8/0x2d80 fs/reiserfs/super.c:2205
 mount_bdev+0x2fc/0x3b0 fs/super.c:1158
 mount_fs+0xa3/0x310 fs/super.c:1261
 vfs_kern_mount.part.0+0x68/0x470 fs/namespace.c:961
 vfs_kern_mount fs/namespace.c:951 [inline]
 do_new_mount fs/namespace.c:2492 [inline]
 do_mount+0x115c/0x2f50 fs/namespace.c:2822
 ksys_mount+0xcf/0x130 fs/namespace.c:3038
 __do_sys_mount fs/namespace.c:3052 [inline]
 __se_sys_mount fs/namespace.c:3049 [inline]
 __x64_sys_mount+0xba/0x150 fs/namespace.c:3049
 do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
 entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7f261b660b2a
Code: 48 c7 c2 b8 ff ff ff f7 d8 64 89 02 b8 ff ff ff ff eb d2 e8 b8 04 00 00 0f 1f 84 00 00 00 00 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f2619fd1f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 0000000020000400 RCX: 00007f261b660b2a
RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007f2619fd1fe0
RBP: 00007f2619fd2020 R08: 00007f2619fd2020 R09: 0000000020000000
R10: 0000000000010001 R11: 0000000000000202 R12: 0000000020000000
R13: 0000000020000100 R14: 00007f2619fd1fe0 R15: 0000000020000040

The buggy address belongs to the page:
page:ffffea0001d3d640 count:0 mapcount:0 mapping:0000000000000000 index:0x1
flags: 0xfff00000000000()
raw: 00fff00000000000 ffffea0001f05348 ffffea0001a2b808 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff888074f58f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 ffff888074f58f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff888074f59000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                   ^
 ffff888074f59080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff888074f59100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================