From: Dinh Nguyen <dinguyen@kernel.org>
To: Abdifatah Suruur <suruurism@gmail.com>, linux-fpga@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, yilun.xu@intel.com, trix@redhat.com
Subject: Re: [PATCH] fpga: dfl: afu: prevent read-only port mappings from becoming writable
Date: Wed, 19 Aug 2026 06:23:21 -0500 [thread overview]
Message-ID: <7d5b8ce3-2f07-434b-afcf-927214959730@kernel.org> (raw)
In-Reply-To: <20260819084213.1560-1-suruurism@gmail.com>
On 8/19/26 03:42, Abdifatah Suruur wrote:
> afu_mmap() rejects writable mappings of port 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 FPGA port control/status registers the host owns. A guest
> assigned an AFU can use this to reconfigure or reset the port and
> interfere with other tenants on the same FPGA.
>
> 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).
>
> Fixes: 1a1527cf5ddac ("fpga: dfl: add FPGA Accelerated Function Unit driver basic framework")
Please used exactly 12 characters for the hash ID.
Dinh
next prev parent reply other threads:[~2026-08-19 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 8:42 [PATCH] fpga: dfl: afu: prevent read-only port mappings from becoming writable Abdifatah Suruur
2026-08-19 11:23 ` Dinh Nguyen [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=7d5b8ce3-2f07-434b-afcf-927214959730@kernel.org \
--to=dinguyen@kernel.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=suruurism@gmail.com \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.