[v6.1] KASAN: use-after-free Read in ntfs_attr_find (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 4aa6747d9352 Linux 6.1.69
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=17440bbee80000
kernel config: https://syzkaller.appspot.com/x/.config?x=e3efadc69a1b0490
dashboard link: https://syzkaller.appspot.com/bug?extid=af4e5d45b6b48a6e89b6
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13da6d9ee80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12b27409e80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/31c5d5a5223e/disk-4aa6747d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/85c4938c28c7/vmlinux-4aa6747d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/0fcb53eb57be/Image-4aa6747d.gz.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/d83907939630/mount_0.gz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+af4e5d...@syzkaller.appspotmail.com

loop0: detected capacity change from 0 to 4096
ntfs: (device loop0): is_boot_sector_ntfs(): Invalid end of sector marker.
==================================================================
BUG: KASAN: use-after-free in ntfs_attr_find+0x5a0/0x9d0 fs/ntfs/attrib.c:609
Read of size 2 at addr ffff0000e16e3042 by task syz-executor349/4225

CPU: 0 PID: 4225 Comm: syz-executor349 Not tainted 6.1.69-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/10/2023
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:284 [inline]
print_report+0x174/0x4c0 mm/kasan/report.c:395
kasan_report+0xd4/0x130 mm/kasan/report.c:495
__asan_report_load_n_noabort+0x28/0x34 mm/kasan/report_generic.c:361
ntfs_attr_find+0x5a0/0x9d0 fs/ntfs/attrib.c:609
ntfs_attr_lookup+0x3dc/0x1cd8
ntfs_read_locked_inode+0x87c/0x38e0 fs/ntfs/inode.c:666
ntfs_read_inode_mount+0xbb0/0x2044 fs/ntfs/inode.c:2098
ntfs_fill_super+0x13b4/0x2314 fs/ntfs/super.c:2855
mount_bdev+0x274/0x370 fs/super.c:1432
ntfs_mount+0x44/0x58 fs/ntfs/super.c:3049
legacy_get_tree+0xd4/0x16c fs/fs_context.c:632
vfs_get_tree+0x90/0x274 fs/super.c:1562
do_new_mount+0x25c/0x8c4 fs/namespace.c:3040
path_mount+0x590/0xe5c fs/namespace.c:3370
do_mount fs/namespace.c:3383 [inline]
__do_sys_mount fs/namespace.c:3591 [inline]
__se_sys_mount fs/namespace.c:3568 [inline]
__arm64_sys_mount+0x45c/0x594 fs/namespace.c:3568
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2c0 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x64/0x218 arch/arm64/kernel/syscall.c:206
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:000000004dfbbf4b refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x1216e3
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000000 fffffc00037f3188 fffffc000385ba08 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff0000e16e2f00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ffff0000e16e2f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>ffff0000e16e3000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff0000e16e3080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff0000e16e3100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================
ntfs: (device loop0): ntfs_is_extended_system_file(): Inode hard link count doesn't match number of name attributes. You should run chkdsk.
ntfs: (device loop0): ntfs_read_locked_inode(): $DATA attribute is missing.
ntfs: (device loop0): ntfs_read_locked_inode(): Failed with error code -2. Marking corrupt inode 0x0 as bad. Run chkdsk.
ntfs: (device loop0): ntfs_read_inode_mount(): ntfs_read_inode() of $MFT failed. BUG or corrupt $MFT. Run chkdsk and if no errors are found, please report you saw this message to linux-n...@lists.sourceforge.net
ntfs: (device loop0): ntfs_fill_super(): Failed to load essential metadata.


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup