From: Alex Williamson <alex@shazbot.org>
To: Abdifatah Suruur <suruurism@gmail.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
eric.auger@redhat.com, smostafa@google.com, praan@google.com,
ioana.ciornei@nxp.com, nipun.gupta@amd.com,
nikhil.agarwal@amd.com, alex@shazbot.org
Subject: Re: [PATCH v2 7/7] vfio/cdx: reject non-shared MMIO mmaps
Date: Tue, 29 Sep 2026 14:36:21 -0600 [thread overview]
Message-ID: <20260929143621.540f0024@shazbot.org> (raw)
In-Reply-To: <20260929094848.7439-8-suruurism@gmail.com>
On Tue, 29 Sep 2026 12:48:48 +0300
Abdifatah Suruur <suruurism@gmail.com> wrote:
> vfio_cdx_mmap() accepts MAP_PRIVATE mappings. A non-shared mapping
> with VM_MAYWRITE is a COW mapping, and remap_pfn_range()'s COW special
> case in get_remap_pgoff() then overwrites vma->vm_pgoff with the
> physical frame number:
>
> if (is_cow) {
> if (addr != vm_start || end != vm_end)
> return -EINVAL;
> *vm_pgoff_p = pfn;
> }
>
> The VMA is inserted into the device file's mapping->i_mmap interval
> tree keyed by vm_pgoff, which VFIO expects to be the logical file
> offset: the core links every device mmap to the device inode's
> i_mapping precisely so that unmap_mapping_range() can revoke all
> mappings associated with a device (see vfio_device_cdev_open()).
It's actually vfio_device_open_file() and vfio_device_fops_cdev_open(),
vfio_device_cdev_open() doesn't exist.
> A raw PFN in vm_pgoff lands the interval tree entry in the wrong
> coordinate space, so unmap_mapping_range() cannot find the VMA and a
> stale MMIO mapping survives any revocation attempt. Without this
> check, a MAP_PRIVATE mapping reintroduces that corruption even with
> the logical-vm_pgoff fix in place.
>
> Require VM_SHARED as vfio-pci, vfio/fsl-mc and vfio/platform already
vfio-fsl-mc and vfio-platform for consistency.
Applied series with these changes to vfio next branch for v7.4. Thanks,
Alex
> do. This is defensive hygiene: vfio-cdx does not call
> unmap_mapping_range() today, so no reachable stale-mapping issue
> exists.
>
> Signed-off-by: Abdifatah Suruur <suruurism@gmail.com>
> ---
> drivers/vfio/cdx/main.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/vfio/cdx/main.c b/drivers/vfio/cdx/main.c
> index ea55b7767672c..28dc8c8256006 100644
> --- a/drivers/vfio/cdx/main.c
> +++ b/drivers/vfio/cdx/main.c
> @@ -271,6 +271,9 @@ static int vfio_cdx_mmap(struct vfio_device *core_vdev,
>
> index = vma->vm_pgoff >> (VFIO_CDX_OFFSET_SHIFT - PAGE_SHIFT);
>
> + if (!(vma->vm_flags & VM_SHARED))
> + return -EINVAL;
> +
> if (index >= cdx_dev->res_count)
> return -EINVAL;
>
prev parent reply other threads:[~2026-09-29 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 9:48 [PATCH v2 0/7] vfio: mmap()/mprotect() hygiene for MMIO region mappings Abdifatah Suruur
2026-09-29 9:48 ` [PATCH v2 1/7] vfio/platform: prevent read-only region mappings from becoming writable Abdifatah Suruur
2026-09-29 9:48 ` [PATCH v2 2/7] vfio/fsl-mc: " Abdifatah Suruur
2026-09-29 9:48 ` [PATCH v2 3/7] vfio/cdx: " Abdifatah Suruur
2026-09-29 9:48 ` [PATCH v2 4/7] vfio/platform: keep logical vm_pgoff in MMIO region mmap Abdifatah Suruur
2026-09-29 9:48 ` [PATCH v2 5/7] vfio/fsl-mc: " Abdifatah Suruur
2026-09-29 9:48 ` [PATCH v2 6/7] vfio/cdx: " Abdifatah Suruur
2026-09-29 9:48 ` [PATCH v2 7/7] vfio/cdx: reject non-shared MMIO mmaps Abdifatah Suruur
2026-09-29 20:36 ` Alex Williamson [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=20260929143621.540f0024@shazbot.org \
--to=alex@shazbot.org \
--cc=eric.auger@redhat.com \
--cc=ioana.ciornei@nxp.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nikhil.agarwal@amd.com \
--cc=nipun.gupta@amd.com \
--cc=praan@google.com \
--cc=smostafa@google.com \
--cc=suruurism@gmail.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
all inboxes | Powered by JetHome®