From: syzbot <syzbot+332bd4e9d148f11a87dc@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, ntfs3@lists.linux.dev,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [ntfs3?] KMSAN: uninit-value in ntfs_read_hdr (3)
Date: Wed, 17 Sep 2025 15:55:30 -0700 [thread overview]
Message-ID: <68cb3c62.050a0220.50883.002b.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 5aca7966d2a7 Merge tag 'perf-tools-fixes-for-v6.17-2025-09..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12998c7c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1b093ccee5a9e08c
dashboard link: https://syzkaller.appspot.com/bug?extid=332bd4e9d148f11a87dc
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=14ccc534580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16998c7c580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/7dcf9f15bc6a/disk-5aca7966.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/8836a30085d9/vmlinux-5aca7966.xz
kernel image: https://storage.googleapis.com/syzbot-assets/b00f10dc0558/bzImage-5aca7966.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/78b7a2febda1/mount_0.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+332bd4e9d148f11a87dc@syzkaller.appspotmail.com
=====================================================
BUG: KMSAN: uninit-value in ntfs_dir_emit fs/ntfs3/dir.c:335 [inline]
BUG: KMSAN: uninit-value in ntfs_read_hdr+0xfcc/0x13e0 fs/ntfs3/dir.c:385
ntfs_dir_emit fs/ntfs3/dir.c:335 [inline]
ntfs_read_hdr+0xfcc/0x13e0 fs/ntfs3/dir.c:385
ntfs_readdir+0xf21/0x1a30 fs/ntfs3/dir.c:496
iterate_dir+0x452/0x620 fs/readdir.c:108
__do_sys_getdents64 fs/readdir.c:410 [inline]
__se_sys_getdents64+0x17e/0x550 fs/readdir.c:396
__x64_sys_getdents64+0x97/0xe0 fs/readdir.c:396
x64_sys_call+0x3a14/0x3e20 arch/x86/include/generated/asm/syscalls_64.h:218
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Uninit was stored to memory at:
ntfs_write_bh+0x6ae/0xe90 fs/ntfs3/fsntfs.c:1430
indx_write fs/ntfs3/index.c:1027 [inline]
indx_insert_into_buffer+0x287/0x2010 fs/ntfs3/index.c:1809
indx_insert_entry+0xcde/0x1050 fs/ntfs3/index.c:1986
ni_add_name+0xef7/0x11e0 fs/ntfs3/frecord.c:2995
ntfs_link_inode+0x221/0x350 fs/ntfs3/inode.c:1728
ntfs_link+0x20e/0x500 fs/ntfs3/namei.c:146
vfs_link+0x8eb/0xb30 fs/namei.c:4854
do_linkat+0x4af/0x1040 fs/namei.c:4924
__do_sys_link fs/namei.c:4958 [inline]
__se_sys_link fs/namei.c:4956 [inline]
__x64_sys_link+0xd7/0x140 fs/namei.c:4956
x64_sys_call+0x162f/0x3e20 arch/x86/include/generated/asm/syscalls_64.h:87
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Uninit was stored to memory at:
hdr_insert_de+0x4c8/0x550 fs/ntfs3/index.c:838
indx_insert_into_buffer+0x1b6/0x2010 fs/ntfs3/index.c:1805
indx_insert_entry+0xcde/0x1050 fs/ntfs3/index.c:1986
ni_add_name+0xef7/0x11e0 fs/ntfs3/frecord.c:2995
ntfs_link_inode+0x221/0x350 fs/ntfs3/inode.c:1728
ntfs_link+0x20e/0x500 fs/ntfs3/namei.c:146
vfs_link+0x8eb/0xb30 fs/namei.c:4854
do_linkat+0x4af/0x1040 fs/namei.c:4924
__do_sys_link fs/namei.c:4958 [inline]
__se_sys_link fs/namei.c:4956 [inline]
__x64_sys_link+0xd7/0x140 fs/namei.c:4956
x64_sys_call+0x162f/0x3e20 arch/x86/include/generated/asm/syscalls_64.h:87
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Uninit was created at:
slab_post_alloc_hook mm/slub.c:4197 [inline]
slab_alloc_node mm/slub.c:4240 [inline]
kmem_cache_alloc_noprof+0x81b/0xec0 mm/slub.c:4247
ntfs_link_inode+0x90/0x350 fs/ntfs3/inode.c:1716
ntfs_link+0x20e/0x500 fs/ntfs3/namei.c:146
vfs_link+0x8eb/0xb30 fs/namei.c:4854
do_linkat+0x4af/0x1040 fs/namei.c:4924
__do_sys_link fs/namei.c:4958 [inline]
__se_sys_link fs/namei.c:4956 [inline]
__x64_sys_link+0xd7/0x140 fs/namei.c:4956
x64_sys_call+0x162f/0x3e20 arch/x86/include/generated/asm/syscalls_64.h:87
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0xd9/0x210 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
CPU: 0 UID: 0 PID: 5963 Comm: syz-executor Not tainted syzkaller #0 PREEMPT(none)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025
=====================================================
---
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 syzkaller@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
next reply other threads:[~2025-09-17 22:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 22:55 syzbot [this message]
2025-09-18 19:35 ` Forwarded: Re: [syzbot] [ntfs3?] KMSAN: uninit-value in ntfs_read_hdr (3) syzbot
2025-09-22 18:03 ` syzbot
2025-10-26 15:54 ` Forwarded: syzbot
2025-10-29 20:03 ` Forwarded: Re: KMSAN: uninit-value in ntfs_read_hdr (3) syzbot
2025-11-05 7:52 ` syzbot
[not found] <20250918193455.115481-1-sidharthseela@gmail.com>
2025-09-18 19:56 ` [syzbot] [ntfs3?] " syzbot
[not found] <20250922180305.163051-2-sidharthseela@gmail.com>
2025-09-22 19:42 ` syzbot
[not found] <CAPqLRf3LgEErOjV3V2A6XsaBL=fvhGPFooXWSv4Vt2Q6juWGXQ@mail.gmail.com>
2025-10-26 16:26 ` syzbot
[not found] <CAPqLRf1_Y=mCBQKKHoSZJ3BxxsfMWYd+asreyGLofV+ge2UySg@mail.gmail.com>
2025-10-29 20:50 ` syzbot
[not found] <CAPqLRf36qEgmaLxkGfURAQ549Em_==asxBSuy6PcoKYpXi05ag@mail.gmail.com>
2025-11-05 8:42 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=68cb3c62.050a0220.50883.002b.GAE@google.com \
--to=syzbot+332bd4e9d148f11a87dc@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.