From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+9b9124ae9b12d5af5d95@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] KMSAN: kernel-infoleak in vmci_host_unlocked_ioctl (3)
Date: Sun, 22 Jun 2025 14:28:43 +0800 [thread overview]
Message-ID: <20250622062844.1505-1-hdanton@sina.com> (raw)
In-Reply-To: <6854a3e6.a00a0220.137b3.0022.GAE@google.com>
On Thu, 19 Jun 2025 16:57:26 -0700
> syzbot found the following issue on:
>
> HEAD commit: 08215f5486ec Merge tag 'kbuild-fixes-v6.16' of git://git.k..
> git tree: upstream
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=13f7fd70580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=61539536677af51c
> dashboard link: https://syzkaller.appspot.com/bug?extid=9b9124ae9b12d5af5d95
> compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17f7fd70580000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1485690c580000
#syz test
--- x/drivers/misc/vmw_vmci/vmci_context.c
+++ y/drivers/misc/vmw_vmci/vmci_context.c
@@ -245,7 +245,7 @@ static int ctx_fire_notification(u32 con
array_size = vmci_handle_arr_get_size(subscriber_array);
for (i = 0; i < array_size; i++) {
int result;
- struct vmci_event_ctx ev;
+ struct vmci_event_ctx ev = {0};
ev.msg.hdr.dst = vmci_handle_arr_get_entry(subscriber_array, i);
ev.msg.hdr.src = vmci_make_handle(VMCI_HYPERVISOR_CONTEXT_ID,
--
next prev parent reply other threads:[~2025-06-22 6:29 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 23:57 syzbot
2025-06-20 1:03 ` [syzbot] " syzbot
2025-06-20 4:21 ` syzbot
2025-06-20 5:23 ` syzbot
2025-06-20 6:52 ` syzbot
2025-06-20 6:54 ` syzbot
2025-06-22 2:37 ` Edward Adam Davis
2025-06-22 3:02 ` syzbot
2025-06-22 4:46 ` Hillf Danton
2025-06-22 5:19 ` syzbot
2025-06-22 6:28 ` Hillf Danton [this message]
2025-06-22 7:32 ` syzbot
2025-06-23 3:03 ` [syzbot] " syzbot
2025-06-23 8:03 ` syzbot
2025-06-23 8:50 ` syzbot
2025-06-23 9:45 ` syzbot
2025-06-23 12:29 ` Edward Adam Davis
2025-06-23 13:45 ` syzbot
2025-06-26 2:17 ` [syzbot] " syzbot
2025-06-26 2:49 ` syzbot
2025-06-27 3:26 ` syzbot
2025-06-27 5:13 ` syzbot
2025-06-27 5:52 ` [PATCH] vmci: Prevent the dispatching of uninitialized payloads Lizhi Xu
2025-07-03 7:53 ` [PATCH V2] " Lizhi Xu
2025-07-03 8:09 ` [syzbot] Re: [syzbot] [kernel?] KMSAN: kernel-infoleak in vmci_host_unlocked_ioctl (3) syzbot
[not found] <20250620010300.3380487-1-lizhi.xu@windriver.com>
2025-06-20 2:55 ` syzbot
[not found] <20250620042056.1099990-1-lizhi.xu@windriver.com>
2025-06-20 4:28 ` syzbot
[not found] <20250620052310.1280771-1-lizhi.xu@windriver.com>
2025-06-20 5:58 ` syzbot
[not found] <20250620065230.1552640-1-lizhi.xu@windriver.com>
2025-06-20 8:49 ` syzbot
[not found] <20250620065432.1558000-1-lizhi.xu@windriver.com>
2025-06-20 10:02 ` syzbot
[not found] <20250623030312.2337101-1-lizhi.xu@windriver.com>
2025-06-23 4:28 ` syzbot
[not found] <20250623080347.3056823-1-lizhi.xu@windriver.com>
2025-06-23 8:36 ` syzbot
[not found] <20250623085022.3182174-1-lizhi.xu@windriver.com>
2025-06-23 9:28 ` syzbot
[not found] <20250623094537.3353300-1-lizhi.xu@windriver.com>
2025-06-23 12:11 ` syzbot
[not found] <20250626021712.2842722-1-lizhi.xu@windriver.com>
2025-06-26 3:35 ` syzbot
[not found] <20250626024902.2942685-1-lizhi.xu@windriver.com>
2025-06-26 4:45 ` syzbot
[not found] <20250627032632.2470249-1-lizhi.xu@windriver.com>
2025-06-27 4:54 ` syzbot
[not found] <20250627051303.2837086-1-lizhi.xu@windriver.com>
2025-06-27 5:44 ` syzbot
[not found] <20250703080919.1229530-1-lizhi.xu@windriver.com>
2025-07-03 10:12 ` 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=20250622062844.1505-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+9b9124ae9b12d5af5d95@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®