From: Paolo Bonzini <pbonzini@redhat.com>
To: Liu Jing <liujing@cmss.chinamobile.com>, mpe@ellerman.id.au
Cc: npiggin@gmail.com, christophe.leroy@csgroup.eu,
naveen@kernel.org, maddy@linux.ibm.com,
linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: Array access out of bounds
Date: Wed, 23 Oct 2024 14:58:34 +0200 [thread overview]
Message-ID: <cd69f611-6478-4df6-907e-433ac559a20a@redhat.com> (raw)
In-Reply-To: <20241023120111.3973-1-liujing@cmss.chinamobile.com>
On 10/23/24 14:01, Liu Jing wrote:
> In the kvmppc_mmu_book3s_64_xlate function,
> r = be64_to_cpu(pteg[i+1]); i used is 16 after the last loop and adding 1 will cross the line.
>
> Signed-off-by: Liu Jing <liujing@cmss.chinamobile.com>
>
> diff --git a/arch/powerpc/kvm/book3s_64_mmu.c b/arch/powerpc/kvm/book3s_64_mmu.c
> index 61290282fd9e..75d2b284c4b4 100644
> --- a/arch/powerpc/kvm/book3s_64_mmu.c
> +++ b/arch/powerpc/kvm/book3s_64_mmu.c
> @@ -284,11 +284,16 @@ static int kvmppc_mmu_book3s_64_xlate(struct kvm_vcpu *vcpu, gva_t eaddr,
> second = true;
> goto do_second;
> }
> + if (i < 14) {
This should be i <= 14 (not "<"). And in fact, if you get here you must
have found == true, and therefore i is indeed <= 14. The code right
above is this:
if (!found) {
if (second)
goto no_page_found;
v_val |= HPTE_V_SECONDARY;
second = true;
goto do_second;
}
and "found = true" is set just before a break statement.
Paolo
> + r = be64_to_cpu(pteg[i+1]);
> + pp = (r & HPTE_R_PP) | key;
> + if (r & HPTE_R_PP0)
> + pp |= 8;
> + } else {
> + dprintk("KVM: Index out of bounds!\n");
> + goto no_page_found;
> + }
>
> - r = be64_to_cpu(pteg[i+1]);
> - pp = (r & HPTE_R_PP) | key;
> - if (r & HPTE_R_PP0)
> - pp |= 8;
>
> gpte->eaddr = eaddr;
> gpte->vpage = kvmppc_mmu_book3s_64_ea_to_vp(vcpu, eaddr, data);
prev parent reply other threads:[~2024-10-23 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 12:01 Liu Jing
2024-10-23 12:58 ` Paolo Bonzini [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=cd69f611-6478-4df6-907e-433ac559a20a@redhat.com \
--to=pbonzini@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liujing@cmss.chinamobile.com \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=npiggin@gmail.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®