From: syzbot <syzbot+d6caa905917d353f0d07@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, glider@google.com,
hpa@zytor.com, jmattson@google.com, joro@8bytes.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, pbonzini@redhat.com, seanjc@google.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
vkuznets@redhat.com, wanpengli@tencent.com, x86@kernel.org
Subject: [syzbot] KMSAN: uninit-value in kvm_irq_delivery_to_apic_fast
Date: Tue, 28 Jun 2022 04:37:24 -0700 [thread overview]
Message-ID: <000000000000d8420a05e28075ea@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 4b28366af7d9 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=126a4b60080000
kernel config: https://syzkaller.appspot.com/x/.config?x=d14e10a167d1c585
dashboard link: https://syzkaller.appspot.com/bug?extid=d6caa905917d353f0d07
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=14d596c4080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10bcf08ff00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d6caa905917d353f0d07@syzkaller.appspotmail.com
L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
=====================================================
BUG: KMSAN: uninit-value in kvm_apic_set_irq arch/x86/kvm/lapic.c:634 [inline]
BUG: KMSAN: uninit-value in kvm_irq_delivery_to_apic_fast+0x7a7/0x990 arch/x86/kvm/lapic.c:1044
kvm_apic_set_irq arch/x86/kvm/lapic.c:634 [inline]
kvm_irq_delivery_to_apic_fast+0x7a7/0x990 arch/x86/kvm/lapic.c:1044
kvm_irq_delivery_to_apic+0xdb/0xe40 arch/x86/kvm/irq_comm.c:54
kvm_pv_kick_cpu_op+0xd1/0x100 arch/x86/kvm/x86.c:9155
kvm_emulate_hypercall+0xee7/0x1340 arch/x86/kvm/x86.c:9285
__vmx_handle_exit+0x101f/0x1710 arch/x86/kvm/vmx/vmx.c:6237
vmx_handle_exit+0x38/0x1f0 arch/x86/kvm/vmx/vmx.c:6254
vcpu_enter_guest+0x4733/0x52d0 arch/x86/kvm/x86.c:10366
vcpu_run+0x794/0x1230 arch/x86/kvm/x86.c:10455
kvm_arch_vcpu_ioctl_run+0x11fe/0x1b30 arch/x86/kvm/x86.c:10659
kvm_vcpu_ioctl+0xcd4/0x1980 arch/x86/kvm/../../../virt/kvm/kvm_main.c:3948
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0x222/0x400 fs/ioctl.c:856
__x64_sys_ioctl+0x92/0xd0 fs/ioctl.c:856
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+0x46/0xb0
Local variable lapic_irq created at:
kvm_pv_kick_cpu_op+0x46/0x100 arch/x86/kvm/x86.c:9146
kvm_emulate_hypercall+0xee7/0x1340 arch/x86/kvm/x86.c:9285
CPU: 1 PID: 3490 Comm: syz-executor407 Not tainted 5.19.0-rc3-syzkaller-30868-g4b28366af7d9 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
=====================================================
---
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-06-28 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 11:37 syzbot [this message]
2022-06-28 13:01 ` [syzbot] KMSAN: uninit-value in kvm_irq_delivery_to_apic_fast Vitaly Kuznetsov
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=000000000000d8420a05e28075ea@google.com \
--to=syzbot+d6caa905917d353f0d07@syzkaller.appspotmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=glider@google.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
/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