[v5.15] KASAN: use-after-free Read in ntfs_attr_find

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ddcaf4999061 Linux 5.15.147
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1189f007e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=ab92786ed9f7c373
dashboard link: https://syzkaller.appspot.com/bug?extid=0ac549e1686580665949
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
userspace arch: arm64

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9f538e3b5b6b/disk-ddcaf499.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/aff958e6c838/vmlinux-ddcaf499.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b812c40b66fa/Image-ddcaf499.gz.xz

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

loop1: detected capacity change from 0 to 4096
==================================================================
BUG: KASAN: use-after-free in ntfs_attr_find+0x5a0/0x9e4 fs/ntfs/attrib.c:609
Read of size 2 at addr ffff000135702442 by task syz-executor.1/7679

CPU: 0 PID: 7679 Comm: syz-executor.1 Not tainted 5.15.147-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
Call trace:
dump_backtrace+0x0/0x530 arch/arm64/kernel/stacktrace.c:152
show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:216
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x108/0x170 lib/dump_stack.c:106
print_address_description+0x7c/0x3f0 mm/kasan/report.c:248
__kasan_report mm/kasan/report.c:434 [inline]
kasan_report+0x174/0x1e4 mm/kasan/report.c:451
__asan_report_load_n_noabort+0x40/0x4c mm/kasan/report_generic.c:319
ntfs_attr_find+0x5a0/0x9e4 fs/ntfs/attrib.c:609
ntfs_attr_lookup+0x3e0/0x1cf0
ntfs_read_locked_inode+0x880/0x38f0 fs/ntfs/inode.c:666
ntfs_iget+0x110/0x19c fs/ntfs/inode.c:177
load_and_init_mft_mirror fs/ntfs/super.c:1027 [inline]
load_system_files+0xe0/0x4228 fs/ntfs/super.c:1772
ntfs_fill_super+0x1670/0x24e8 fs/ntfs/super.c:2894
mount_bdev+0x274/0x370 fs/super.c:1387
ntfs_mount+0x44/0x58 fs/ntfs/super.c:3051
legacy_get_tree+0xd4/0x16c fs/fs_context.c:611
vfs_get_tree+0x90/0x274 fs/super.c:1517
do_new_mount+0x25c/0x8c4 fs/namespace.c:2994
path_mount+0x594/0x101c fs/namespace.c:3324
do_mount fs/namespace.c:3337 [inline]
__do_sys_mount fs/namespace.c:3545 [inline]
__se_sys_mount fs/namespace.c:3522 [inline]
__arm64_sys_mount+0x510/0x5e0 fs/namespace.c:3522
__invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:608
el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:626
el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584

The buggy address belongs to the page:
page:00000000e10f082c refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x175702
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000000 fffffc0004aea7c8 fffffc0005a0f348 0000000000000000
raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:
ffff000135702300: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff000135702380: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff000135702400: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff000135702480: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff000135702500: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
==================================================================


---
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 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

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: ddcaf4999061 Linux 5.15.147
git tree: linux-5.15.y

console output: https://syzkaller.appspot.com/x/log.txt?x=15b3383be80000

kernel config: https://syzkaller.appspot.com/x/.config?x=ab92786ed9f7c373
dashboard link: https://syzkaller.appspot.com/bug?extid=0ac549e1686580665949
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=13e5a91be80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12bae28be80000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9f538e3b5b6b/disk-ddcaf499.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/aff958e6c838/vmlinux-ddcaf499.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b812c40b66fa/Image-ddcaf499.gz.xz

mounted in repro: https://storage.googleapis.com/syzbot-assets/0af5c75686f3/mount_0.gz

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

loop0: detected capacity change from 0 to 4096

==================================================================
BUG: KASAN: use-after-free in ntfs_attr_find+0x5a0/0x9e4 fs/ntfs/attrib.c:609

Read of size 2 at addr ffff000189421442 by task syz-executor165/3969

CPU: 1 PID: 3969 Comm: syz-executor165 Not tainted 5.15.147-syzkaller #0

page:00000000dcecdb73 refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x1c9421
flags: 0x5ffc00000000000(node=0|zone=2|lastcpupid=0x7ff)
raw: 05ffc00000000000 fffffc0005a02408 ffff0001b482b920 0000000000000000

raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000
page dumped because: kasan: bad access detected

Memory state around the buggy address:

ffff000189421300: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff000189421380: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
>ffff000189421400: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
^
ffff000189421480: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
ffff000189421500: 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 0x1 as bad. Run chkdsk.
ntfs: (device loop0): load_system_files(): Failed to load $MFTMirr. Will not be able to remount read-write. Run ntfsfix and/or chkdsk.
ntfs: (device loop0): map_mft_record_page(): Mft record 0xa is corrupt. Run chkdsk.
ntfs: (device loop0): map_mft_record(): Failed with error code 5.
ntfs: (device loop0): ntfs_read_locked_inode(): Failed with error code -5. Marking corrupt inode 0xa as bad. Run chkdsk.
ntfs: (device loop0): load_and_init_upcase(): Failed to load $UpCase from the volume. Using default.
attempt to access beyond end of device
loop0: rw=0, want=32770, limit=4096
ntfs: (device loop0): ntfs_end_buffer_async_read(): Buffer I/O error, logical block 0x4000.
attempt to access beyond end of device
loop0: rw=0, want=32772, limit=4096
ntfs: (device loop0): ntfs_end_buffer_async_read(): Buffer I/O error, logical block 0x4001.
attempt to access beyond end of device
loop0: rw=0, want=32774, limit=4096


---
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.