linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: syzbot <syzbot+89a42836ac72e6a02d35@syzkaller.appspotmail.com>
Cc: christoffer.dall@arm.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, maz@kernel.org,
	pbonzini@redhat.com, peterx@redhat.com,
	syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: slab-out-of-bounds Read in kvm_vcpu_gfn_to_memslot
Date: Tue, 7 Apr 2020 18:09:05 -0700	[thread overview]
Message-ID: <20200408010905.GC9715@linux.intel.com> (raw)
In-Reply-To: <000000000000fca9a205a2b90dd6@google.com>

On Tue, Apr 07, 2020 at 01:16:10PM -0700, syzbot wrote:
> Hello,
> 
> syzbot found the following crash on:
> 
> HEAD commit:    bef7b2a7 Merge tag 'devicetree-for-5.7' of git://git.kerne..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=15ce12cde00000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=91b674b8f0368e69
> dashboard link: https://syzkaller.appspot.com/bug?extid=89a42836ac72e6a02d35
> compiler:       gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14c69db7e00000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=17b8b02be00000
> 
> The bug was bisected to:
> 
> commit 36947254e5f981aeeedab1c7dfa35fc34d330e80
> Author: Sean Christopherson <sean.j.christopherson@intel.com>
> Date:   Tue Feb 18 21:07:32 2020 +0000
> 
>     KVM: Dynamically size memslot array based on number of used slots
> 
> bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=15f1b1fbe00000
> final crash:    https://syzkaller.appspot.com/x/report.txt?x=17f1b1fbe00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=13f1b1fbe00000
> 
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+89a42836ac72e6a02d35@syzkaller.appspotmail.com
> Fixes: 36947254e5f9 ("KVM: Dynamically size memslot array based on number of used slots")

#syz dup: KASAN: slab-out-of-bounds Read in __kvm_gfn_to_hva_cache_init

      reply	other threads:[~2020-04-08  1:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07 20:16 KASAN: slab-out-of-bounds Read in kvm_vcpu_gfn_to_memslot syzbot
2020-04-08  1:09 ` 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=20200408010905.GC9715@linux.intel.com \
    --to=sean.j.christopherson@intel.com \
    --cc=christoffer.dall@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=syzbot+89a42836ac72e6a02d35@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;
as well as URLs for NNTP newsgroup(s).