From: syzbot <syzbot+541e21dcc32c4046cba9@syzkaller.appspotmail.com>
To: glider@google.com, jmorris@namei.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, paul@paul-moore.com,
penguin-kernel@I-love.SAKURA.ne.jp, serge@hallyn.com,
syzkaller-bugs@googlegroups.com, takedakn@nttdata.co.jp
Subject: [syzbot] KMSAN: uninit-value in tomoyo_path_chown
Date: Mon, 19 Sep 2022 01:10:35 -0700 [thread overview]
Message-ID: <00000000000008058305e9033f85@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 3a2b6b904ea7 x86: kmsan: enable KMSAN builds for x86
git tree: https://github.com/google/kmsan.git master
console+strace: https://syzkaller.appspot.com/x/log.txt?x=13719145080000
kernel config: https://syzkaller.appspot.com/x/.config?x=8e64bc5364a1307e
dashboard link: https://syzkaller.appspot.com/bug?extid=541e21dcc32c4046cba9
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project.git 610139d2d9ce6746b3c617fb3e2f7886272d26ff), GNU ld (GNU Binutils for Debian) 2.35.2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10cac995080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16816c33080000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+541e21dcc32c4046cba9@syzkaller.appspotmail.com
=====================================================
BUG: KMSAN: uninit-value in tomoyo_path_chown+0x121/0x240 security/tomoyo/tomoyo.c:366
tomoyo_path_chown+0x121/0x240 security/tomoyo/tomoyo.c:366
security_path_chown+0x17d/0x260 security/security.c:1224
chown_common+0x9f2/0xef0 fs/open.c:729
vfs_fchown fs/open.c:802 [inline]
ksys_fchown+0x229/0x360 fs/open.c:813
__do_sys_fchown fs/open.c:821 [inline]
__se_sys_fchown fs/open.c:819 [inline]
__x64_sys_fchown+0x8a/0xe0 fs/open.c:819
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
Local variable newattrs created at:
chown_common+0xd1/0xef0 fs/open.c:708
vfs_fchown fs/open.c:802 [inline]
ksys_fchown+0x229/0x360 fs/open.c:813
CPU: 0 PID: 3490 Comm: syz-executor426 Not tainted 6.0.0-rc2-syzkaller-47460-g3a2b6b904ea7 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/22/2022
=====================================================
---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
next reply other threads:[~2022-09-19 8:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 8:10 syzbot [this message]
2022-09-19 11:05 ` [PATCH (urgent)] vfs: fix uninitialized uid/gid in chown_common() Tetsuo Handa
2022-09-19 15:12 ` Christian Brauner
2022-09-19 15:14 ` Christian Brauner
2022-09-19 23:41 ` Serge E. Hallyn
2022-09-20 0:25 ` Seth Forshee
2022-09-20 0:29 ` Seth Forshee
2022-09-20 0:45 ` Tetsuo Handa
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=00000000000008058305e9033f85@google.com \
--to=syzbot+541e21dcc32c4046cba9@syzkaller.appspotmail.com \
--cc=glider@google.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=serge@hallyn.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=takedakn@nttdata.co.jp \
/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;
as well as URLs for NNTP newsgroup(s).