From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Aleksandr Burakov <a.burakov@rosalinux.ru>
Cc: Bingbu Cao <bingbu.cao@intel.com>,
Tianshu Qiu <tian.shu.qiu@intel.com>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH] staging: media: ipu3: buffer overflow fix in imgu_map_node
Date: Mon, 2 Jan 2023 13:41:21 +0000 [thread overview]
Message-ID: <Y7LfAR4QdIzp81yW@paasikivi.fi.intel.com> (raw)
In-Reply-To: <20221223123025.5948-1-a.burakov@rosalinux.ru>
Hi Aleksandr,
On Fri, Dec 23, 2022 at 03:30:25PM +0300, Aleksandr Burakov wrote:
> If imgu_node_map[i].css_queue is not equal to css_queue
> then "i" after the loop could be equal to IMGU_NODE_NUM
> that is more than the border value (IMGU_NODE_NUM - 1).
> So imgu_map_node() call may return IMGU_NODE_NUM that is more
> than expected value.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Fixes: 7fc7af649ca7 ("media: staging/intel-ipu3: Add imgu top level pci device driver")
> Signed-off-by: Aleksandr Burakov <a.burakov@rosalinux.ru>
> ---
> drivers/staging/media/ipu3/ipu3.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/media/ipu3/ipu3.c b/drivers/staging/media/ipu3/ipu3.c
> index 0c453b37f8c4..cb09eb3cc227 100644
> --- a/drivers/staging/media/ipu3/ipu3.c
> +++ b/drivers/staging/media/ipu3/ipu3.c
> @@ -60,8 +60,10 @@ unsigned int imgu_map_node(struct imgu_device *imgu, unsigned int css_queue)
> for (i = 0; i < IMGU_NODE_NUM; i++)
> if (imgu_node_map[i].css_queue == css_queue)
> break;
> -
> - return i;
> + if (i < IMGU_NODE_NUM)
> + return i;
> + else
> + return (IMGU_NODE_NUM - 1);
> }
>
> /**************** Dummy buffers ****************/
Thanks for the patch. It would require a bug elsewhere in the driver for
this to happen. If some handling for this case is added, it shouldn't be
hiding the issue.
One easy way could be to add WARN_ON() for this, and return some value (as
you do). Zero would do equally well.
I.e.
return WARN_ON(i >= IMGU_NODE_NUM) ? 0 : i;
--
Sakari Ailus
next prev parent reply other threads:[~2023-01-02 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 12:30 [PATCH] staging: media: ipu3: buffer overflow fix in imgu_map_node Aleksandr Burakov
2023-01-02 13:41 ` Sakari Ailus [this message]
2023-01-04 13:33 ` Dan Carpenter
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=Y7LfAR4QdIzp81yW@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=a.burakov@rosalinux.ru \
--cc=bingbu.cao@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lvc-project@linuxtesting.org \
--cc=tian.shu.qiu@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