From: Nicolas Dufresne <nicolas.dufresne@collabora.com>
To: Tharit Tangkijwanichakul <tharitt97@gmail.com>,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-media@vger.kernel.org
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@kernel.org>,
Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
me@brighamcampbell.com, jkoolstra@xs4all.nl
Subject: Re: [PATCH] media: hantro: Harden MPEG-2 control access against NULL
Date: Mon, 10 Aug 2026 10:09:44 -0400 [thread overview]
Message-ID: <2a5abb0004aa453c2f985aff41c72d4952006fc9.camel@collabora.com> (raw)
In-Reply-To: <20260731140751.1183-1-tharitt97@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1886 bytes --]
Le vendredi 31 juillet 2026 à 14:07 +0000, Tharit Tangkijwanichakul a écrit :
> The MPEG-2 sequence and picture controls are validated
> before a job is queued, so hantro_get_ctrl() is not expected to return
> NULL in hantro_g1_mpeg2_dec_run(). The controls are nonetheless
> dereferenced unconditionally.
>
> Harden the invariant by checking the sequence and picture controls with
> WARN_ON().
>
> Found by code inspection.
>
> Fixes: f329e21e9dad ("media: uapi: mpeg2: Split sequence and picture parameters")
> Signed-off-by: Tharit Tangkijwanichakul <tharitt97@gmail.com>
Reviewed-by: Nicolas Dufresne <nicolas.dufresne@collabora.com>
p.s. this is a bit cosmetic, since only a programming error could lead to that,
once a control is registered, it has a value. But that makes it consistent with
all other use of hantro_get_ctrl() in this driver, which I like.
Nicolas
> ---
> Tested on a Rockchip RK3588 (Rock 5B) board with Fluster:
> MPEG-2 (MPEG2_VIDEO-MAIN): 23/43, unchanged
>
> drivers/media/platform/verisilicon/hantro_g1_mpeg2_dec.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/media/platform/verisilicon/hantro_g1_mpeg2_dec.c b/drivers/media/platform/verisilicon/hantro_g1_mpeg2_dec.c
> index e0d6bd0a6e44..6a942f4b8a2d 100644
> --- a/drivers/media/platform/verisilicon/hantro_g1_mpeg2_dec.c
> +++ b/drivers/media/platform/verisilicon/hantro_g1_mpeg2_dec.c
> @@ -161,8 +161,13 @@ int hantro_g1_mpeg2_dec_run(struct hantro_ctx *ctx)
>
> seq = hantro_get_ctrl(ctx,
> V4L2_CID_STATELESS_MPEG2_SEQUENCE);
> + if (WARN_ON(!seq))
> + return -EINVAL;
> +
> pic = hantro_get_ctrl(ctx,
> V4L2_CID_STATELESS_MPEG2_PICTURE);
> + if (WARN_ON(!pic))
> + return -EINVAL;
>
> reg = G1_REG_DEC_AXI_RD_ID(0) |
> G1_REG_DEC_TIMEOUT_E(1) |
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-08-10 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 14:07 Tharit Tangkijwanichakul
2026-08-10 14:09 ` Nicolas Dufresne [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=2a5abb0004aa453c2f985aff41c72d4952006fc9.camel@collabora.com \
--to=nicolas.dufresne@collabora.com \
--cc=benjamin.gaignard@collabora.com \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=hverkuil@kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=jkoolstra@xs4all.nl \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=me@brighamcampbell.com \
--cc=p.zabel@pengutronix.de \
--cc=skhan@linuxfoundation.org \
--cc=tharitt97@gmail.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
Powered by JetHome