Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp3457124pxk; Mon, 7 Sep 2020 13:42:01 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwKE2JxTuLNrpupSUBs9w3vTC4W6oHY3E6JdIo64SoK9yJMmcrnrG5gH5C0M14kKwKn9iSn X-Received: by 2002:a05:6402:b68:: with SMTP id cb8mr5853561edb.350.1599511321504; Mon, 07 Sep 2020 13:42:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1599511321; cv=none; d=google.com; s=arc-20160816; b=R6MdvK3RXr0yPlm9yaXJmvM2NkD/jwIvYBiX82N0DB/p69Mleb5tNt8aY3IRH+f9Xu lnsFvxrqu+9aY4i7fCvb2y+qhfGEZG7H3/JHI0F6x9l9xjMtPIeUGhBcco0eJwd3To2Y +rSI8W0x1QsN/IO4grcIf8sp2/4SZVFj0xTZr/R0WCCID7kDzoulXXatR8QttQAHKApl y+k3Ev4bSDBetfo1hVm7UJ3A2vCudKBgjsPawQ1FRJoUmbjuhTxmvHE3/z6Q350k3c7A r8A5NLmSr7C6OLfkQ8zyxgK3mTzG7ifHvLgl7beLKTkr+zPXK/tRHiJRz9zadmljJKTI w+/Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from; bh=4CKD6rVWgMwv0slZYcX0kgigEgG9XoAGVLWH0V3Csxc=; b=nz5hz6KghoCdvnsetrG8b3utgO4ngsF6gspKRx5sYmM7IDjjcknskaFsp9KEVBBWx2 ar7D+Een8cIrFxId+vIM5RQaec/N5tZniCcd0RPaQsFdhRRznU0V2BXnq6/Ey7OO9Urm Y+fCvp2rKtV1+zlX1ueUGviMFUAQxFJfFitqci19Jzaiemkcfkokzsq+jJ7qfD5yfVgs hgTZAjrpysbIdhh4jLB5UGP1BKi/POeaLPJGIH/HUgkqWGs61HSjCAO7yQHWhceBPxav 5CO+WyouCGXrjKqSL6BgFN/zRikHw+Fanu4xiAliVDepLHZF560cN2nyGVNaVkxIraQM MFMg== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=vmware.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n19si10019455edq.82.2020.09.07.13.41.39; Mon, 07 Sep 2020 13:42:01 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=vmware.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727930AbgIGUjy (ORCPT + 99 others); Mon, 7 Sep 2020 16:39:54 -0400 Received: from ex13-edg-ou-001.vmware.com ([208.91.0.189]:52489 "EHLO EX13-EDG-OU-001.vmware.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726810AbgIGUjp (ORCPT ); Mon, 7 Sep 2020 16:39:45 -0400 Received: from sc9-mailhost3.vmware.com (10.113.161.73) by EX13-EDG-OU-001.vmware.com (10.113.208.155) with Microsoft SMTP Server id 15.0.1156.6; Mon, 7 Sep 2020 13:39:42 -0700 Received: from akaher-virtual-machine.eng.vmware.com (unknown [10.197.103.239]) by sc9-mailhost3.vmware.com (Postfix) with ESMTP id BC1FA40735; Mon, 7 Sep 2020 13:39:42 -0700 (PDT) From: Ajay Kaher To: , CC: , , , , , , , , , Subject: [PATCH v4.9.y 0/3] vfio: Fix for CVE-2020-12888 Date: Tue, 8 Sep 2020 02:05:17 +0530 Message-ID: <1599510917-23734-4-git-send-email-akaher@vmware.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1599510917-23734-1-git-send-email-akaher@vmware.com> References: <1599510917-23734-1-git-send-email-akaher@vmware.com> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: None (EX13-EDG-OU-001.vmware.com: akaher@vmware.com does not designate permitted sender hosts) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org CVE-2020-12888 Kernel: vfio: access to disabled MMIO space of some devices may lead to DoS scenario The VFIO modules allow users (guest VMs) to enable or disable access to the devices' MMIO memory address spaces. If a user attempts to access (read/write) the devices' MMIO address space when it is disabled, some h/w devices issue an interrupt to the CPU to indicate a fatal error condition, crashing the system. This flaw allows a guest user or process to crash the host system resulting in a denial of service. Patch 1/ is to force the user fault if PFNMAP vma might be DMA mapped before user access. Patch 2/ setup a vm_ops handler to support dynamic faulting instead of calling remap_pfn_range(). Also provides a list of vmas actively mapping the area which can later use to invalidate those mappings. Patch 3/ block the user from accessing memory spaces which is disabled by using new vma list support to zap, or invalidate, those memory mappings in order to force them to be faulted back in on access. Upstreamed patches link: https://lore.kernel.org/kvm/158871401328.15589.17598154478222071285.stgit@gimli.home [PATCH v4.9.y 1/3]: Backporting of upsream commit 41311242221e: vfio/type1: Support faulting PFNMAP vmas [PATCH v4.9.y 2/3]: Backporting of upsream commit 11c4cd07ba11: vfio-pci: Fault mmaps to enable vma tracking [PATCH v4.9.y 3/3]: Backporting of upsream commit abafbc551fdd: vfio-pci: Invalidate mmaps and block MMIO access on disabled memory