REISERFS warning (device loop6): vs-13060 reiserfs_update_sd_size: stat data of object [3 7 0x0 SD] (nlink == 2) not found (pos 6)
REISERFS warning (device loop6): vs-13060 reiserfs_update_sd_size: stat data of object [3 7 0x0 SD] (nlink == 3) not found (pos 4)
==================================================================
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+0x45c/0xe88 fs/reiserfs/namei.c:165
Read of size 4 at addr ffff0000e0f8af24 by task syz.6.195/5665

CPU: 1 PID: 5665 Comm: syz.6.195 Not tainted 6.1.123-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:316 [inline]
 print_report+0x174/0x4c0 mm/kasan/report.c:427
 kasan_report+0xd4/0x130 mm/kasan/report.c:531
 __asan_report_load_n_noabort+0x28/0x34 mm/kasan/report_generic.c:361
 bin_search_in_dir_item fs/reiserfs/namei.c:40 [inline]
 search_by_entry_key+0x45c/0xe88 fs/reiserfs/namei.c:165
 reiserfs_find_entry+0x288/0x149c fs/reiserfs/namei.c:322
 reiserfs_lookup+0x184/0x3c4 fs/reiserfs/namei.c:368
 __lookup_slow+0x250/0x374 fs/namei.c:1690
 lookup_one_len+0x178/0x28c fs/namei.c:2740
 open_xa_dir+0x35c/0x578 fs/reiserfs/xattr.c:162
 xattr_lookup+0x3c/0x268 fs/reiserfs/xattr.c:395
 reiserfs_xattr_get+0xf0/0x96c fs/reiserfs/xattr.c:677
 security_get+0x94/0xd0 fs/reiserfs/xattr_security.c:19
 __vfs_getxattr+0x34c/0x368 fs/xattr.c:407
 cap_inode_need_killpriv+0x50/0x78 security/commoncap.c:301
 security_inode_need_killpriv+0x6c/0xa4 security/security.c:1436
 dentry_needs_remove_privs fs/inode.c:2054 [inline]
 __file_remove_privs+0x1c4/0x52c fs/inode.c:2085
 file_remove_privs+0x24/0x34 fs/inode.c:2112
 __generic_file_write_iter+0xbc/0x388 mm/filemap.c:3918
 generic_file_write_iter+0xb8/0x2b4 mm/filemap.c:4005
 do_iter_write+0x534/0x964 fs/read_write.c:861
 vfs_writev fs/read_write.c:934 [inline]
 do_pwritev+0x1ec/0x334 fs/read_write.c:1031
 __do_sys_pwritev2 fs/read_write.c:1090 [inline]
 __se_sys_pwritev2 fs/read_write.c:1081 [inline]
 __arm64_sys_pwritev2+0xd4/0x108 fs/read_write.c:1081
 __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 physical page:
page:00000000e2cf9636 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x120f8a
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000000 dead000000000100 dead000000000122 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
 ffff0000e0f8ae00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff0000e0f8ae80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff0000e0f8af00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
                               ^
 ffff0000e0f8af80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
 ffff0000e0f8b000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================