From: Sebastian Alba Vives <sebasjosue84@gmail.com>
To: yilun.xu@linux.intel.com, gregkh@linuxfoundation.org
Cc: linux-fpga@vger.kernel.org, conor.dooley@microchip.com,
mdf@kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org,
Sebastian Alba Vives <sebasjosue84@gmail.com>
Subject: [PATCH v6 0/3] fpga: bounds checks and input validation fixes
Date: Tue, 12 May 2026 07:07:07 -0600 [thread overview]
Message-ID: <20260512130710.933089-1-sebasjosue84@gmail.com> (raw)
This series adds three defensive fixes to FPGA drivers:
Patch 1/3 fixes dfh_get_param_size() in the DFL driver where the loop
bounds check is evaluated before incrementing size, potentially returning
an inflated size that exceeds the feature region boundary.
Patch 2/3 validates the DMA mapping length in afu_ioctl_dma_map() at the
ioctl entry point before passing it down the call chain, preventing
implicit integer truncation in pin_user_pages_fast().
Patch 3/3 fixes mpf_ops_parse_header() in the Microchip SPI FPGA manager
where a zero header_size from the bitstream causes a one-byte read before
the buffer start.
Sebastian Alba Vives (3):
fpga: dfl: add bounds check in dfh_get_param_size()
fpga: dfl-afu: validate DMA mapping length in afu_dma_map_region()
fpga: microchip-spi: fix zero header_size OOB read in
mpf_ops_parse_header()
drivers/fpga/dfl-afu-main.c | 3 +++
drivers/fpga/dfl.c | 2 ++
drivers/fpga/microchip-spi.c | 3 +++
3 files changed, 8 insertions(+)
--
2.43.0
next reply other threads:[~2026-05-12 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 13:07 Sebastian Alba Vives [this message]
2026-05-12 13:07 ` [PATCH v6 1/3] fpga: dfl: add bounds check in dfh_get_param_size() Sebastian Alba Vives
2026-05-12 13:07 ` [PATCH v6 2/3] fpga: dfl-afu: validate DMA mapping length in afu_dma_map_region() Sebastian Alba Vives
2026-05-12 13:07 ` [PATCH v6 3/3] fpga: microchip-spi: fix zero header_size OOB read in mpf_ops_parse_header() Sebastian Alba Vives
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=20260512130710.933089-1-sebasjosue84@gmail.com \
--to=sebasjosue84@gmail.com \
--cc=conor.dooley@microchip.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yilun.xu@linux.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