From: Sean Christopherson <seanjc@google.com>
To: syzbot <syzbot+8cdd16fd5a6c0565e227@syzkaller.appspotmail.com>
Cc: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, pbonzini@redhat.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org
Subject: Re: [syzbot] BUG: unable to handle kernel paging request in vmx_handle_exit_irqoff
Date: Thu, 3 Nov 2022 18:42:24 +0000 [thread overview]
Message-ID: <Y2QLkI7Jqj8lNnlj@google.com> (raw)
In-Reply-To: <0000000000004d244705ec88228c@google.com>
On Wed, Nov 02, 2022, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: 61c3426aca2c Add linux-next specific files for 20221102
> git tree: linux-next
> console+strace: https://syzkaller.appspot.com/x/log.txt?x=13596541880000
> kernel config: https://syzkaller.appspot.com/x/.config?x=acb529cc910d907c
> dashboard link: https://syzkaller.appspot.com/bug?extid=8cdd16fd5a6c0565e227
> compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17d036de880000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11d5e00a880000
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/cc56d88dd6a3/disk-61c3426a.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/5921b65b080f/vmlinux-61c3426a.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/39cbd355fedd/bzImage-61c3426a.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+8cdd16fd5a6c0565e227@syzkaller.appspotmail.com
>
> BUG: unable to handle page fault for address: fffffbc0000001d8
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> PGD 23ffe4067 P4D 23ffe4067 PUD 0
> Oops: 0000 [#1] PREEMPT SMP KASAN
> CPU: 0 PID: 5404 Comm: syz-executor526 Not tainted 6.1.0-rc3-next-20221102-syzkaller #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
> RIP: 0010:gate_offset arch/x86/include/asm/desc_defs.h:100 [inline]
Looks like a KASAN bug, the KVM side of things looks ok and that code hasn't been
touched in quite some time. The actual explosion is in kasan_check_range(), not
KVM code.
I'll bisect, this repros very quickly for me.
prev parent reply other threads:[~2022-11-03 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 16:19 [syzbot] BUG: unable to handle kernel paging request in vmx_handle_exit_irqoff syzbot
2022-11-03 2:58 ` syzbot
2022-11-03 18:42 ` Sean Christopherson [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=Y2QLkI7Jqj8lNnlj@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=syzbot+8cdd16fd5a6c0565e227@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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