From: Hans Verkuil <hverkuil+cisco@kernel.org>
To: Soham Kute <officialsohamkute@gmail.com>,
dwlsalmeida@gmail.com, mchehab@kernel.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [PATCH v2] media: vidtv: fix general protection fault in vidtv_psi_ts_psi_write_into
Date: Mon, 16 Mar 2026 14:33:48 +0100 [thread overview]
Message-ID: <16ac1516-781a-4cff-812f-59a30b15bb79@kernel.org> (raw)
In-Reply-To: <20260207203947.4354-1-officialsohamkute@gmail.com>
Hi Soham,
On 07/02/2026 21:39, Soham Kute wrote:
> Add defensive validation for psi_write_args pointers to avoid
> null pointer dereference reported by syzbot.
>
> Reported-by: syzbot+814c351d094f41a1b86@syzkaller.appspotmail.com
I can't find any report with this hash from syzbot.
Can you point me to the correct syzbot report?
>
> Signed-off-by: Soham Kute <officialsohamkute@gmail.com>
> ---
> drivers/media/test-drivers/vidtv/vidtv_psi.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/media/test-drivers/vidtv/vidtv_psi.c b/drivers/media/test-drivers/vidtv/vidtv_psi.c
> index 2a51c898c..bac0ea03b 100644
> --- a/drivers/media/test-drivers/vidtv/vidtv_psi.c
> +++ b/drivers/media/test-drivers/vidtv/vidtv_psi.c
> @@ -156,7 +156,13 @@ static void vidtv_psi_set_sec_len(struct vidtv_psi_table_header *h, u16 new_len)
> * add stuffing (i.e. padding bytes) after the CRC
> */
> static u32 vidtv_psi_ts_psi_write_into(struct psi_write_args *args)
> -{
> +{
> + if (!args || !args->dest_buf || !args->from ||
> + !args->continuity_counter) {
> + pr_warn_once("%s: invalid write arguments\n", __func__);
> + return 0;
> + }
I'm fairly certain you paper over the real bug, which is somewhere else.
The question is where the NULL pointer is exactly and why it is NULL.
Without the syzbot report I have no idea.
Regards,
Hans
> +
> struct vidtv_mpeg_ts ts_header = {
> .sync_byte = TS_SYNC_BYTE,
> .bitfield = cpu_to_be16((args->new_psi_section << 14) | args->pid),
prev parent reply other threads:[~2026-03-16 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 20:39 Soham Kute
2026-02-07 20:41 ` syzbot
2026-03-16 13:33 ` Hans Verkuil [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=16ac1516-781a-4cff-812f-59a30b15bb79@kernel.org \
--to=hverkuil+cisco@kernel.org \
--cc=dwlsalmeida@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=officialsohamkute@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