loop4: detected capacity change from 0 to 4096 ntfs3: loop4: Different NTFS sector size (4096) and media sector size (512). ntfs3: loop4: RAW NTFS volume: Filesystem size 16384.00 Gb > volume size 0.00 Gb. Mount in read-only. ntfs3: loop4: NTFS 16384.00 Gb is too big to use 32 bits per cluster. ================================================================== BUG: KASAN: use-after-free in memcmp+0x172/0x1c0 lib/string.c:681 Read of size 8 at addr ffff888051e68002 by task syz-executor.4/18464 CPU: 1 PID: 18464 Comm: syz-executor.4 Not tainted 6.6.0-rc5-syzkaller-00067-g8182d7a3f1b8 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/06/2023 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x1b0 lib/dump_stack.c:106 print_address_description mm/kasan/report.c:364 [inline] print_report+0xc4/0x620 mm/kasan/report.c:475 kasan_report+0xda/0x110 mm/kasan/report.c:588 memcmp+0x172/0x1c0 lib/string.c:681 memcmp include/linux/fortify-string.h:728 [inline] ntfs_init_from_boot fs/ntfs3/super.c:858 [inline] ntfs_fill_super+0x6f2/0x4350 fs/ntfs3/super.c:1139 get_tree_bdev+0x3b5/0x650 fs/super.c:1577 vfs_get_tree+0x8c/0x370 fs/super.c:1750 do_new_mount fs/namespace.c:3335 [inline] path_mount+0x1492/0x1ed0 fs/namespace.c:3662 do_mount fs/namespace.c:3675 [inline] __do_sys_mount fs/namespace.c:3884 [inline] __se_sys_mount fs/namespace.c:3861 [inline] __x64_sys_mount+0x293/0x310 fs/namespace.c:3861 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x38/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f2d2387e1ea Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 09 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f2d24549ee8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 00007f2d24549f80 RCX: 00007f2d2387e1ea RDX: 00000000200000c0 RSI: 000000002001f1c0 RDI: 00007f2d24549f40 RBP: 00000000200000c0 R08: 00007f2d24549f80 R09: 0000000000010040 R10: 0000000000010040 R11: 0000000000000202 R12: 000000002001f1c0 R13: 00007f2d24549f40 R14: 000000000001f1b9 R15: 0000000020000100 The buggy address belongs to the physical page: page:ffffea0001479a00 refcount:0 mapcount:-128 mapping:0000000000000000 index:0x1 pfn:0x51e68 flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) page_type: 0xffffff7f(buddy) raw: 00fff00000000000 ffffea0000b40a08 ffffea0000b6a608 0000000000000000 raw: 0000000000000001 0000000000000003 00000000ffffff7f 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as freed page last allocated via order 0, migratetype Movable, gfp_mask 0x140dca(GFP_HIGHUSER_MOVABLE|__GFP_COMP|__GFP_ZERO), pid 17816, tgid 17808 (syz-executor.2), ts 1834166821791, free_ts 1836978265788 set_page_owner include/linux/page_owner.h:31 [inline] post_alloc_hook+0x2cf/0x340 mm/page_alloc.c:1536 prep_new_page mm/page_alloc.c:1543 [inline] get_page_from_freelist+0xee0/0x2f20 mm/page_alloc.c:3170 __alloc_pages+0x1d0/0x4a0 mm/page_alloc.c:4426 __folio_alloc+0x16/0x40 mm/page_alloc.c:4458 vma_alloc_folio+0x156/0x890 mm/mempolicy.c:2258 wp_page_copy mm/memory.c:3070 [inline] do_wp_page+0x1971/0x3420 mm/memory.c:3449 handle_pte_fault mm/memory.c:4994 [inline] __handle_mm_fault+0x1d1b/0x3e10 mm/memory.c:5119 handle_mm_fault+0x478/0xa00 mm/memory.c:5284 do_user_addr_fault+0x3d1/0x1000 arch/x86/mm/fault.c:1413 handle_page_fault arch/x86/mm/fault.c:1505 [inline] exc_page_fault+0x5c/0xd0 arch/x86/mm/fault.c:1561 asm_exc_page_fault+0x26/0x30 arch/x86/include/asm/idtentry.h:570 page last free stack trace: reset_page_owner include/linux/page_owner.h:24 [inline] free_pages_prepare mm/page_alloc.c:1136 [inline] free_unref_page_prepare+0x476/0xa40 mm/page_alloc.c:2312 free_unref_page_list+0xe6/0xb30 mm/page_alloc.c:2451 release_pages+0x32a/0x14e0 mm/swap.c:1042 tlb_batch_pages_flush+0x9a/0x190 mm/mmu_gather.c:98 zap_pte_range mm/memory.c:1534 [inline] zap_pmd_range mm/memory.c:1573 [inline] zap_pud_range mm/memory.c:1602 [inline] zap_p4d_range mm/memory.c:1623 [inline] unmap_page_range+0x19b7/0x2c10 mm/memory.c:1644 unmap_single_vma+0x194/0x2b0 mm/memory.c:1690 unmap_vmas+0x1e2/0x330 mm/memory.c:1731 exit_mmap+0x1ad/0xa60 mm/mmap.c:3210 __mmput+0x12a/0x4d0 kernel/fork.c:1349 mmput+0x62/0x70 kernel/fork.c:1371 exit_mm kernel/exit.c:567 [inline] do_exit+0x9ad/0x2a20 kernel/exit.c:861 do_group_exit+0xd4/0x2a0 kernel/exit.c:1024 get_signal+0x23ba/0x2790 kernel/signal.c:2892 arch_do_signal_or_restart+0x90/0x7f0 arch/x86/kernel/signal.c:309 exit_to_user_mode_loop kernel/entry/common.c:168 [inline] exit_to_user_mode_prepare+0x11f/0x240 kernel/entry/common.c:204 __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline] syscall_exit_to_user_mode+0x1d/0x60 kernel/entry/common.c:296 Memory state around the buggy address: ffff888051e67f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff888051e67f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff888051e68000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff888051e68080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff888051e68100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ==================================================================