mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Abdifatah Suruur <suruurism@gmail.com>, xen-devel@lists.xenproject.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen/gntdev: prevent private mappings from becoming writable
Date: Fri, 25 Sep 2026 17:38:46 +0200	[thread overview]
Message-ID: <3a2f0678-f81a-47cd-a47b-af9b439cedb3@suse.com> (raw)
In-Reply-To: <20260819084217.1577-1-suruurism@gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 910 bytes --]

On 19.08.26 10:42, Abdifatah Suruur wrote:
> gntdev_mmap() rejects writable private (non-shared) mappings of foreign
> grant pages, because a private writable mapping takes the COW path on
> pages that have no proper struct-page backing.  However, VM_MAYWRITE is
> left set, so userspace can map the grant read-only and then upgrade the
> mapping to writable with mprotect(), hitting the same COW path the
> check was written to prevent.
> 
> Clear VM_MAYWRITE for private mappings, 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).
> 
> Fixes: ab31523c2fcac ("xen/gntdev: allow usermode to map granted pages")
> Cc: stable@vger.kernel.org
> Signed-off-by: Abdifatah Suruur <suruurism@gmail.com>

Reviewed-by: Juergen Gross <jgross@suse.com>


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2026-09-25 15:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19  8:42 Abdifatah Suruur
2026-09-25 15:38 ` Juergen Gross [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=3a2f0678-f81a-47cd-a47b-af9b439cedb3@suse.com \
    --to=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suruurism@gmail.com \
    --cc=xen-devel@lists.xenproject.org \
    /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®