From: Vincent Donnefort <vdonnefort@google.com>
To: Sebastian Ene <sebastianene@google.com>
Cc: maz@kernel.org, oliver.upton@linux.dev, joey.gouly@arm.com,
suzuki.poulose@arm.com, yuzenghui@huawei.com,
catalin.marinas@arm.com, will@kernel.org, qperret@google.com,
keirf@google.com, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.linux.dev, linux-kernel@vger.kernel.org,
kernel-team@android.com
Subject: Re: [PATCH v3] KVM: arm64: Check range args for pKVM mem transitions
Date: Thu, 30 Oct 2025 15:54:21 +0000 [thread overview]
Message-ID: <aQOKLaCKUDcqIZeM@google.com> (raw)
In-Reply-To: <aQMBG0SUlNWuQQFZ@google.com>
On Thu, Oct 30, 2025 at 06:09:31AM +0000, Sebastian Ene wrote:
> On Thu, Oct 16, 2025 at 05:45:41PM +0100, Vincent Donnefort wrote:
> > There's currently no verification for host issued ranges in most of the
> > pKVM memory transitions. The end boundary might therefore be subject to
> > overflow and later checks could be evaded.
> >
> > Close this loophole with an additional pfn_range_is_valid() check on a
> > per public function basis. Once this check has passed, it is safe to
> > convert pfn and nr_pages into a phys_addr_t and a size.
> >
> > host_unshare_guest transition is already protected via
> > __check_host_shared_guest(), while assert_host_shared_guest() callers
> > are already ignoring host checks.
> >
> > Signed-off-by: Vincent Donnefort <vdonnefort@google.com>
> >
> > ---
> >
> > v2 -> v3:
> > * Test range against PA-range and make the func phys specific.
> >
> > v1 -> v2:
> > * Also check for (nr_pages * PAGE_SIZE) overflow. (Quentin)
> > * Rename to check_range_args().
> >
> > diff --git a/arch/arm64/kvm/hyp/nvhe/mem_protect.c b/arch/arm64/kvm/hyp/nvhe/mem_protect.c
> > index ddc8beb55eee..49db32f3ddf7 100644
> > --- a/arch/arm64/kvm/hyp/nvhe/mem_protect.c
> > +++ b/arch/arm64/kvm/hyp/nvhe/mem_protect.c
> > @@ -367,6 +367,19 @@ static int host_stage2_unmap_dev_all(void)
> > return kvm_pgtable_stage2_unmap(pgt, addr, BIT(pgt->ia_bits) - addr);
> > }
>
> Hello Vincent,
>
> >
> > +/*
> > + * Ensure the PFN range is contained within PA-range.
> > + *
> > + * This check is also robust to overflows and is therefore a requirement before
> > + * using a pfn/nr_pages pair from an untrusted source.
> > + */
> > +static bool pfn_range_is_valid(u64 pfn, u64 nr_pages)
> > +{
> > + u64 limit = BIT(kvm_phys_shift(&host_mmu.arch.mmu) - PAGE_SHIFT);
> > +
> > + return pfn < limit && ((limit - pfn) >= nr_pages);
> > +}
> > +
>
> This newly introduced function is probably fine to be called without the host lock held as long
> as no one modifies the vtcr field from the host.mmu structure. While
> searching I couldn't find a place where this is directly modified so
> this is probably fine.
>
> > struct kvm_mem_range {
> > u64 start;
> > u64 end;
> > @@ -776,6 +789,9 @@ int __pkvm_host_donate_hyp(u64 pfn, u64 nr_pages)
> > void *virt = __hyp_va(phys);
> > int ret;
> >
> > + if (!pfn_range_is_valid(pfn, nr_pages))
> > + return -EINVAL;
> > +
> > host_lock_component();
> > hyp_lock_component();
> >
> > @@ -804,6 +820,9 @@ int __pkvm_hyp_donate_host(u64 pfn, u64 nr_pages)
> > u64 virt = (u64)__hyp_va(phys);
> > int ret;
> >
> > + if (!pfn_range_is_valid(pfn, nr_pages))
> > + return -EINVAL;
> > +
> > host_lock_component();
> > hyp_lock_component();
> >
> > @@ -887,6 +906,9 @@ int __pkvm_host_share_ffa(u64 pfn, u64 nr_pages)
> > u64 size = PAGE_SIZE * nr_pages;
> > int ret;
> >
> > + if (!pfn_range_is_valid(pfn, nr_pages))
> > + return -EINVAL;
> > +
> > host_lock_component();
> > ret = __host_check_page_state_range(phys, size, PKVM_PAGE_OWNED);
> > if (!ret)
> > @@ -902,6 +924,9 @@ int __pkvm_host_unshare_ffa(u64 pfn, u64 nr_pages)
> > u64 size = PAGE_SIZE * nr_pages;
> > int ret;
> >
> > + if (!pfn_range_is_valid(pfn, nr_pages))
> > + return -EINVAL;
> > +
> > host_lock_component();
> > ret = __host_check_page_state_range(phys, size, PKVM_PAGE_SHARED_OWNED);
> > if (!ret)
> > @@ -945,6 +970,9 @@ int __pkvm_host_share_guest(u64 pfn, u64 gfn, u64 nr_pages, struct pkvm_hyp_vcpu
> > if (prot & ~KVM_PGTABLE_PROT_RWX)
> > return -EINVAL;
> >
> > + if (!pfn_range_is_valid(pfn, nr_pages))
> > + return -EINVAL;
> > +
>
> I think we don't need it here because __pkvm_host_share_guest has the
> __guest_check_transition_size verification in place which limits
> nr_pages.
__guest_check_transition size will only limit to PMD_SIZE, which can be quite a
big number if you consider > 4KiB pages systems. So I believe this is still a loophole
worth fixing.
>
> > ret = __guest_check_transition_size(phys, ipa, nr_pages, &size);
> > if (ret)
> > return ret;
> >
> > base-commit: 7ea30958b3054f5e488fa0b33c352723f7ab3a2a
> > --
> > 2.51.0.869.ge66316f041-goog
> >
>
> Other than that this looks good, thanks
> Sebastian
Thanks for having a look at the patch.
next prev parent reply other threads:[~2025-10-30 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 16:45 [PATCH v3] KVM: arm64: Check range args for pKVM mem transitions Vincent Donnefort
2025-10-30 6:09 ` Sebastian Ene
2025-10-30 15:54 ` Vincent Donnefort [this message]
2025-10-30 16:23 ` Marc Zyngier
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=aQOKLaCKUDcqIZeM@google.com \
--to=vdonnefort@google.com \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=keirf@google.com \
--cc=kernel-team@android.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=qperret@google.com \
--cc=sebastianene@google.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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).