mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Christian A. Ehrhardt" <lk@c--e.de>
To: Sean Christopherson <seanjc@google.com>
Cc: "Christian A. Ehrhardt" <lk@c--e.de>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Kees Cook <keescook@chromium.org>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] x86/kvm: Fix state restore in em_rsm
Date: Wed, 26 Oct 2022 23:52:54 +0200	[thread overview]
Message-ID: <20221026215255.1063662-1-lk@c--e.de> (raw)

Syzkaller reports a stack-out-of-bounds access when
emulating RSM (return from system management mode).

Assume that a 64-bit capable host (i.e. CONFIG_X86_64 is true)
emulates a guest cpu that does not support 64-bit mode. In this case
RSM must use the 32-bit version of the SMM state map which only
contains space for 8 general purpose registers.
However, NR_EMULATOR_GPRS is defined to 16 due to CONFIG_X86_64.

As a result rsm_load_state_32 will try to restore 16
registers from the state save area which only contains 8
registers. Manual offset calculation easily shows that
memory beyond the end of the smstate buffer is accessed in
this case.

Revert the relevant parts of b443183a25ab and use explicit constants
for the number of general purpose registers, again. This
also ensures that the code in rsm_load_state_{32,64} matches
what is done in enter_smm_save_state_{32,64}.

Fixes: b443183a25ab ("KVM: x86: Reduce the number of emulator GPRs to '8' for 32-bit KVM")
Signed-off-by: Christian A. Ehrhardt <lk@c--e.de>
---
 arch/x86/kvm/emulate.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/x86/kvm/emulate.c b/arch/x86/kvm/emulate.c
index 3b27622d4642..05355ebaf4f3 100644
--- a/arch/x86/kvm/emulate.c
+++ b/arch/x86/kvm/emulate.c
@@ -2432,7 +2432,7 @@ static int rsm_load_state_32(struct x86_emulate_ctxt *ctxt,
 	ctxt->eflags =             GET_SMSTATE(u32, smstate, 0x7ff4) | X86_EFLAGS_FIXED;
 	ctxt->_eip =               GET_SMSTATE(u32, smstate, 0x7ff0);
 
-	for (i = 0; i < NR_EMULATOR_GPRS; i++)
+	for (i = 0; i < 8; i++)
 		*reg_write(ctxt, i) = GET_SMSTATE(u32, smstate, 0x7fd0 + i * 4);
 
 	val = GET_SMSTATE(u32, smstate, 0x7fcc);
@@ -2489,7 +2489,7 @@ static int rsm_load_state_64(struct x86_emulate_ctxt *ctxt,
 	u16 selector;
 	int i, r;
 
-	for (i = 0; i < NR_EMULATOR_GPRS; i++)
+	for (i = 0; i < 16; i++)
 		*reg_write(ctxt, i) = GET_SMSTATE(u64, smstate, 0x7ff8 - i * 8);
 
 	ctxt->_eip   = GET_SMSTATE(u64, smstate, 0x7f78);
-- 
2.34.1


             reply	other threads:[~2022-10-26 21:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26 21:52 Christian A. Ehrhardt [this message]
2022-10-26 22:33 ` Sean Christopherson

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=20221026215255.1063662-1-lk@c--e.de \
    --to=lk@c--e.de \
    --cc=keescook@chromium.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.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®