From: Nuo Mi <nuomi2021-at-gmail.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] avcodec/vvc/dec: fix possible null-pointer dereference Date: Thu, 12 Jun 2025 21:22:40 +0800 Message-ID: <CAFXK13epM98U_xPOfHjC2jgi7aSKRP9S59UczRRMhB515LKSVQ@mail.gmail.com> (raw) In-Reply-To: <20250611175329.90644-1-epirat07@gmail.com> On Thu, Jun 12, 2025 at 1:53 AM Marvin Scholz < epirat07-at-gmail.com@ffmpeg.org> wrote: > When checking for filmgrain here, needs_fg can be true even when > film_grain_characteristics is NULL (when aom_film_grain.enable is true), > therefore this check could end up dereferencing film_grain_characteristics > even though it is NULL. > > Fix CID 1648347 > Thank you, Marvin. Pushed. > --- > libavcodec/vvc/dec.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/libavcodec/vvc/dec.c b/libavcodec/vvc/dec.c > index aba31b94fe..7930d64a05 100644 > --- a/libavcodec/vvc/dec.c > +++ b/libavcodec/vvc/dec.c > @@ -770,7 +770,8 @@ static int check_film_grain(VVCContext *s, > VVCFrameContext *fc) > !s->avctx->hwaccel; > > if (fc->ref->needs_fg && > - (fc->sei.common.film_grain_characteristics->present && > + (fc->sei.common.film_grain_characteristics && > + fc->sei.common.film_grain_characteristics->present && > > !ff_h274_film_grain_params_supported(fc->sei.common.film_grain_characteristics->model_id, > fc->ref->frame->format) || > !av_film_grain_params_select(fc->ref->frame))) { > -- > 2.39.5 (Apple Git-154) > > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe". > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2025-06-12 13:23 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-11 17:53 Marvin Scholz 2025-06-12 13:22 ` Nuo Mi [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=CAFXK13epM98U_xPOfHjC2jgi7aSKRP9S59UczRRMhB515LKSVQ@mail.gmail.com \ --to=nuomi2021-at-gmail.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git