[v6.1] KASAN: slab-out-of-bounds Write in ntfs_set_ea

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 59d7b1a7104a Linux 6.1.117
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=170cd2c0580000
kernel config: https://syzkaller.appspot.com/x/.config?x=a689a3c1ad3115c7
dashboard link: https://syzkaller.appspot.com/bug?extid=09cb867ecb33ece66d64
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=155c9378580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=108cd2c0580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/61a4b203aa79/disk-59d7b1a7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/37495321edfd/vmlinux-59d7b1a7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c7da55de72ce/bzImage-59d7b1a7.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/39f3a01067e8/mount_0.gz

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

==================================================================
BUG: KASAN: slab-out-of-bounds in ntfs_set_ea+0x1394/0x1660 fs/ntfs3/xattr.c:411
Write of size 4 at addr ffff88807e21ef5c by task syz-executor117/4299

CPU: 1 PID: 4299 Comm: syz-executor117 Not tainted 6.1.117-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/30/2024
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0x1e3/0x2cb lib/dump_stack.c:106
print_address_description mm/kasan/report.c:284 [inline]
print_report+0x15f/0x4f0 mm/kasan/report.c:395
kasan_report+0x136/0x160 mm/kasan/report.c:495
ntfs_set_ea+0x1394/0x1660 fs/ntfs3/xattr.c:411
ntfs_save_wsl_perm+0x139/0x490 fs/ntfs3/xattr.c:976
ntfs3_setattr+0x961/0xb70 fs/ntfs3/file.c:816
notify_change+0xce3/0xfc0 fs/attr.c:499
chmod_common+0x2a7/0x4b0 fs/open.c:606
do_fchmodat fs/open.c:645 [inline]
__do_sys_fchmodat fs/open.c:658 [inline]
__se_sys_fchmodat fs/open.c:655 [inline]
__x64_sys_fchmodat+0x117/0x1a0 fs/open.c:655
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fabb2161b19
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 71 1d 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 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:00007fabb20f2218 EFLAGS: 00000246 ORIG_RAX: 000000000000010c
RAX: ffffffffffffffda RBX: 00007fabb22016f8 RCX: 00007fabb2161b19
RDX: 0000000000000141 RSI: 0000000020000200 RDI: 00000000ffffff9c
RBP: 00007fabb22016f0 R08: 00007ffdb1e6e977 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fabb21ce08c
R13: 0030656c69662f2e R14: 7974697275636573 R15: 6f6f6c2f7665642f
</TASK>

The buggy address belongs to the object at ffff88807e21ef40
which belongs to the cache kmalloc-32 of size 32
The buggy address is located 28 bytes inside of
32-byte region [ffff88807e21ef40, ffff88807e21ef60)

The buggy address belongs to the physical page:
page:ffffea0001f88780 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x7e21e
flags: 0xfff00000000200(slab|node=0|zone=1|lastcpupid=0x7ff)
raw: 00fff00000000200 0000000000000000 dead000000000122 ffff888017c41500
raw: 0000000000000000 0000000080400040 00000001ffffffff 0000000000000000
page dumped because: kasan: bad access detected
page_owner tracks the page as allocated
page last allocated via order 0, migratetype Unmovable, gfp_mask 0x12c40(GFP_NOFS|__GFP_NOWARN|__GFP_NORETRY), pid 4254, tgid 4254 (udevd), ts 78589845938, free_ts 78499692962
set_page_owner include/linux/page_owner.h:31 [inline]
post_alloc_hook+0x18d/0x1b0 mm/page_alloc.c:2517
prep_new_page mm/page_alloc.c:2524 [inline]
get_page_from_freelist+0x3731/0x38d0 mm/page_alloc.c:4313
__alloc_pages+0x28d/0x770 mm/page_alloc.c:5589
alloc_slab_page+0x6a/0x150 mm/slub.c:1794
allocate_slab mm/slub.c:1939 [inline]
new_slab+0x84/0x2d0 mm/slub.c:1992
___slab_alloc+0xc20/0x1270 mm/slub.c:3180
__slab_alloc mm/slub.c:3279 [inline]
slab_alloc_node mm/slub.c:3364 [inline]
__kmem_cache_alloc_node+0x19f/0x260 mm/slub.c:3437
__do_kmalloc_node mm/slab_common.c:935 [inline]
__kmalloc+0xa1/0x230 mm/slab_common.c:949
kmalloc include/linux/slab.h:562 [inline]
kzalloc include/linux/slab.h:693 [inline]
tomoyo_encode2 security/tomoyo/realpath.c:45 [inline]
tomoyo_encode+0x26b/0x530 security/tomoyo/realpath.c:80
tomoyo_realpath_from_path+0x594/0x5d0 security/tomoyo/realpath.c:283
tomoyo_get_realpath security/tomoyo/file.c:151 [inline]
tomoyo_path_perm+0x29f/0x710 security/tomoyo/file.c:822
security_inode_getattr+0xcf/0x120 security/security.c:1361
vfs_getattr+0x26/0x360 fs/stat.c:158
vfs_statx+0x194/0x4b0 fs/stat.c:233
vfs_fstatat fs/stat.c:267 [inline]
__do_sys_newfstatat fs/stat.c:437 [inline]
__se_sys_newfstatat fs/stat.c:431 [inline]
__x64_sys_newfstatat+0x151/0x1e0 fs/stat.c:431
do_syscall_x64 arch/x86/entry/common.c:51 [inline]
do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:81
page last free stack trace:
reset_page_owner include/linux/page_owner.h:24 [inline]
free_pages_prepare mm/page_alloc.c:1444 [inline]
free_pcp_prepare mm/page_alloc.c:1494 [inline]
free_unref_page_prepare+0xf63/0x1120 mm/page_alloc.c:3369
free_unref_page+0x33/0x3e0 mm/page_alloc.c:3464
free_slab mm/slub.c:2031 [inline]
discard_slab mm/slub.c:2037 [inline]
__unfreeze_partials+0x1b7/0x210 mm/slub.c:2586
put_cpu_partial+0x17b/0x250 mm/slub.c:2662
qlink_free mm/kasan/quarantine.c:168 [inline]
qlist_free_all+0x76/0xe0 mm/kasan/quarantine.c:187
kasan_quarantine_reduce+0x156/0x170 mm/kasan/quarantine.c:294
__kasan_slab_alloc+0x1f/0x70 mm/kasan/common.c:305
kasan_slab_alloc include/linux/kasan.h:201 [inline]
slab_post_alloc_hook+0x52/0x3a0 mm/slab.h:737
slab_alloc_node mm/slub.c:3398 [inline]
__kmem_cache_alloc_node+0x137/0x260 mm/slub.c:3437
kmalloc_trace+0x26/0xe0 mm/slab_common.c:1026
kmalloc include/linux/slab.h:557 [inline]
kzalloc include/linux/slab.h:693 [inline]
nsim_fib6_rt_create drivers/net/netdevsim/fib.c:547 [inline]
nsim_fib6_rt_insert drivers/net/netdevsim/fib.c:752 [inline]
nsim_fib6_event drivers/net/netdevsim/fib.c:856 [inline]
nsim_fib_event drivers/net/netdevsim/fib.c:889 [inline]
nsim_fib_event_work+0x19be/0x4120 drivers/net/netdevsim/fib.c:1494
process_one_work+0x8a9/0x11d0 kernel/workqueue.c:2292
process_scheduled_works kernel/workqueue.c:2355 [inline]
worker_thread+0xd04/0x1200 kernel/workqueue.c:2441
kthread+0x28d/0x320 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295

Memory state around the buggy address:
ffff88807e21ee00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff88807e21ee80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
>ffff88807e21ef00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
^
ffff88807e21ef80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc
ffff88807e21f000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
==================================================================


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