Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp8117032imu; Tue, 4 Dec 2018 03:17:35 -0800 (PST) X-Google-Smtp-Source: AFSGD/VSA4XtySLskFOezrSRl3+XXYmuw45f7OyBZ2E9rtM3dKw+XdyAr/IIDnFQy3yZ14OgvYT2 X-Received: by 2002:a17:902:4225:: with SMTP id g34mr20080751pld.152.1543922255897; Tue, 04 Dec 2018 03:17:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543922255; cv=none; d=google.com; s=arc-20160816; b=yAmHaO02XWr+jMvFizbNnGmTaWEKShfmqtYXHzKCqKVG2tsdB6IoLsrcIdujgEVg20 RjoRd4KkxhhQV2XkYC9qKuSxIZBZNmRUcgdcFCJr7zYfqfELDjvCF7om8XpwfXInW7X5 azJwfQhkZr9OnEp0slMj7ZIVhDTZ399+fuIoxGj6AdkQ/eNYlmsm+cCetITfKNKPhJij iMo9p2ThIv2wAzWESYhYP8kyHXGNlfjO9EeFAPr0a5VTtL5jp4wDCB/Y90ulEhtE8Ac1 b1AP+qdHctWzj6q1dzqHboSaFIAUjoJCcJ23aXGUXluljtkt4v5N/mxrx2QB6Nsq6JSH +J5A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=YBDD8Pwk278G+hYSBk5ydPIg2Q5vfcfBFAy8NtC7EXk=; b=Rrh5KfrhRtRW4M7uIerEg75QwXJxHw3Y88liuUOoGAylGJyl6kew380azEavWC2d11 t0ZwYGvlAmaN9RQthDHdZb6azsZ+0WRi/w3PbKEIy5+pmVD6HG51oyJlQGedzEQWfskT n2EyOmHYRxt8hVCzSsVH3xZmO+DMi593aVQPTD3weil8EXcgh5uvY44wV5nfSVFg12sF 1Ft6YVu7+WTgT1LttGyPmeHvCwLqGVR5b9sTzkW+sa0Iv50c3a/m68ZyVsG8OqfuvAG7 Kx6NPnCevmM5T+HWfMTgmLiCTtT58B/q8K99wiZTvQS5I1tn+T/OUc7C4sZ0qjGMBkpV UYVg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=MabgDMNl; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w10si13788854pgj.214.2018.12.04.03.17.20; Tue, 04 Dec 2018 03:17:35 -0800 (PST) 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; dkim=pass header.i=@kernel.org header.s=default header.b=MabgDMNl; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728237AbeLDLQs (ORCPT + 99 others); Tue, 4 Dec 2018 06:16:48 -0500 Received: from mail.kernel.org ([198.145.29.99]:53562 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728170AbeLDLFj (ORCPT ); Tue, 4 Dec 2018 06:05:39 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 4F0FD214E0; Tue, 4 Dec 2018 11:05:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1543921538; bh=LIBC66iDQHR77HG0ru530u6BIFiCnIQh8gWtTzi+Xow=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=MabgDMNlu08UF0MpnD3ITqZSQIDwP+6tTlqgCsDKD7YhgYtfE8q6YAUn9/cBjGgiU M2yBS1MkVRdk1llVZk/crruwjz95+fyIdAWYKwqmvDXNDD1sNTY2IMWzO2I3QiH9AN 18dKBpqJdrPB6w2B12Sgq6rT3ZkbNTBKsO5AwJX0= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, syzbot+a8ef68d71211ba264f56@syzkaller.appspotmail.com, Mark Kanda , Liran Alon , Paolo Bonzini Subject: [PATCH 4.14 111/146] KVM: x86: Fix kernel info-leak in KVM_HC_CLOCK_PAIRING hypercall Date: Tue, 4 Dec 2018 11:49:57 +0100 Message-Id: <20181204103731.291249187@linuxfoundation.org> X-Mailer: git-send-email 2.19.2 In-Reply-To: <20181204103726.750894136@linuxfoundation.org> References: <20181204103726.750894136@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.14-stable review patch. If anyone has any objections, please let me know. ------------------ From: Liran Alon commit bcbfbd8ec21096027f1ee13ce6c185e8175166f6 upstream. kvm_pv_clock_pairing() allocates local var "struct kvm_clock_pairing clock_pairing" on stack and initializes all it's fields besides padding (clock_pairing.pad[]). Because clock_pairing var is written completely (including padding) to guest memory, failure to init struct padding results in kernel info-leak. Fix the issue by making sure to also init the padding with zeroes. Fixes: 55dd00a73a51 ("KVM: x86: add KVM_HC_CLOCK_PAIRING hypercall") Reported-by: syzbot+a8ef68d71211ba264f56@syzkaller.appspotmail.com Reviewed-by: Mark Kanda Signed-off-by: Liran Alon Cc: stable@vger.kernel.org Signed-off-by: Paolo Bonzini Signed-off-by: Greg Kroah-Hartman --- arch/x86/kvm/x86.c | 1 + 1 file changed, 1 insertion(+) --- a/arch/x86/kvm/x86.c +++ b/arch/x86/kvm/x86.c @@ -6378,6 +6378,7 @@ static int kvm_pv_clock_pairing(struct k clock_pairing.nsec = ts.tv_nsec; clock_pairing.tsc = kvm_read_l1_tsc(vcpu, cycle); clock_pairing.flags = 0; + memset(&clock_pairing.pad, 0, sizeof(clock_pairing.pad)); ret = 0; if (kvm_write_guest(vcpu->kvm, paddr, &clock_pairing,