From: Alex Williamson <alex@shazbot.org>
To: Abdifatah Suruur <suruurism@gmail.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
alex.williamson@redhat.com, alex@shazbot.org
Subject: Re: [PATCH] vfio/fsl-mc: prevent read-only region mappings from becoming writable
Date: Wed, 2 Sep 2026 16:33:56 -0600 [thread overview]
Message-ID: <20260902163356.34649391@shazbot.org> (raw)
In-Reply-To: <20260819084209.1543-1-suruurism@gmail.com>
On Wed, 19 Aug 2026 11:42:09 +0300
Abdifatah Suruur <suruurism@gmail.com> wrote:
> vfio_fsl_mc_mmap() rejects writable mappings of regions without the
> WRITE flag, but leaves VM_MAYWRITE set. Userspace can map such a region
> read-only and then upgrade the mapping to writable with mprotect(),
> writing to MMIO regions (e.g. response portals) the device marks
> read-only.
>
> Clear VM_MAYWRITE for regions without the WRITE flag, as i915 does for
> its read-only objects and as fixed in drm/vc4 (CVE-2026-68445) and
> drm/panthor (CVE-2024-53071) and ptp: vmclock (commit
> a5edadbae57e2298a56cf7a4e774a027905a331f).
In reference to both this and the platform version of the same, this is
being positioned relative to CVE fixes, but while these drivers do
include support for exposing read-only regions, it appears there are no
devices that report a read-only region and it's apparently
mathematically impossible for fsl-mc to do so.
They're still logical fixes, they still appear valid, but the commit log
should be blunt that these are effectively unreachable. Thanks,
Alex
PS.
$ ./scripts/get_maintainer.pl -f drivers/vfio/platform/
Eric Auger <eric.auger@redhat.com> (maintainer:VFIO PLATFORM DRIVER)
Mostafa Saleh <smostafa@google.com> (reviewer:VFIO PLATFORM DRIVER)
Pranjal Shrivastava <praan@google.com> (reviewer:VFIO PLATFORM DRIVER)
Alex Williamson <alex@shazbot.org> (maintainer:VFIO DRIVER)
kvm@vger.kernel.org (open list:VFIO PLATFORM DRIVER)
linux-kernel@vger.kernel.org (open list)
$ ./scripts/get_maintainer.pl -f drivers/vfio/fsl-mc/
Ioana Ciornei <ioana.ciornei@nxp.com> (maintainer:VFIO FSL-MC DRIVER)
Alex Williamson <alex@shazbot.org> (maintainer:VFIO DRIVER)
kvm@vger.kernel.org (open list:VFIO FSL-MC DRIVER)
linux-kernel@vger.kernel.org (open list)
> Fixes: fb1ff4c194157 ("vfio/fsl-mc: Add VFIO framework skeleton for fsl-mc devices")
> Cc: stable@vger.kernel.org
> Signed-off-by: Abdifatah Suruur <suruurism@gmail.com>
>
> ---
> --- a/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> +++ b/drivers/vfio/fsl-mc/vfio_fsl_mc.c
> @@ -406,7 +406,11 @@
> if (!(vdev->regions[index].flags & VFIO_REGION_INFO_FLAG_WRITE)
> && (vma->vm_flags & VM_WRITE))
> return -EINVAL;
>
> + /* Prevent read-only region mappings from being upgraded with mprotect() */
> + if (!(vdev->regions[index].flags & VFIO_REGION_INFO_FLAG_WRITE))
> + vm_flags_clear(vma, VM_MAYWRITE);
> +
> vma->vm_private_data = mc_dev;
>
> return vfio_fsl_mc_mmap_mmio(vdev->regions[index], vma);
> }
>
next prev parent reply other threads:[~2026-09-02 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 8:42 [PATCH] vfio/fsl-mc: prevent read-only region mappings from becoming writable Abdifatah Suruur
2026-08-19 9:02 ` sashiko-bot
2026-09-02 22:33 ` Alex Williamson [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-19 8:39 Abdifatah Suruur
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=20260902163356.34649391@shazbot.org \
--to=alex@shazbot.org \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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