mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: "Gustavo A. R. Silva" <gustavo@embeddedor.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Christoffer Dall <christoffer.dall@arm.com>,
	Will Deacon <will.deacon@arm.com>
Cc: kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: arm/arm64: vgic: fix off-by-one bug in vgic_get_irq()
Date: Thu, 13 Dec 2018 10:52:52 +0000	[thread overview]
Message-ID: <d01370b0-5b80-b537-3168-88c166a17e7e@arm.com> (raw)
In-Reply-To: <20181212201123.GA26674@embeddedor>

Hi Gustavo,

On 12/12/2018 20:11, Gustavo A. R. Silva wrote:
> When using the nospec API, it should be taken into account that:
> 
> "...if the CPU speculates past the bounds check then
>  * array_index_nospec() will clamp the index within the range of [0,
>  * size)."
> 
> The above is part of the header for macro array_index_nospec() in
> linux/nospec.h
> 
> Now, in this particular case, if intid evaluates to exactly VGIC_MAX_SPI
> or to exaclty VGIC_MAX_PRIVATE, the array_index_nospec() macro ends up
> returning VGIC_MAX_SPI - 1 or VGIC_MAX_PRIVATE - 1 respectively, instead
> of VGIC_MAX_SPI or VGIC_MAX_PRIVATE, which, based on the original logic:
> 
> 	/* SGIs and PPIs */
> 	if (intid <= VGIC_MAX_PRIVATE)
>  		return &vcpu->arch.vgic_cpu.private_irqs[intid];
> 
>  	/* SPIs */
> 	if (intid <= VGIC_MAX_SPI)
>  		return &kvm->arch.vgic.spis[intid - VGIC_NR_PRIVATE_IRQS];
> 
> are valid values for intid.
> 
> Fix this by calling array_index_nospec() macro with VGIC_MAX_PRIVATE + 1
> and VGIC_MAX_SPI + 1 as arguments for its parameter size.
> 
> Fixes: 41b87599c743 ("KVM: arm/arm64: vgic: fix possible spectre-v1 in vgic_get_irq()")
> Cc: stable@vger.kernel.org
> Signed-off-by: Gustavo A. R. Silva <gustavo@embeddedor.com>
> ---
>  virt/kvm/arm/vgic/vgic.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/virt/kvm/arm/vgic/vgic.c b/virt/kvm/arm/vgic/vgic.c
> index 50e25438fb3c..5db40696055a 100644
> --- a/virt/kvm/arm/vgic/vgic.c
> +++ b/virt/kvm/arm/vgic/vgic.c
> @@ -103,13 +103,13 @@ struct vgic_irq *vgic_get_irq(struct kvm *kvm, struct kvm_vcpu *vcpu,
>  {
>  	/* SGIs and PPIs */
>  	if (intid <= VGIC_MAX_PRIVATE) {
> -		intid = array_index_nospec(intid, VGIC_MAX_PRIVATE);
> +		intid = array_index_nospec(intid, VGIC_MAX_PRIVATE + 1);
>  		return &vcpu->arch.vgic_cpu.private_irqs[intid];
>  	}
>  
>  	/* SPIs */
>  	if (intid <= VGIC_MAX_SPI) {
> -		intid = array_index_nospec(intid, VGIC_MAX_SPI);
> +		intid = array_index_nospec(intid, VGIC_MAX_SPI + 1);
>  		return &kvm->arch.vgic.spis[intid - VGIC_NR_PRIVATE_IRQS];
>  	}
>  
> 

That's a good one. Out of curiosity, how did you find it?

Thanks,
	
	M.
-- 
Jazz is not dead. It just smells funny...

      reply	other threads:[~2018-12-13 10:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12 20:11 Gustavo A. R. Silva
2018-12-13 10:52 ` Marc Zyngier [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=d01370b0-5b80-b537-3168-88c166a17e7e@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=christoffer.dall@arm.com \
    --cc=gustavo@embeddedor.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=will.deacon@arm.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®