linux-kernel - Re: [PATCH] KVM: VMX: Always reflect SGX EPCM #PFs back into the guest

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: <176823901501.1371726.15879387751613608587.b4-ty@google.com>
Date: Mon, 12 Jan 2026 09:39:04 -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, 
	Kai Huang <kai.huang@...el.com>
Subject: Re: [PATCH] KVM: VMX: Always reflect SGX EPCM #PFs back into the guest

On Fri, 21 Nov 2025 14:20:18 -0800, Sean Christopherson wrote:
> When handling intercepted #PFs, reflect EPCM (Enclave Page Cache Map)
> violations, i.e. #PFs with the SGX flag set, back into the guest.  KVM
> doesn't shadow EPCM entries (the EPCM deals only with virtual/linear
> addresses), and so EPCM violation cannot be due to KVM interference,
> and more importantly can't be resolved by KVM.
> 
> On pre-SGX2 hardware, EPCM violations are delivered as #GP(0) faults, but
> on SGX2+ hardware, they are delivered as #PF(SGX).  Failure to account for
> the SGX2 behavior could put a vCPU into an infinite loop due to KVM not
> realizing the #PF is the guest's responsibility.
> 
> [...]

Applied to kvm-x86 vmx, thanks!

[1/1] KVM: VMX: Always reflect SGX EPCM #PFs back into the guest
      https://github.com/kvm-x86/linux/commit/ff8071eb3aa5

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