Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp4584839pxj; Wed, 12 May 2021 08:41:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxCIykTC+Ohb2cUHe62Bid5+A+wMkbDIrT0j68N8158BEjwDef+Jr8fMt7nR9ifOZTskUOu X-Received: by 2002:a17:906:2a16:: with SMTP id j22mr38077398eje.397.1620834116053; Wed, 12 May 2021 08:41:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620834116; cv=none; d=google.com; s=arc-20160816; b=wJl6mFj+iC4aRtlIMDeP9l5GSH2z4kbzsKiTXBdcmHZf3ZoqtUCcLEOqe0Y4zVXXMR iNg01up2nY2/ua+Vqdg4PRSd3FEVtSNm4x69/ZKffDl9iAEBKe3TNH9O2AnauNH0kt0s 5GAXgUNk9t+SFiM1nECNR3m1M9Pq/jfnQW+G5DuKCfB1tjzWvq7NJ/HRncoGULkfYGOo slLq1PUql+Xznf3G4oLHGk/YnLh0ThXjpqC3PN/sRt6VfPYNOogNGMlI9T/60i3mNMxS gT+1eLGJcmhDJ3TVYwoIW2fqhintnd/JAjUHORtZDSOqKZoCyeIgA3Lh5Hf08dkHv/E3 jEAQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=UU9eG6JDKBQtMoi3XUPl/jfZL1da+zGwMBJewcgqCCw=; b=cTWJTUqs4J5e9vkcw25v4n3QfVuJ5NA4ZaU1JdCCsRUt4epkyqc2hlSCMiTiFKexZI iJynvHOQuwV7Rt+Ef4ung4Y7Sej6Buz90IsxDQGj5SPg5g9VSdhbvYG2jE1ZoCHXB1yr kAOwmDS6Tk9X0GbYzZpgTfo0fLUxbaicP9y6G0/NTXCjOzP/85BPZ+snOdOOpqdoOOUL cjUTW9p3LzmVhT0mp31QRmjln6pEVbDfnYdQhih50ifSrVFg4YvAy4W7Eo3o/itGeOc4 LgWNacHU+xx2YLgbSBgH69toZSupqnGIEqaUt024ifqtvry3yg27FSRJ9ZzV0VRzrJ5F xo7g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=oErm4nV8; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b10si250901eje.471.2021.05.12.08.41.30; Wed, 12 May 2021 08:41:56 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=oErm4nV8; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236237AbhELPhX (ORCPT + 99 others); Wed, 12 May 2021 11:37:23 -0400 Received: from mail.kernel.org ([198.145.29.99]:50144 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234368AbhELPQi (ORCPT ); Wed, 12 May 2021 11:16:38 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id BE9C261977; Wed, 12 May 2021 15:06:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1620831987; bh=0X/d1CoQSv/APvaWuPpeFQT6tUOsHo13VsJG+W3O07U=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=oErm4nV8vbUMskUoJ4gy9uC5hGRf65F5gTeZn2XUoD/+H/WH58cNWCz7wd4I/ly0f kUlN9V72tr1RGN69JlFuo+/jDpJbvHkKEN9Iz1WHDoDqJz9OJPLybrsLFQ6+RTMViH qcq5+3TcXyS7fx5mMe3o61R/DKH+hpiVX2PcWyls= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Brijesh Singh , Tom Lendacky , Sean Christopherson , Paolo Bonzini Subject: [PATCH 5.10 095/530] KVM: SVM: Do not allow SEV/SEV-ES initialization after vCPUs are created Date: Wed, 12 May 2021 16:43:25 +0200 Message-Id: <20210512144822.926735023@linuxfoundation.org> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20210512144819.664462530@linuxfoundation.org> References: <20210512144819.664462530@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Sean Christopherson commit 8727906fde6ea665b52e68ddc58833772537f40a upstream. Reject KVM_SEV_INIT and KVM_SEV_ES_INIT if they are attempted after one or more vCPUs have been created. KVM assumes a VM is tagged SEV/SEV-ES prior to vCPU creation, e.g. init_vmcb() needs to mark the VMCB as SEV enabled, and svm_create_vcpu() needs to allocate the VMSA. At best, creating vCPUs before SEV/SEV-ES init will lead to unexpected errors and/or behavior, and at worst it will crash the host, e.g. sev_launch_update_vmsa() will dereference a null svm->vmsa pointer. Fixes: 1654efcbc431 ("KVM: SVM: Add KVM_SEV_INIT command") Fixes: ad73109ae7ec ("KVM: SVM: Provide support to launch and run an SEV-ES guest") Cc: stable@vger.kernel.org Cc: Brijesh Singh Cc: Tom Lendacky Signed-off-by: Sean Christopherson Message-Id: <20210331031936.2495277-4-seanjc@google.com> Signed-off-by: Paolo Bonzini Signed-off-by: Greg Kroah-Hartman --- arch/x86/kvm/svm/sev.c | 3 +++ 1 file changed, 3 insertions(+) --- a/arch/x86/kvm/svm/sev.c +++ b/arch/x86/kvm/svm/sev.c @@ -168,6 +168,9 @@ static int sev_guest_init(struct kvm *kv struct kvm_sev_info *sev = &to_kvm_svm(kvm)->sev_info; int asid, ret; + if (kvm->created_vcpus) + return -EINVAL; + ret = -EBUSY; if (unlikely(sev->active)) return ret;