From: Abdifatah Suruur <suruurism@gmail.com>
To: linux-fpga@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, yilun.xu@intel.com, trix@redhat.com
Subject: [PATCH] fpga: dfl: afu: prevent read-only port mappings from becoming writable
Date: Wed, 19 Aug 2026 11:42:13 +0300 [thread overview]
Message-ID: <20260819084213.1560-1-suruurism@gmail.com> (raw)
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")
Cc: stable@vger.kernel.org
Signed-off-by: Abdifatah Suruur <suruurism@gmail.com>
---
--- a/drivers/fpga/dfl-afu-main.c
+++ b/drivers/fpga/dfl-afu-main.c
@@ -836,7 +836,11 @@
if ((vma->vm_flags & VM_WRITE) &&
!(region.flags & DFL_PORT_REGION_WRITE))
return -EPERM;
+ /* Prevent read-only port mappings from being upgraded with mprotect() */
+ if (!(region.flags & DFL_PORT_REGION_WRITE))
+ vm_flags_clear(vma, VM_MAYWRITE);
+
/* Support debug access to the mapping */
vma->vm_ops = &afu_vma_ops;
vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
next reply other threads:[~2026-08-19 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 8:42 Abdifatah Suruur [this message]
2026-08-19 11:23 ` [PATCH] fpga: dfl: afu: prevent read-only port mappings from becoming writable Dinh Nguyen
-- 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=20260819084213.1560-1-suruurism@gmail.com \
--to=suruurism@gmail.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox