From: Vincent Donnefort <vdonnefort@google.com>
To: Sebastian Ott <sebott@redhat.com>
Cc: Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
Quentin Perret <qperret@google.com>,
Fuad Tabba <tabba@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Mark Brown <broonie@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] KVM: arm64: Fix uninitialized memcache pointer in user_mem_abort()
Date: Tue, 6 May 2025 11:36:35 +0100 [thread overview]
Message-ID: <aBnmM7DSonZr_VHC@google.com> (raw)
In-Reply-To: <20250505173148.33900-1-sebott@redhat.com>
On Mon, May 05, 2025 at 07:31:48PM +0200, Sebastian Ott wrote:
> Commit fce886a60207 ("KVM: arm64: Plumb the pKVM MMU in KVM") made the
> initialization of the local memcache variable in user_mem_abort()
> conditional, leaving a codepath where it is used uninitialized via
> kvm_pgtable_stage2_map().
>
> This can fail on any path that requires a stage-2 allocation
> without transition via a permission fault or dirty logging.
>
> Fix this by making sure that memcache is always valid.
>
> Fixes: fce886a60207 ("KVM: arm64: Plumb the pKVM MMU in KVM")
> Signed-off-by: Sebastian Ott <sebott@redhat.com>
> Reviewed-by: Marc Zyngier <maz@kernel.org>
> Cc: stable@vger.kernel.org
> Link: https://lore.kernel.org/kvmarm/3f5db4c7-ccce-fb95-595c-692fa7aad227@redhat.com/
> ---
> arch/arm64/kvm/mmu.c | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm64/kvm/mmu.c b/arch/arm64/kvm/mmu.c
> index 754f2fe0cc67..eeda92330ade 100644
> --- a/arch/arm64/kvm/mmu.c
> +++ b/arch/arm64/kvm/mmu.c
> @@ -1501,6 +1501,11 @@ static int user_mem_abort(struct kvm_vcpu *vcpu, phys_addr_t fault_ipa,
> return -EFAULT;
> }
>
> + if (!is_protected_kvm_enabled())
> + memcache = &vcpu->arch.mmu_page_cache;
> + else
> + memcache = &vcpu->arch.pkvm_memcache;
> +
> /*
> * Permission faults just need to update the existing leaf entry,
> * and so normally don't require allocations from the memcache. The
> @@ -1510,13 +1515,11 @@ static int user_mem_abort(struct kvm_vcpu *vcpu, phys_addr_t fault_ipa,
> if (!fault_is_perm || (logging_active && write_fault)) {
> int min_pages = kvm_mmu_cache_min_pages(vcpu->arch.hw_mmu);
>
> - if (!is_protected_kvm_enabled()) {
> - memcache = &vcpu->arch.mmu_page_cache;
> + if (!is_protected_kvm_enabled())
> ret = kvm_mmu_topup_memory_cache(memcache, min_pages);
> - } else {
> - memcache = &vcpu->arch.pkvm_memcache;
> + else
> ret = topup_hyp_memcache(memcache, min_pages);
> - }
> +
> if (ret)
> return ret;
> }
>
> base-commit: 92a09c47464d040866cf2b4cd052bc60555185fb
> --
> 2.49.0
>
>
For the pKVM part
Reviewed-by: Vincent Donnefort <vdonnefort@google.com>
Thanks
next prev parent reply other threads:[~2025-05-06 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 17:31 [PATCH] KVM: arm64: Fix uninitialized memcache pointer in user_mem_abort() Sebastian Ott
2025-05-06 10:36 ` Vincent Donnefort [this message]
2025-05-07 7:56 ` Oliver Upton
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=aBnmM7DSonZr_VHC@google.com \
--to=vdonnefort@google.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=qperret@google.com \
--cc=sebott@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tabba@google.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).