JBD2: Ignoring recovery information on journal ocfs2: Mounting device (7,0) on (node local, slot 0) with ordered data mode. ================================================================== BUG: KASAN: use-after-free in ocfs2_xattr_get_type fs/ocfs2/ocfs2_fs.h:1114 [inline] BUG: KASAN: use-after-free in ocfs2_xattr_list_entries fs/ocfs2/xattr.c:934 [inline] BUG: KASAN: use-after-free in ocfs2_xattr_ibody_list fs/ocfs2/xattr.c:982 [inline] BUG: KASAN: use-after-free in ocfs2_listxattr+0x408/0xa74 fs/ocfs2/xattr.c:1044 Read of size 1 at addr ffff0000eec20007 by task syz.0.20/6784 CPU: 0 UID: 0 PID: 6784 Comm: syz.0.20 Not tainted syzkaller #0 PREEMPT Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/03/2025 Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C) __dump_stack+0x30/0x40 lib/dump_stack.c:94 dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120 print_address_description+0x8c/0x21c mm/kasan/report.c:378 print_report+0x50/0x68 mm/kasan/report.c:482 kasan_report+0xb0/0x110 mm/kasan/report.c:595 __asan_report_load1_noabort+0x20/0x2c mm/kasan/report_generic.c:378 ocfs2_xattr_get_type fs/ocfs2/ocfs2_fs.h:1114 [inline] ocfs2_xattr_list_entries fs/ocfs2/xattr.c:934 [inline] ocfs2_xattr_ibody_list fs/ocfs2/xattr.c:982 [inline] ocfs2_listxattr+0x408/0xa74 fs/ocfs2/xattr.c:1044 vfs_listxattr fs/xattr.c:493 [inline] listxattr+0x10c/0x380 fs/xattr.c:924 filename_listxattr fs/xattr.c:958 [inline] path_listxattrat+0x15c/0x33c fs/xattr.c:988 __do_sys_listxattr fs/xattr.c:1001 [inline] __se_sys_listxattr fs/xattr.c:998 [inline] __arm64_sys_listxattr+0x84/0x98 fs/xattr.c:998 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x98/0x254 arch/arm64/kernel/syscall.c:49 el0_svc_common+0xe8/0x23c arch/arm64/kernel/syscall.c:132 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:151 el0_svc+0x5c/0x26c arch/arm64/kernel/entry-common.c:724 el0t_64_sync_handler+0x84/0x12c arch/arm64/kernel/entry-common.c:743 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596 The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xafa pfn:0x12ec20 flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff) raw: 05ffc00000000000 fffffdffc3a6ffc8 fffffdffc3bb0848 0000000000000000 raw: 0000000000000afa 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff0000eec1ff00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff0000eec1ff80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff0000eec20000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff0000eec20080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff0000eec20100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ==================================================================