From: Mostafa Saleh <smostafa@google.com>
To: Abdifatah Suruur <suruurism@gmail.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Eric Auger <eric.auger@redhat.com>,
Pranjal Shrivastava <praan@google.com>,
Alex Williamson <alex@shazbot.org>
Subject: Re: [PATCH v2] vfio/platform: prevent read-only region mappings from becoming writable
Date: Thu, 3 Sep 2026 09:07:43 +0000 [thread overview]
Message-ID: <apk43xFwqAAwdd3s@google.com> (raw)
In-Reply-To: <20260903071955.13144-1-suruurism@gmail.com>
On Thu, Sep 03, 2026 at 10:19:55AM +0300, Abdifatah Suruur wrote:
> vfio_platform_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().
>
> 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),
> drm/panthor (CVE-2024-53071) and ptp: vmclock (commit
> a5edadbae57e2298a56cf7a4e774a027905a331f).
nit: checkpatch(--strict) fails with:
Please use git commit description style 'commit <12+ chars of sha1>
("<title line>")' - ie:
'commit a5edadbae57e ("ptp: vmclock: prevent read-only mappings from becoming writable")'
>
> Note this is defensive hardening: no in-tree platform driver currently
> publishes a region without the WRITE flag. The guard costs nothing and
> keeps the mmap() interface honest if a read-only region ever appears.
>
> Fixes: de49fc0d99e6a ("vfio/platform: initial skeleton of VFIO support for platform devices")
This only adds a stub for vfio_platform_mmap(), The right one is
Fixes: fad4d5b1f042 ("vfio/platform: support MMAP of MMIO regions")
> Signed-off-by: Abdifatah Suruur <suruurism@gmail.com>
Reviewed-by: Mostafa Saleh <smostafa@google.com>
Thanks,
Mostafa
> ---
> v2: commit log now states plainly that the read-only path is
> unreachable in practice, per Alex's review; dropped Cc: stable as
> there is no reachable issue to backport.
>
> --- a/drivers/vfio/platform/vfio_platform_common.c
> +++ b/drivers/vfio/platform/vfio_platform_common.c
> @@ -594,7 +594,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 = vdev;
>
> if (vdev->regions[index].type & VFIO_PLATFORM_REGION_TYPE_MMIO)
> return vfio_platform_mmap_mmio(vdev->regions[index], vma);
prev parent reply other threads:[~2026-09-03 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 7:19 Abdifatah Suruur
2026-09-03 9:07 ` Mostafa Saleh [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=apk43xFwqAAwdd3s@google.com \
--to=smostafa@google.com \
--cc=alex@shazbot.org \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=praan@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®