From: "Wachowski, Karol" <karol.wachowski@linux.intel.com>
To: Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>,
dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, jeff.hugo@oss.qualcomm.com,
lizhi.hou@amd.com, dawid.osuchowski@linux.intel.com,
stable@vger.kernel.org
Subject: Re: [PATCH] accel/ivpu: Add bounds check for firmware runtime memory
Date: Fri, 29 May 2026 14:27:29 +0200 [thread overview]
Message-ID: <fcad21ec-ebeb-41af-a94a-b31120fa945a@linux.intel.com> (raw)
In-Reply-To: <20260529120853.135876-1-andrzej.kacprowski@linux.intel.com>
On 29-May-26 14:08, Andrzej Kacprowski wrote:
> Validate that the firmware runtime memory specified in the image
> header is properly aligned and sized to hold the firmware image.
> This prevents errors during memory allocation and image transfer.
>
> Fixes: 2007e210b6a1 ("accel/ivpu: Split FW runtime and global memory buffers")
> Cc: <stable@vger.kernel.org> # v7.0+
> Signed-off-by: Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>
Reviewed-by: Karol Wachowski <karol.wachowski@linux.intel.com>
> ---
> drivers/accel/ivpu/ivpu_fw.c | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/drivers/accel/ivpu/ivpu_fw.c b/drivers/accel/ivpu/ivpu_fw.c
> index 107f8ad31050..33c50779c06b 100644
> --- a/drivers/accel/ivpu/ivpu_fw.c
> +++ b/drivers/accel/ivpu/ivpu_fw.c
> @@ -259,6 +259,22 @@ static int ivpu_fw_parse(struct ivpu_device *vdev)
> return -EINVAL;
> }
>
> + if (!PAGE_ALIGNED(runtime_addr)) {
> + ivpu_err(vdev, "Runtime address 0x%llx not page aligned\n", runtime_addr);
> + return -EINVAL;
> + }
> +
> + if (!PAGE_ALIGNED(runtime_size)) {
> + ivpu_err(vdev, "Runtime size %llu not page aligned\n", runtime_size);
> + return -EINVAL;
> + }
> +
> + if (runtime_size < image_size) {
> + ivpu_err(vdev, "Runtime size too small: %llu, image size: %llu\n",
> + runtime_size, image_size);
> + return -EINVAL;
> + }
> +
> if (!ivpu_is_within_range(image_load_addr, image_size, &vdev->hw->ranges.runtime)) {
> ivpu_err(vdev, "Invalid firmware load address: 0x%llx and size %llu\n",
> image_load_addr, image_size);
next prev parent reply other threads:[~2026-05-29 12:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 12:08 [PATCH] accel/ivpu: Add bounds check for firmware runtime memory Andrzej Kacprowski
2026-05-29 12:27 ` Wachowski, Karol [this message]
2026-06-02 5:50 ` Wachowski, Karol
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=fcad21ec-ebeb-41af-a94a-b31120fa945a@linux.intel.com \
--to=karol.wachowski@linux.intel.com \
--cc=andrzej.kacprowski@linux.intel.com \
--cc=dawid.osuchowski@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=lizhi.hou@amd.com \
--cc=oded.gabbay@gmail.com \
--cc=stable@vger.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.