loop0: detected capacity change from 0 to 4096 ================================================================== BUG: KASAN: use-after-free in ntfs_attr_find+0x5a0/0x9d0 fs/ntfs/attrib.c:609 Read of size 2 at addr ffff0000dc87d442 by task syz-executor383/6095 CPU: 1 PID: 6095 Comm: syz-executor383 Not tainted 6.7.0-rc8-syzkaller-g0802e17d9aca #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 Call trace: dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:291 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:298 __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:364 [inline] print_report+0x174/0x514 mm/kasan/report.c:475 kasan_report+0xd8/0x138 mm/kasan/report.c:588 __asan_report_load_n_noabort+0x1c/0x28 mm/kasan/report_generic.c:391 ntfs_attr_find+0x5a0/0x9d0 fs/ntfs/attrib.c:609 ntfs_attr_lookup+0x3dc/0x1cd8 ntfs_read_locked_inode+0x87c/0x38dc fs/ntfs/inode.c:666 ntfs_iget+0x110/0x19c fs/ntfs/inode.c:177 load_and_init_mft_mirror fs/ntfs/super.c:1035 [inline] load_system_files+0xe4/0x4734 fs/ntfs/super.c:1780 ntfs_fill_super+0x14e0/0x2314 fs/ntfs/super.c:2900 mount_bdev+0x1e8/0x2b4 fs/super.c:1650 ntfs_mount+0x44/0x58 fs/ntfs/super.c:3057 legacy_get_tree+0xd4/0x16c fs/fs_context.c:662 vfs_get_tree+0x90/0x288 fs/super.c:1771 do_new_mount+0x25c/0x8c8 fs/namespace.c:3337 path_mount+0x590/0xe04 fs/namespace.c:3664 do_mount fs/namespace.c:3677 [inline] __do_sys_mount fs/namespace.c:3886 [inline] __se_sys_mount fs/namespace.c:3863 [inline] __arm64_sys_mount+0x45c/0x594 fs/namespace.c:3863 __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:51 el0_svc_common+0x130/0x23c arch/arm64/kernel/syscall.c:136 do_el0_svc+0x48/0x58 arch/arm64/kernel/syscall.c:155 el0_svc+0x54/0x158 arch/arm64/kernel/entry-common.c:678 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:696 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:595 The buggy address belongs to the physical page: page:00000000c25f236a refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x11c87d flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff) page_type: 0xffffffff() raw: 05ffc00000000000 fffffc0003721f88 ffff0001b416cbb0 0000000000000000 raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff0000dc87d300: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff0000dc87d380: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff0000dc87d400: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff0000dc87d480: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff0000dc87d500: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ================================================================== syz-executor383: attempt to access beyond end of device loop0: rw=0, sector=32768, nr_sectors = 2 limit=4096 syz-executor383: attempt to access beyond end of device loop0: rw=0, sector=32770, nr_sectors = 2 limit=4096 syz-executor383: attempt to access beyond end of device loop0: rw=0, sector=32772, nr_sectors = 2 limit=4096