From: sashiko-bot@kernel.org
To: "Chang S. Bae" <chang.seok.bae@intel.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v7 13/20] KVM: x86: Reject EVEX-prefixed instructions
Date: Wed, 02 Sep 2026 02:59:24 +0000 [thread overview]
Message-ID: <20260902025924.D33F61F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260902021804.718676-14-chang.seok.bae@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The EVEX prefix check reads `ctxt->modrm` without fetching it, resulting in the use of a stale value from a previously emulated instruction.
--
commit 01b255a08e34ec61090bf09c90c37d94d681cde4
Author: Chang S. Bae <chang.seok.bae@intel.com>
KVM: x86: Reject EVEX-prefixed instructions
Explicitly mark EVEX-prefixed opcodes (0x62) as unsupported.
> diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
> index eba4e9b7cd5cf..f0d5a40eba27f 100644
> --- a/arch/x86/kvm/emulate.c
> +++ b/arch/x86/kvm/emulate.c
> @@ -5052,6 +5052,11 @@ int x86_decode_insn(struct x86_emulate_ctxt *ctxt, void *insn, int insn_len, int
> if (opcode.flags & ModRM)
> ctxt->modrm = insn_fetch(u8, ctxt);
>
> + /* EVEX-prefixed instructions are not implemented */
> + if (ctxt->opcode_len == 1 && ctxt->b == 0x62 &&
> + (mode == X86EMUL_MODE_PROT64 || (ctxt->modrm & 0xc0) == 0xc0))
> + opcode.flags = NotImpl;
> +
[Severity: Medium]
Does this EVEX prefix check read a stale ctxt->modrm value?
In x86_decode_insn(), opcode 0x62 is mapped to NotImpl in the 1-byte opcode
table, which lacks the ModRM flag. This means ctxt->modrm is not fetched
by the check right above this new block.
As a result, if a guest executes opcode 0x62 in 16-bit or 32-bit mode, this
condition evaluates (ctxt->modrm & 0xc0) == 0xc0 using a leftover value from
a previously emulated instruction.
It was previously suggested this might trigger KMSAN warnings and cause a
host denial of service. Since ctxt is allocated via kmem_cache_zalloc(),
KMSAN sees the memory as initialized, which makes the DoS concern inaccurate.
However, does this logic flaw still break the intended EVEX detection? Since
0x62 already evaluates to NotImpl during the opcode table lookup, it seems
the subsequent opcode.flags = NotImpl assignment here is a no-op with no
functional impact.
> done_modrm:
> ctxt->d = opcode.flags;
> while (ctxt->d & GroupMask) {
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260902021804.718676-1-chang.seok.bae@intel.com?part=13
next prev parent reply other threads:[~2026-09-02 2:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 2:17 [PATCH v7 00/20] KVM: x86: Enable APX for guests Chang S. Bae
2026-09-02 2:17 ` [PATCH v7 01/20] KVM: x86: Extend VCPU registers for EGPRs Chang S. Bae
2026-09-02 2:17 ` [PATCH v7 02/20] KVM: VMX: Save guest EGPRs in VCPU cache Chang S. Bae
2026-09-02 3:26 ` sashiko-bot
2026-09-02 2:17 ` [PATCH v7 03/20] KVM: x86: Support APX state for XSAVE ABI Chang S. Bae
2026-09-02 3:08 ` sashiko-bot
2026-09-02 2:17 ` [PATCH v7 04/20] KVM: VMX: Refactor VMX instruction information access Chang S. Bae
2026-09-02 2:17 ` [PATCH v7 05/20] KVM: VMX: Refactor instruction information decoding Chang S. Bae
2026-09-02 2:17 ` [PATCH v7 06/20] KVM: VMX: Remove unused control-register access defines Chang S. Bae
2026-09-02 2:17 ` [PATCH v7 07/20] KVM: VMX: Refactor register index retrieval from exit qualification Chang S. Bae
2026-09-02 2:17 ` [PATCH v7 08/20] KVM: VMX: Support instruction information extension Chang S. Bae
2026-09-02 2:17 ` [PATCH v7 09/20] KVM: nVMX: Propagate extended instruction information Chang S. Bae
2026-09-02 3:07 ` sashiko-bot
2026-09-02 2:17 ` [PATCH v7 10/20] KVM: x86: Support EGPR accessing and tracking for emulator Chang S. Bae
2026-09-02 2:17 ` [PATCH v7 11/20] KVM: x86: Handle EGPR index and REX2-incompatible opcodes Chang S. Bae
2026-09-02 3:06 ` sashiko-bot
2026-09-02 2:17 ` [PATCH v7 12/20] KVM: x86: Support REX2-prefixed opcode decode Chang S. Bae
2026-09-02 2:17 ` [PATCH v7 13/20] KVM: x86: Reject EVEX-prefixed instructions Chang S. Bae
2026-09-02 2:59 ` sashiko-bot [this message]
2026-09-02 2:17 ` [PATCH v7 14/20] KVM: x86: Move KVM_SUPPORTED_{XCR0,XSS} into kvm_x86_vendor_init() Chang S. Bae
2026-09-02 2:17 ` [PATCH v7 15/20] KVM: x86: Guard valid XCR0.APX settings Chang S. Bae
2026-09-02 2:18 ` [PATCH v7 16/20] KVM: x86: Add APX to supported XCR0 Chang S. Bae
2026-09-02 3:07 ` sashiko-bot
2026-09-02 2:18 ` [PATCH v7 17/20] KVM: x86: Expose APX foundation feature to userspace Chang S. Bae
2026-09-02 2:18 ` [PATCH v7 18/20] KVM: x86: Expose APX sub-features " Chang S. Bae
2026-09-02 3:00 ` sashiko-bot
2026-09-02 2:18 ` [PATCH v7 19/20] KVM: x86: selftests: Add APX state and ABI test Chang S. Bae
2026-09-02 3:07 ` sashiko-bot
2026-09-02 2:18 ` [PATCH v7 20/20] KVM: x86: selftests: Add APX state handling and XCR0 sanity checks Chang S. Bae
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=20260902025924.D33F61F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=chang.seok.bae@intel.com \
--cc=kvm@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.