From: Greg KH <gregkh@linuxfoundation.org>
To: Sebastian Alba Vives <sebasjosue84@gmail.com>
Cc: linux-fpga@vger.kernel.org, yilun.xu@linux.intel.com,
conor.dooley@microchip.com, mdf@kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] fpga: microchip-spi: add bounds checks in mpf_ops_parse_header()
Date: Thu, 2 Apr 2026 18:06:12 +0200 [thread overview]
Message-ID: <2026040243-gratify-griminess-87a6@gregkh> (raw)
In-Reply-To: <20260402153752.3793055-1-sebasjosue84@gmail.com>
On Thu, Apr 02, 2026 at 09:37:52AM -0600, Sebastian Alba Vives wrote:
> From: Sebastian Josue Alba Vives <sebasjosue84@gmail.com>
>
> mpf_ops_parse_header() reads several fields from the bitstream file
> and uses them as offsets and sizes without validating them against the
> buffer size, leading to multiple out-of-bounds read vulnerabilities:
Note, bitstream files are "trusted" so this really isn't a
"vulnerability" just a "someone with hardware permissions sent a stupid
file to the kernel" issue :)
> 1. There is no check that count is large enough to read header_size
> at MPF_HEADER_SIZE_OFFSET (24). Add a minimum count check.
>
> 2. When header_size (u8 from file) is 0, the expression
> *(buf + header_size - 1) reads one byte before the buffer.
> Return -EINVAL since retrying with a larger buffer cannot fix
> a zero header_size.
>
> 3. In the block lookup loop, block_id_offset and block_start_offset
> advance by MPF_LOOKUP_TABLE_RECORD_SIZE (9) each iteration with
> blocks_num (u8) controlling the count. With a small buffer, these
> offsets exceed count, causing OOB reads via get_unaligned_le32().
> Return -EAGAIN since a larger buffer may resolve the issue.
>
> 4. components_size_start (from file) and component_size_byte_num
> (derived from components_num, u16 from file) are used as offsets
> into buf without validation, allowing arbitrary OOB reads.
>
> Add bounds checks for all four cases.
>
> Fixes: 5f8d4a9008307 ("fpga: microchip-spi: add Microchip MPF FPGA manager")
> Cc: stable@vger.kernel.org
> Signed-off-by: Sebastian Alba Vives <sebasjosue84@gmail.com>
> ---
> drivers/fpga/microchip-spi.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
Please look at these review comments:
https://sashiko.dev/#/patchset/20260402153752.3793055-1-sebasjosue84%40gmail.com
this driver is "odd", but some of those comments seem correct.
thansk,
greg k-h
next prev parent reply other threads:[~2026-04-02 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260402125446.3776153-3-sebasjosue84@gmail.com>
2026-04-02 15:37 ` [PATCH v2] fpga: microchip-spi: add bounds checks in mpf_ops_parse_header() Sebastian Alba Vives
2026-04-02 16:03 ` Greg KH
2026-04-02 16:06 ` Greg KH [this message]
2026-04-02 16:16 ` Conor Dooley
2026-04-02 16:23 ` [PATCH v3] " Sebastian Alba Vives
2026-04-07 10:44 ` Xu Yilun
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=2026040243-gratify-griminess-87a6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=conor.dooley@microchip.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=sebasjosue84@gmail.com \
--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