Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp1949590ybe; Thu, 12 Sep 2019 02:03:34 -0700 (PDT) X-Google-Smtp-Source: APXvYqxyI1IMRT0+BGe++/dAJgjEite1sZDFA+pbtZ07IYNGKdE+Hoc+ZV3PfrMadyyg3gn07LKZ X-Received: by 2002:a50:ab83:: with SMTP id u3mr33986395edc.228.1568279014018; Thu, 12 Sep 2019 02:03:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568279014; cv=none; d=google.com; s=arc-20160816; b=ghS5GXw68k3+gEHTJWNgUSV8K9JjpYh24sqBOmVxBybhe96GW9I32ZX1g9ihoeyt0W SZgMVaCLYh28KcEWAzW2o5NYq36xMwN+JslXxZJfIzxAQwXpNJuaVXedwVX7NR/+Iw9Z b4WnvY7CeIo5l/FCMGGFDiz4j8pqfwEzkOFAvdSaKKC+FN2/A9S0pcmQsBctgX7HXTOJ wcXtWFEqXoUCz6+x7n6/ItkVot5VQdxuia3B8fOTU5ZbBVaXctr0syUbEZFhXiMkC86g JhfWBFmhIW30xCpvBtaxEy5bWPyNmJs54D3E4dum3Y4VLeNyaIvoPo1zTQSc817jAuKC FemA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=OdbWiHSMWMRqOuOTQQWyAeT6MHQpmrLeZTELw3F77vQ=; b=iV8VQcP8gDwb74UcaMCSxfGeIcUEfxEk5+vhvpfdkEjZ28zEYHz5fZ+yD8yBCYVT/L l8mnjel8MeZ7SVj/V4OXfonSOpg9Ec2nHkBWKoprs3QdBsQtl4PCNcUC0aZUA9T0/Rfz SfGDkrZWHKfZpsmYnxgNUChO/dgSF7/tyxEH9gDJ3Cou/nEyFUA+LI22VnDazSEEexix OGFAprwvumCVQI0ay6TUzyU0fIvWorrZjhwt+WC+KLLTVXiZyYtRVT1eLOuSYgcu++mK /7F754tS8eC1pC4XNcv0fzmjSxtvcTqM/GpgB/1EbK9//hzzVqCSc8ZGJweFKbFe2gAq rR/Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 8si15625842edz.299.2019.09.12.02.03.09; Thu, 12 Sep 2019 02:03:34 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730489AbfILJBD (ORCPT + 99 others); Thu, 12 Sep 2019 05:01:03 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47556 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726159AbfILJBD (ORCPT ); Thu, 12 Sep 2019 05:01:03 -0400 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 137FDC053FDF; Thu, 12 Sep 2019 09:01:03 +0000 (UTC) Received: from thuth.com (ovpn-204-41.brq.redhat.com [10.40.204.41]) by smtp.corp.redhat.com (Postfix) with ESMTP id A00AB60C63; Thu, 12 Sep 2019 09:00:55 +0000 (UTC) From: Thomas Huth To: Christian Borntraeger , Janosch Frank , kvm@vger.kernel.org Cc: David Hildenbrand , Cornelia Huck , linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH] KVM: s390: Do not leak kernel stack data in the KVM_S390_INTERRUPT ioctl Date: Thu, 12 Sep 2019 11:00:50 +0200 Message-Id: <20190912090050.20295-1-thuth@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Thu, 12 Sep 2019 09:01:03 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When the userspace program runs the KVM_S390_INTERRUPT ioctl to inject an interrupt, we convert them from the legacy struct kvm_s390_interrupt to the new struct kvm_s390_irq via the s390int_to_s390irq() function. However, this function does not take care of all types of interrupts that we can inject into the guest later (see do_inject_vcpu()). Since we do not clear out the s390irq values before calling s390int_to_s390irq(), there is a chance that we copy unwanted data from the kernel stack into the guest memory later if the interrupt data has not been properly initialized by s390int_to_s390irq(). Specifically, the problem exists with the KVM_S390_INT_PFAULT_INIT interrupt: s390int_to_s390irq() does not handle it, but the function __deliver_pfault_init() will later copy the uninitialized stack data from the ext.ext_params2 into the guest memory. Fix it by handling that interrupt type in s390int_to_s390irq(), too. And while we're at it, make sure that s390int_to_s390irq() now directly returns -EINVAL for unknown interrupt types, so that we do not run into this problem again in case we add more interrupt types to do_inject_vcpu() sometime in the future. Signed-off-by: Thomas Huth --- arch/s390/kvm/interrupt.c | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/arch/s390/kvm/interrupt.c b/arch/s390/kvm/interrupt.c index 3e7efdd9228a..165dea4c7f19 100644 --- a/arch/s390/kvm/interrupt.c +++ b/arch/s390/kvm/interrupt.c @@ -1960,6 +1960,16 @@ int s390int_to_s390irq(struct kvm_s390_interrupt *s390int, case KVM_S390_MCHK: irq->u.mchk.mcic = s390int->parm64; break; + case KVM_S390_INT_PFAULT_INIT: + irq->u.ext.ext_params = s390int->parm; + irq->u.ext.ext_params2 = s390int->parm64; + break; + case KVM_S390_RESTART: + case KVM_S390_INT_CLOCK_COMP: + case KVM_S390_INT_CPU_TIMER: + break; + default: + return -EINVAL; } return 0; } -- 2.18.1