From: Liviu Dudau <liviu.dudau@arm.com>
To: Osama Abdelkader <osama.abdelkader@gmail.com>
Cc: Boris Brezillon <boris.brezillon@collabora.com>,
Steven Price <steven.price@arm.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Heiko Stuebner <heiko@sntech.de>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] drm/panthor: fix firmware control interface bounds checks
Date: Tue, 28 Jul 2026 16:12:53 +0100 [thread overview]
Message-ID: <amjG9WVZrb6v92_h@e142607> (raw)
In-Reply-To: <20260720134435.13377-1-osama.abdelkader@gmail.com>
On Mon, Jul 20, 2026 at 03:44:35PM +0200, Osama Abdelkader wrote:
> panthor_init_cs_iface() and panthor_init_csg_iface() validate firmware
> control interface offsets with 32-bit arithmetic and the size of the host
> wrapper structures. The offsets are derived from firmware-provided strides,
> so the arithmetic can wrap before the bounds check, and the host wrapper
> size is not the size of the firmware control interface being mapped.
How can the offsets wrap with the firmware-provided strides? It's not like
the firmware provides arbitrarily large strides.
>
> Use 64-bit arithmetic for the computed offsets and validate against the
> actual firmware control interface structure sizes with subtraction-based
> bounds checks. Also validate that the shared section is large enough for
> the global control interface before using it.
>
> Fixes: 2718d91816ee ("drm/panthor: Add the FW logical block")
> Cc: stable@vger.kernel.org
> Signed-off-by: Osama Abdelkader <osama.abdelkader@gmail.com>
> ---
> drivers/gpu/drm/panthor/panthor_fw.c | 18 +++++++++++++-----
> 1 file changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/panthor/panthor_fw.c b/drivers/gpu/drm/panthor/panthor_fw.c
> index eee2bc7e8541..e2fcbd639c3c 100644
> --- a/drivers/gpu/drm/panthor/panthor_fw.c
> +++ b/drivers/gpu/drm/panthor/panthor_fw.c
> @@ -897,15 +897,16 @@ static int panthor_init_cs_iface(struct panthor_device *ptdev,
> struct panthor_fw_csg_iface *csg_iface = panthor_fw_get_csg_iface(ptdev, csg_idx);
> struct panthor_fw_cs_iface *cs_iface = &ptdev->fw->iface.streams[csg_idx][cs_idx];
> u64 shared_section_sz = panthor_kernel_bo_size(ptdev->fw->shared_section->mem);
> - u32 iface_offset = CSF_GROUP_CONTROL_OFFSET +
> - (csg_idx * glb_iface->control->group_stride) +
> + u64 iface_offset = CSF_GROUP_CONTROL_OFFSET +
> + ((u64)csg_idx * glb_iface->control->group_stride) +
> CSF_STREAM_CONTROL_OFFSET +
> - (cs_idx * csg_iface->control->stream_stride);
> + ((u64)cs_idx * csg_iface->control->stream_stride);
> struct panthor_fw_cs_iface *first_cs_iface =
> panthor_fw_get_cs_iface(ptdev, 0, 0);
>
> - if (iface_offset + sizeof(*cs_iface) >= shared_section_sz)
> + if (iface_offset > shared_section_sz ||
> + sizeof(*cs_iface->control) > shared_section_sz - iface_offset)
> return -EINVAL;
>
> spin_lock_init(&cs_iface->lock);
> cs_iface->control = ptdev->fw->shared_section->mem->kmap + iface_offset;
> @@ -955,11 +956,13 @@ static int panthor_init_csg_iface(struct panthor_device *ptdev,
> struct panthor_fw_global_iface *glb_iface = panthor_fw_get_glb_iface(ptdev);
> struct panthor_fw_csg_iface *csg_iface = &ptdev->fw->iface.groups[csg_idx];
> u64 shared_section_sz = panthor_kernel_bo_size(ptdev->fw->shared_section->mem);
> - u32 iface_offset = CSF_GROUP_CONTROL_OFFSET + (csg_idx * glb_iface->control->group_stride);
> + u64 iface_offset = CSF_GROUP_CONTROL_OFFSET +
> + ((u64)csg_idx * glb_iface->control->group_stride);
> unsigned int i;
>
> - if (iface_offset + sizeof(*csg_iface) >= shared_section_sz)
> + if (iface_offset > shared_section_sz ||
> + sizeof(*csg_iface->control) > shared_section_sz - iface_offset)
> return -EINVAL;
>
> spin_lock_init(&csg_iface->lock);
> csg_iface->control = ptdev->fw->shared_section->mem->kmap + iface_offset;
> @@ -1011,12 +1014,16 @@ static u32 panthor_get_instr_features(struct panthor_device *ptdev)
> static int panthor_fw_init_ifaces(struct panthor_device *ptdev)
> {
> struct panthor_fw_global_iface *glb_iface = &ptdev->fw->iface.global;
> + u64 shared_section_sz = panthor_kernel_bo_size(ptdev->fw->shared_section->mem);
> unsigned int i;
>
> if (!ptdev->fw->shared_section->mem->kmap)
> return -EINVAL;
>
> + if (sizeof(*glb_iface->control) > shared_section_sz)
> + return -EINVAL;
> +
> spin_lock_init(&glb_iface->lock);
> glb_iface->control = ptdev->fw->shared_section->mem->kmap;
>
> if (!glb_iface->control->version) {
> --
> 2.43.0
>
I'm OK with the general content of the patch, so:
Reviewed-by: Liviu Dudau <liviu.dudau@arm.com>
Best regards,
Liviu
--
====================
| I would like to |
| fix the world, |
| but they're not |
| giving me the |
\ source code! /
---------------
¯\_(ツ)_/¯
next prev parent reply other threads:[~2026-07-28 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 13:44 Osama Abdelkader
2026-07-28 15:12 ` Liviu Dudau [this message]
2026-07-29 11:36 ` Osama Abdelkader
2026-07-31 7:32 ` Steven Price
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=amjG9WVZrb6v92_h@e142607 \
--to=liviu.dudau@arm.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=osama.abdelkader@gmail.com \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=steven.price@arm.com \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®