From: Kees Cook <kees@kernel.org>
To: syzbot+efde959319469ff8d4d7@syzkaller.appspotmail.com,
Edward Adam Davis <eadavis@qq.com>
Cc: Kees Cook <kees@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] hfsplus: fix uninit-value in copy_name
Date: Fri, 5 Jul 2024 14:20:54 -0700 [thread overview]
Message-ID: <172021445223.2844396.7059951310501602233.b4-ty@kernel.org> (raw)
In-Reply-To: <tencent_8BBB6433BC9E1C1B7B4BDF1BF52574BA8808@qq.com>
On Tue, 21 May 2024 13:21:46 +0800, Edward Adam Davis wrote:
> [syzbot reported]
> BUG: KMSAN: uninit-value in sized_strscpy+0xc4/0x160
> sized_strscpy+0xc4/0x160
> copy_name+0x2af/0x320 fs/hfsplus/xattr.c:411
> hfsplus_listxattr+0x11e9/0x1a50 fs/hfsplus/xattr.c:750
> vfs_listxattr fs/xattr.c:493 [inline]
> listxattr+0x1f3/0x6b0 fs/xattr.c:840
> path_listxattr fs/xattr.c:864 [inline]
> __do_sys_listxattr fs/xattr.c:876 [inline]
> __se_sys_listxattr fs/xattr.c:873 [inline]
> __x64_sys_listxattr+0x16b/0x2f0 fs/xattr.c:873
> x64_sys_call+0x2ba0/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:195
> do_syscall_x64 arch/x86/entry/common.c:52 [inline]
> do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83
> entry_SYSCALL_64_after_hwframe+0x77/0x7f
>
> [...]
I've taken some security-related hfsplus stuff before, so:
Applied to for-next/hardening, thanks!
[1/1] hfsplus: fix uninit-value in copy_name
https://git.kernel.org/kees/c/974a00974829
Take care,
--
Kees Cook
next prev parent reply other threads:[~2024-07-05 21:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-18 9:21 [syzbot] [hfs?] KMSAN: " syzbot
2024-05-21 0:40 ` Edward Adam Davis
2024-05-21 3:10 ` syzbot
2024-05-21 3:45 ` Edward Adam Davis
2024-05-21 4:21 ` syzbot
2024-05-21 5:21 ` [PATCH] hfsplus: fix " Edward Adam Davis
2024-07-04 13:36 ` Dmitry Vyukov
2024-07-05 13:46 ` Edward Adam Davis
2024-07-05 21:20 ` Kees Cook [this message]
2024-07-06 7:20 ` Christian Brauner
2024-07-08 6:52 ` Dmitry Vyukov
2024-07-08 19:20 ` Kees Cook
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=172021445223.2844396.7059951310501602233.b4-ty@kernel.org \
--to=kees@kernel.org \
--cc=eadavis@qq.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+efde959319469ff8d4d7@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®