mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+9b9124ae9b12d5af5d95@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] KMSAN: kernel-infoleak in vmci_host_unlocked_ioctl (3)
Date: Mon, 23 Jun 2025 02:28:02 -0700	[thread overview]
Message-ID: <68591e22.a00a0220.34b642.0006.GAE@google.com> (raw)
In-Reply-To: <20250623085022.3182174-1-lizhi.xu@windriver.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
KMSAN: kernel-infoleak in vmci_host_unlocked_ioctl

=====================================================
BUG: KMSAN: kernel-infoleak in instrument_copy_to_user include/linux/instrumented.h:114 [inline]
BUG: KMSAN: kernel-infoleak in _inline_copy_to_user include/linux/uaccess.h:196 [inline]
BUG: KMSAN: kernel-infoleak in _copy_to_user+0xcc/0x120 lib/usercopy.c:26
 instrument_copy_to_user include/linux/instrumented.h:114 [inline]
 _inline_copy_to_user include/linux/uaccess.h:196 [inline]
 _copy_to_user+0xcc/0x120 lib/usercopy.c:26
 copy_to_user include/linux/uaccess.h:225 [inline]
 vmci_host_do_receive_datagram drivers/misc/vmw_vmci/vmci_host.c:442 [inline]
 vmci_host_unlocked_ioctl+0x1d6f/0x52d0 drivers/misc/vmw_vmci/vmci_host.c:942
 vfs_ioctl fs/ioctl.c:51 [inline]
 __do_sys_ioctl fs/ioctl.c:907 [inline]
 __se_sys_ioctl+0x239/0x400 fs/ioctl.c:893
 __x64_sys_ioctl+0x97/0xe0 fs/ioctl.c:893
 x64_sys_call+0x1ebe/0x3db0 arch/x86/include/generated/asm/syscalls_64.h:17
 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

Local variable filename created at:
 ima_file_mprotect+0x78/0x800 security/integrity/ima/ima_main.c:500
 security_file_mprotect+0x141/0x590 security/security.c:3012

Bytes 28-31 of 40 are uninitialized
Memory access of size 40 starts at ffff888021ad2880
Data copied to user address 000000000000a4bf

CPU: 1 UID: 0 PID: 6749 Comm: syz.0.16 Not tainted 6.16.0-rc3-syzkaller-g86731a2a651e-dirty #0 PREEMPT(undef) 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
=====================================================


Tested on:

commit:         86731a2a Linux 6.16-rc3
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=112fdb0c580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=595d344ff0b23ac5
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
patch:          https://syzkaller.appspot.com/x/patch.diff?x=16bff370580000


       reply	other threads:[~2025-06-23  9:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250623085022.3182174-1-lizhi.xu@windriver.com>
2025-06-23  9:28 ` syzbot [this message]
     [not found] <20250703080919.1229530-1-lizhi.xu@windriver.com>
2025-07-03 10:12 ` syzbot
     [not found] <20250627051303.2837086-1-lizhi.xu@windriver.com>
2025-06-27  5:44 ` syzbot
     [not found] <20250627032632.2470249-1-lizhi.xu@windriver.com>
2025-06-27  4:54 ` syzbot
     [not found] <20250626024902.2942685-1-lizhi.xu@windriver.com>
2025-06-26  4:45 ` syzbot
     [not found] <20250626021712.2842722-1-lizhi.xu@windriver.com>
2025-06-26  3:35 ` syzbot
     [not found] <20250623094537.3353300-1-lizhi.xu@windriver.com>
2025-06-23 12:11 ` syzbot
     [not found] <20250623080347.3056823-1-lizhi.xu@windriver.com>
2025-06-23  8:36 ` syzbot
     [not found] <20250623030312.2337101-1-lizhi.xu@windriver.com>
2025-06-23  4:28 ` syzbot
     [not found] <20250620065432.1558000-1-lizhi.xu@windriver.com>
2025-06-20 10:02 ` syzbot
     [not found] <20250620065230.1552640-1-lizhi.xu@windriver.com>
2025-06-20  8:49 ` syzbot
     [not found] <20250620052310.1280771-1-lizhi.xu@windriver.com>
2025-06-20  5:58 ` syzbot
     [not found] <20250620042056.1099990-1-lizhi.xu@windriver.com>
2025-06-20  4:28 ` syzbot
     [not found] <20250620010300.3380487-1-lizhi.xu@windriver.com>
2025-06-20  2:55 ` syzbot
2025-06-19 23:57 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
2025-06-22  7:32   ` syzbot
2025-06-23 12:29 ` Edward Adam Davis
2025-06-23 13:45   ` 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=68591e22.a00a0220.34b642.0006.GAE@google.com \
    --to=syzbot+9b9124ae9b12d5af5d95@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhi.xu@windriver.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®