[v5.15] WARNING: kmalloc bug in ntfs_load_attr_list

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 68efe5a6c16a Linux 5.15.197
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1506a19a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=7e6ed99963d6ee1d
dashboard link: https://syzkaller.appspot.com/bug?extid=0e1aca5ad7271973c68d
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1070d83a580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13a5b1fc580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/900f9b9bd850/disk-68efe5a6.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1e089a5019a6/vmlinux-68efe5a6.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b319f477b907/bzImage-68efe5a6.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/f005eda42be6/mount_0.gz

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

loop0: detected capacity change from 0 to 4096
ntfs3: loop0: Different NTFS' sector size (4096) and media sector size (512)
------------[ cut here ]------------
WARNING: CPU: 0 PID: 4319 at mm/util.c:630 kvmalloc_node+0x12b/0x130 mm/util.c:630
Modules linked in:
CPU: 0 PID: 4319 Comm: syz.0.17 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:kvmalloc_node+0x12b/0x130 mm/util.c:630
Code: 41 5f 5d c3 89 de 81 e6 00 20 00 00 31 ff e8 7c d5 d1 ff 81 e3 00 20 00 00 74 0a e8 0f d2 d1 ff 45 31 ff eb d3 e8 05 d2 d1 ff <0f> 0b eb f2 90 41 56 53 49 89 f6 48 89 fb e8 f2 d1 d1 ff 48 83 fb
RSP: 0018:ffffc9000301f740 EFLAGS: 00010293
RAX: ffffffff81a5fa0b RBX: 0000000000000000 RCX: ffff88802831bb80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 00000000ffffffff R08: 0000000000012cc0 R09: 00000000ffffffff
R10: fffff52000603ebd R11: 1ffff92000603eb8 R12: 0000000000000000
R13: ffff8880236fa0b8 R14: 0000000100000000 R15: 0000000000000000
FS: 000055556e349500(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd7bb1f0000 CR3: 000000001e16b000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
kvmalloc include/linux/mm.h:816 [inline]
ntfs_load_attr_list+0x11b/0x4f0 fs/ntfs3/attrlist.c:56
ntfs_read_mft fs/ntfs3/inode.c:180 [inline]
ntfs_iget5+0x10c3/0x3670 fs/ntfs3/inode.c:526
ntfs_loadlog_and_replay+0x139/0x480 fs/ntfs3/fsntfs.c:272
ntfs_fill_super+0x20d4/0x3c10 fs/ntfs3/super.c:1013
get_tree_bdev+0x3f1/0x610 fs/super.c:1325
vfs_get_tree+0x88/0x270 fs/super.c:1530
do_new_mount+0x24a/0xa40 fs/namespace.c:3034
do_mount fs/namespace.c:3377 [inline]
__do_sys_mount fs/namespace.c:3585 [inline]
__se_sys_mount+0x2d6/0x3c0 fs/namespace.c:3562
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f7b542bfeea
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffed26d6ab8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007ffed26d6b40 RCX: 00007f7b542bfeea
RDX: 0000200000000040 RSI: 00002000000000c0 RDI: 00007ffed26d6b00
RBP: 0000200000000040 R08: 00007ffed26d6b40 R09: 0000000000000005
R10: 0000000000000005 R11: 0000000000000246 R12: 00002000000000c0
R13: 00007ffed26d6b00 R14: 000000000001f23e R15: 0000200000000100
</TASK>


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