linux-kernel - Re: [PATCH] KVM: SVM: Inject #GP if memory operand for INVPCID is non-canonical

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: <174076298281.3738096.14978008039669090737.b4-ty@google.com>
Date: Fri, 28 Feb 2025 15:40:32 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>, Paolo Bonzini <pbonzini@...hat.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Babu Moger <babu.moger@....com>, Jim Mattson <jmattson@...gle.com>
Subject: Re: [PATCH] KVM: SVM: Inject #GP if memory operand for INVPCID is non-canonical

On Mon, 24 Feb 2025 09:45:22 -0800, Sean Christopherson wrote:
> Inject a #GP if the memory operand received by INVCPID is non-canonical.
> The APM clearly states that the intercept takes priority over all #GP
> checks except the CPL0 restriction.
> 
> Of course, that begs the question of how the CPU generates a linear
> address in the first place.  Tracing confirms that EXITINFO1 does hold a
> linear address, at least for 64-bit mode guests (hooray GS prefix).
> Unfortunately, the APM says absolutely nothing about the EXITINFO fields
> for INVPCID intercepts, so it's not at all clear what's supposed to
> happen.
> 
> [...]

Applied to kvm-x86 svm, thanks!

[1/1] KVM: SVM: Inject #GP if memory operand for INVPCID is non-canonical
      https://github.com/kvm-x86/linux/commit/d4b69c3d1471

--
https://github.com/kvm-x86/linux/tree/next