From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>,
Janosch Frank <frankja@linux.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: David Hildenbrand <david@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+d889b59b2bb87d4047a2@syzkaller.appspotmail.com
Subject: Re: [PATCH 0/2] KVM: Fix out-of-bounds memslot access
Date: Wed, 8 Apr 2020 09:24:27 +0200 [thread overview]
Message-ID: <526247ac-4201-8b3d-0f15-d93b12a530b8@de.ibm.com> (raw)
In-Reply-To: <20200408064059.8957-1-sean.j.christopherson@intel.com>
On 08.04.20 08:40, Sean Christopherson wrote:
> Two fixes for what are effectively the same bug. The binary search used
> for memslot lookup doesn't check the resolved index and can access memory
> beyond the end of the memslot array.
>
> I split the s390 specific change to a separate patch because it's subtly
> different, and to simplify backporting. The KVM wide fix can be applied
> to stable trees as is, but AFAICT the s390 change would need to be paired
> with the !used_slots check from commit 774a964ef56 ("KVM: Fix out of range
I cannot find the commit id 774a964ef56
next prev parent reply other threads:[~2020-04-08 7:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 6:40 [PATCH 0/2] KVM: Fix out-of-bounds memslot access Sean Christopherson
2020-04-08 6:40 ` [PATCH 1/2] KVM: Check validity of resolved slot when searching memslots Sean Christopherson
2020-04-08 7:04 ` Cornelia Huck
2020-04-08 6:40 ` [PATCH 2/2] KVM: s390: Return last valid slot if approx index is out-of-bounds Sean Christopherson
2020-04-08 7:10 ` Cornelia Huck
2020-04-08 9:08 ` Paolo Bonzini
2020-04-08 7:28 ` Christian Borntraeger
2020-04-08 10:21 ` Claudio Imbrenda
2020-04-08 11:33 ` Paolo Bonzini
2020-04-08 11:40 ` Christian Borntraeger
2020-04-08 6:55 ` [PATCH 0/2] KVM: Fix out-of-bounds memslot access Christian Borntraeger
2020-04-08 7:24 ` Christian Borntraeger [this message]
2020-04-08 8:10 ` Cornelia Huck
2020-04-08 14:23 ` Sean Christopherson
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=526247ac-4201-8b3d-0f15-d93b12a530b8@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=sean.j.christopherson@intel.com \
--cc=syzbot+d889b59b2bb87d4047a2@syzkaller.appspotmail.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).