linux-kernel - Re: [PATCH v3] KVM: arm64: Check range args for pKVM mem transitions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <176184141215.2037781.15285129673531696378.b4-ty@kernel.org>
Date: Thu, 30 Oct 2025 16:23:32 +0000
From: Marc Zyngier <maz@...nel.org>
To: oliver.upton@...ux.dev,
	joey.gouly@....com,
	suzuki.poulose@....com,
	yuzenghui@...wei.com,
	catalin.marinas@....com,
	will@...nel.org,
	Vincent Donnefort <vdonnefort@...gle.com>
Cc: qperret@...gle.com,
	sebastianene@...gle.com,
	keirf@...gle.com,
	linux-arm-kernel@...ts.infradead.org,
	kvmarm@...ts.linux.dev,
	linux-kernel@...r.kernel.org,
	kernel-team@...roid.com
Subject: Re: [PATCH v3] KVM: arm64: Check range args for pKVM mem transitions

On Thu, 16 Oct 2025 17:45:41 +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.
> 
> [...]

Applied to fixes, thanks!

[1/1] KVM: arm64: Check range args for pKVM mem transitions
      commit: f71f7afd0a0cd3f044cd2f8aba71a1a7229df762

Cheers,

	M.
-- 
Without deviation from the norm, progress is not possible.