gfs2: invalid mount option: hash ntfs: (device loop5): is_boot_sector_ntfs(): Invalid end of sector marker. gfs2: can't parse mount arguments ================================================================== BUG: KASAN: use-after-free in ntfs_attr_find+0xacd/0xc20 fs/ntfs/attrib.c:611 Read of size 2 at addr ffff888096452742 by task syz-executor.5/9803 CPU: 0 PID: 9803 Comm: syz-executor.5 Not tainted 4.14.293-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/26/2022 Call Trace: __dump_stack lib/dump_stack.c:17 [inline] dump_stack+0x1b2/0x281 lib/dump_stack.c:58 print_address_description.cold+0x54/0x1d3 mm/kasan/report.c:252 kasan_report_error.cold+0x8a/0x191 mm/kasan/report.c:351 kasan_report mm/kasan/report.c:409 [inline] __asan_report_load_n_noabort+0x6b/0x80 mm/kasan/report.c:440 ntfs_attr_find+0xacd/0xc20 fs/ntfs/attrib.c:611 ntfs_attr_lookup+0xeca/0x1f30 fs/ntfs/attrib.c:1207 ntfs_read_inode_mount+0x726/0x2060 fs/ntfs/inode.c:1879 ntfs_fill_super+0x9a6/0x7170 fs/ntfs/super.c:2871 mount_bdev+0x2b3/0x360 fs/super.c:1134 mount_fs+0x92/0x2a0 fs/super.c:1237 vfs_kern_mount.part.0+0x5b/0x470 fs/namespace.c:1046 vfs_kern_mount fs/namespace.c:1036 [inline] do_new_mount fs/namespace.c:2572 [inline] do_mount+0xe65/0x2a30 fs/namespace.c:2905 SYSC_mount fs/namespace.c:3121 [inline] SyS_mount+0xa8/0x120 fs/namespace.c:3098 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb RIP: 0033:0x7fd2b108e93a RSP: 002b:00007fd2afa01f88 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5 RAX: ffffffffffffffda RBX: 0000000020000200 RCX: 00007fd2b108e93a RDX: 0000000020000000 RSI: 0000000020000100 RDI: 00007fd2afa01fe0 RBP: 00007fd2afa02020 R08: 00007fd2afa02020 R09: 0000000020000000 R10: 0000000000000000 R11: 0000000000000202 R12: 0000000020000000 R13: 0000000020000100 R14: 00007fd2afa01fe0 R15: 0000000020079ca0 Allocated by task 4626: save_stack mm/kasan/kasan.c:447 [inline] set_track mm/kasan/kasan.c:459 [inline] kasan_kmalloc+0xeb/0x160 mm/kasan/kasan.c:551 kmem_cache_alloc+0x124/0x3c0 mm/slab.c:3552 getname_flags+0xc8/0x550 fs/namei.c:138 do_sys_open+0x1ce/0x410 fs/open.c:1075 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb Freed by task 4626: save_stack mm/kasan/kasan.c:447 [inline] set_track mm/kasan/kasan.c:459 [inline] kasan_slab_free+0xc3/0x1a0 mm/kasan/kasan.c:524 __cache_free mm/slab.c:3496 [inline] kmem_cache_free+0x7c/0x2b0 mm/slab.c:3758 putname+0xcd/0x110 fs/namei.c:259 do_sys_open+0x203/0x410 fs/open.c:1090 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292 entry_SYSCALL_64_after_hwframe+0x46/0xbb The buggy address belongs to the object at ffff888096452240 which belongs to the cache names_cache of size 4096 The buggy address is located 1282 bytes inside of 4096-byte region [ffff888096452240, ffff888096453240) The buggy address belongs to the page: page:ffffea0002591480 count:1 mapcount:0 mapping:ffff888096452240 index:0x0 compound_mapcount: 0 flags: 0xfff00000008100(slab|head) raw: 00fff00000008100 ffff888096452240 0000000000000000 0000000100000001 raw: ffffea0002591420 ffffea0002591520 ffff88823f8c1200 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff888096452600: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff888096452680: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb >ffff888096452700: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff888096452780: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff888096452800: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ==================================================================