From: Amirmohammad Eftekhar <amirmohammad.eftekhar@cispa.de>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <amirmohammad.eftekhar@cispa.de>
Subject: [PATCH] KVM: VMX: Add array_index_nospec() to evmcs_field_offset()
Date: Fri, 23 Oct 2026 19:13:07 +0200 [thread overview]
Message-ID: <20261023171307.636760-1-amirmohammad.eftekhar@cispa.de> (raw)
From: Amirmohammad Eftekhar <amirmohammad.eftekhar@cispa.de>
evmcs_field_offset() bounds-checks the guest-supplied field index against
nr_evmcs_1_fields and then indexes vmcs_field_to_evmcs_1[] with it, but,
unlike its vmcs12 counterpart get_vmcs12_field_offset(), it does not clamp
the index with array_index_nospec() after the check. The field index is
derived from a guest-supplied VMCS field encoding on the enlightened
VMREAD/VMWRITE path, so the array access can be performed speculatively
past the bounds check (Spectre v1), disclosing memory adjacent to
vmcs_field_to_evmcs_1[].
Clamp the index with array_index_nospec() immediately after the bounds
check, mirroring get_vmcs12_field_offset().
Signed-off-by: Amirmohammad Eftekhar <amirmohammad.eftekhar@cispa.de>
---
arch/x86/kvm/vmx/hyperv_evmcs.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/x86/kvm/vmx/hyperv_evmcs.h b/arch/x86/kvm/vmx/hyperv_evmcs.h
index bc08fe40590e..052b62b8ed8e 100644
--- a/arch/x86/kvm/vmx/hyperv_evmcs.h
+++ b/arch/x86/kvm/vmx/hyperv_evmcs.h
@@ -136,6 +136,8 @@ static __always_inline int evmcs_field_offset(unsigned long field,
if (unlikely(index >= nr_evmcs_1_fields))
return -ENOENT;
+ index = array_index_nospec(index, nr_evmcs_1_fields);
+
evmcs_field = &vmcs_field_to_evmcs_1[index];
/*
--
2.43.0
next reply other threads:[~2026-10-23 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 17:13 Amirmohammad Eftekhar [this message]
2026-10-24 1:17 ` Sean Christopherson
-- strict thread matches above, loose matches on Subject: below --
2026-10-17 9:30 Amirmohammad Eftekhar
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=20261023171307.636760-1-amirmohammad.eftekhar@cispa.de \
--to=amirmohammad.eftekhar@cispa.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.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
all inboxes | Powered by JetHome®