public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Ajay Kaher <akaher@vmware.com>
Cc: gregkh@linuxfoundation.org, alex.williamson@redhat.com,
	cohuck@redhat.com, peterx@redhat.com, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	srivatsab@vmware.com, srivatsa@csail.mit.edu,
	vsirnapalli@vmware.com
Subject: Re: [PATCH v5.4.y 0/3] vfio: Fix for CVE-2020-12888
Date: Mon, 7 Sep 2020 13:09:11 -0400	[thread overview]
Message-ID: <20200907170911.GM8670@sasha-vm> (raw)
In-Reply-To: <1599401277-32172-4-git-send-email-akaher@vmware.com>

On Sun, Sep 06, 2020 at 07:37:57PM +0530, Ajay Kaher wrote:
>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.

I've queued this and the 4.19 backports, thanks!

-- 
Thanks,
Sasha

      reply	other threads:[~2020-09-07 17:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-06 14:07 [PATCH v5.4.y 1/3] vfio/type1: Support faulting PFNMAP vmas Ajay Kaher
2020-09-06 14:07 ` [PATCH v5.4.y 2/3] vfio-pci: Fault mmaps to enable vma tracking Ajay Kaher
2020-09-06 14:07 ` [PATCH v5.4.y 3/3] vfio-pci: Invalidate mmaps and block MMIO access on disabled memory Ajay Kaher
2020-09-06 14:07 ` [PATCH v5.4.y 0/3] vfio: Fix for CVE-2020-12888 Ajay Kaher
2020-09-07 17:09   ` Sasha Levin [this message]

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=20200907170911.GM8670@sasha-vm \
    --to=sashal@kernel.org \
    --cc=akaher@vmware.com \
    --cc=alex.williamson@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterx@redhat.com \
    --cc=srivatsa@csail.mit.edu \
    --cc=srivatsab@vmware.com \
    --cc=stable@vger.kernel.org \
    --cc=vsirnapalli@vmware.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