From: Frank Li <Frank.li@oss.nxp.com>
To: Rosen Penev <rosenp@gmail.com>
Cc: dmaengine@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
Frank Li <Frank.Li@kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2] dmaengine: bestcomm: gen_bd: fix out-of-bounds access in PSC parameter lookup
Date: Fri, 11 Sep 2026 11:08:19 -0500 [thread overview]
Message-ID: <aqQncwl99bTdW3av@SMW015318> (raw)
In-Reply-To: <20260910192404.21809-1-rosenp@gmail.com>
On Thu, Sep 10, 2026 at 12:24:04PM -0700, Rosen Penev wrote:
> The bcom_psc_params[] array has 6 entries (indices 0-5), but
> bcom_psc_gen_bd_rx_init() checked against MPC52xx_PSC_MAXNUM which can
> be 12 when CONFIG_PPC_MPC512x is set, allowing indices 6-11 to pass
> and read past the array. The tx init function had no bounds check at
> all.
>
> A malformed device tree with a large cell-index could therefore trigger
> an out-of-bounds read. The garbage initiator and ipr values would then
> be used for MMIO writes via out_8(&bcom_eng->regs->ipr[...], ...),
> potentially causing out-of-bounds MMIO accesses.
>
> Fix both functions to use ARRAY_SIZE(bcom_psc_params) for the bounds
> check.
>
> Also remove a stray unused 'struct psc;' forward declaration in
> bcom_psc_gen_bd_tx_init.
use two patches to fix it.
Frank
>
> Assisted-by: Opencode:big-pickle
> Signed-off-by: Rosen Penev <rosenp@gmail.com>
> ---
> v2: fix title
> drivers/dma/bestcomm/gen_bd.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/dma/bestcomm/gen_bd.c b/drivers/dma/bestcomm/gen_bd.c
> index 61b5746e1a97..00dfdc4b8eba 100644
> --- a/drivers/dma/bestcomm/gen_bd.c
> +++ b/drivers/dma/bestcomm/gen_bd.c
> @@ -321,7 +321,7 @@ static const struct bcom_psc_params bcom_psc_params[] = {
> struct bcom_task * bcom_psc_gen_bd_rx_init(unsigned psc_num, int queue_len,
> phys_addr_t fifo, int maxbufsize)
> {
> - if (psc_num >= MPC52xx_PSC_MAXNUM)
> + if (psc_num >= ARRAY_SIZE(bcom_psc_params))
> return NULL;
>
> return bcom_gen_bd_rx_init(queue_len, fifo,
> @@ -342,7 +342,9 @@ EXPORT_SYMBOL_GPL(bcom_psc_gen_bd_rx_init);
> struct bcom_task *
> bcom_psc_gen_bd_tx_init(unsigned psc_num, int queue_len, phys_addr_t fifo)
> {
> - struct psc;
> + if (psc_num >= ARRAY_SIZE(bcom_psc_params))
> + return NULL;
> +
> return bcom_gen_bd_tx_init(queue_len, fifo,
> bcom_psc_params[psc_num].tx_initiator,
> bcom_psc_params[psc_num].tx_ipr);
> --
> 2.55.0
>
prev parent reply other threads:[~2026-09-11 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 19:24 [PATCHv2] dmaengine: bestcomm: gen_bd: fix out-of-bounds access in PSC parameter lookup Rosen Penev
2026-09-10 19:34 ` sashiko-bot
2026-09-11 16:08 ` Frank Li [this message]
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=aqQncwl99bTdW3av@SMW015318 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rosenp@gmail.com \
--cc=vkoul@kernel.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 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.