From: Pavel Skripkin <paskripkin@gmail.com>
To: syzbot <syzbot+cdbd40e0c3ca02cae3b7@syzkaller.appspotmail.com>,
andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
daniel@iogearbox.net, davem@davemloft.net, glider@google.com,
john.fastabend@gmail.com, kafai@fb.com, kpsingh@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yhs@fb.com
Subject: Re: [syzbot] KMSAN: kernel-infoleak in move_addr_to_user (6)
Date: Tue, 21 Dec 2021 23:33:24 +0300 [thread overview]
Message-ID: <24253b93-66f0-15b7-a3b1-f1ffacb86116@gmail.com> (raw)
In-Reply-To: <000000000000a8a64205d39672b8@google.com>
On 12/20/21 19:33, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: b0a8b5053e8b kmsan: core: add dependency on DEBUG_KERNEL
> git tree: https://github.com/google/kmsan.git master
> console output: https://syzkaller.appspot.com/x/log.txt?x=14a45071b00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=46a956fc7a887c60
> dashboard link: https://syzkaller.appspot.com/bug?extid=cdbd40e0c3ca02cae3b7
> compiler: clang version 14.0.0 (/usr/local/google/src/llvm-git-monorepo 2b554920f11c8b763cd9ed9003f4e19b919b8e1f), GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1343f443b00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16efa493b00000
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+cdbd40e0c3ca02cae3b7@syzkaller.appspotmail.com
>
Looks like missing memset(0). tipc_nametbl_lookup_anycast() may return
before initializing sk.ref
> * On exit:
> *
> * - If lookup is deferred to another node, leave 'sk->node' unchanged and
> * return 'true'.
And then sk.ref is passed to msg_set_destport().
There is also one more place with similar possible uninit-value in
tipc_msg_lookup_dest().
With regards,
Pavel Skripkin
prev parent reply other threads:[~2021-12-21 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 16:33 [syzbot] KMSAN: kernel-infoleak in move_addr_to_user (6) syzbot
2021-12-21 20:33 ` Pavel Skripkin [this message]
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=24253b93-66f0-15b7-a3b1-f1ffacb86116@gmail.com \
--to=paskripkin@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=glider@google.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzbot+cdbd40e0c3ca02cae3b7@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).