[syzbot] [ntfs3?] KMSAN: kernel-infoleak in listxattr

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8735c7c84d1b Merge tag '6.7rc7-smb3-srv-fix' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11dec9a1e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=d4130d4bb32c48ef
dashboard link: https://syzkaller.appspot.com/bug?extid=608044293020556ff16b
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/03cd0531b6f3/disk-8735c7c8.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6bb4ebecaed0/vmlinux-8735c7c8.xz
kernel image: https://storage.googleapis.com/syzbot-assets/e40c5a86a2b5/bzImage-8735c7c8.xz

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

=====================================================
BUG: KMSAN: kernel-infoleak in instrument_copy_to_user include/linux/instrumented.h:114 [inline]
BUG: KMSAN: kernel-infoleak in _copy_to_user+0xbc/0x100 lib/usercopy.c:40
instrument_copy_to_user include/linux/instrumented.h:114 [inline]
_copy_to_user+0xbc/0x100 lib/usercopy.c:40
copy_to_user include/linux/uaccess.h:191 [inline]
listxattr+0x2e9/0x6a0 fs/xattr.c:843
path_listxattr fs/xattr.c:865 [inline]
__do_sys_listxattr fs/xattr.c:877 [inline]
__se_sys_listxattr fs/xattr.c:874 [inline]
__x64_sys_listxattr+0x16b/0x2e0 fs/xattr.c:874
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

Uninit was stored to memory at:
ntfs_list_ea fs/ntfs3/xattr.c:232 [inline]
ntfs_listxattr+0x5d2/0x8d0 fs/ntfs3/xattr.c:733
vfs_listxattr fs/xattr.c:494 [inline]
listxattr+0x1f0/0x6a0 fs/xattr.c:841
path_listxattr fs/xattr.c:865 [inline]
__do_sys_listxattr fs/xattr.c:877 [inline]
__se_sys_listxattr fs/xattr.c:874 [inline]
__x64_sys_listxattr+0x16b/0x2e0 fs/xattr.c:874
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

Uninit was created at:
slab_post_alloc_hook+0x129/0xa70 mm/slab.h:768
slab_alloc_node mm/slub.c:3478 [inline]
__kmem_cache_alloc_node+0x5c9/0x970 mm/slub.c:3517
__do_kmalloc_node mm/slab_common.c:1006 [inline]
__kmalloc+0x121/0x3c0 mm/slab_common.c:1020
kmalloc include/linux/slab.h:604 [inline]
ntfs_read_ea+0x78c/0x10b0 fs/ntfs3/xattr.c:118
ntfs_list_ea fs/ntfs3/xattr.c:204 [inline]
ntfs_listxattr+0x173/0x8d0 fs/ntfs3/xattr.c:733
vfs_listxattr fs/xattr.c:494 [inline]
listxattr+0x1f0/0x6a0 fs/xattr.c:841
path_listxattr fs/xattr.c:865 [inline]
__do_sys_listxattr fs/xattr.c:877 [inline]
__se_sys_listxattr fs/xattr.c:874 [inline]
__x64_sys_listxattr+0x16b/0x2e0 fs/xattr.c:874
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0x44/0x110 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x63/0x6b

Bytes 26-31 of 63 are uninitialized
Memory access of size 63 starts at ffff888103174b40
Data copied to user address 0000000020000080

CPU: 0 PID: 5727 Comm: syz-executor.4 Not tainted 6.7.0-rc7-syzkaller-00029-g8735c7c84d1b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
=====================================================


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