Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Frank Plowman via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Frank Plowman <post@frankplowman.com>
Subject: [FFmpeg-devel] Re: [PATCH] avcodec/vvc: validate reference picture list indices
Date: Tue, 6 Jan 2026 08:47:29 +0000
Message-ID: <7b958c6f-b4f6-4079-94b0-e517cb5b07da@frankplowman.com> (raw)
In-Reply-To: <CAPYFPM0OyhLPfpX6QsMNCYfw27Xf-h1ku6KqdcQ9zCx4OpnS5g@mail.gmail.com>


[-- Attachment #1.1.1.1: Type: text/plain, Size: 1857 bytes --]

On 06/01/2026 07:58, Christophe Gisquet via ffmpeg-devel wrote:
> Hi,
> 
> sorry in advance for any bad formatting in my reply from a phone.
> 
> Le mar. 6 janv. 2026, 03:13, 0xBat via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
> a écrit
> 
>> ---
>>  libavcodec/vvc/ctu.c | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/libavcodec/vvc/ctu.c b/libavcodec/vvc/ctu.c
>> index 18cbe0fe0f..8e4f003886 100644
>> --- a/libavcodec/vvc/ctu.c
>> +++ b/libavcodec/vvc/ctu.c
>> @@ -1287,6 +1287,8 @@ static void derive_mmvd(const VVCLocalContext *lc,
>> MvField *mvf, const Mv *mmvd_
>>      if (mvf->pred_flag == PF_BI) {
>>          const RefPicList *rpl = sc->rpl;
>>          const int poc = lc->fc->ps.ph.poc;
>> +        if (mvf->ref_idx[L0] >= rpl[L0].nb_refs || mvf->ref_idx[L1] >=
>> rpl[L1].nb_refs)
>> +            return;
>>          const int diff[] = {
>>              poc - rpl[L0].refs[mvf->ref_idx[L0]].poc,
>>
> 
> Not a maintainer or contributor to the VVC decoder, but sounds fishy. That
> a ref_idx is invalid, means that wherever it came from didn't validate
> against the RPL. I don't know where mvf comes from, but if that's from the
> current frame, it is extremely weird.
> 
> And by that I mean, the issue sounds like it should be caught earlier to
> avoid it from propagating to other places.
> 
> Regards,
> Christophe
> 

Hi,

Yes I agree with Christophe.  MMVD takes its "base MVs" (what is called
mvf here) from the regular merge list, which is shared with various
other merge modes.  Consequently, if there are invalid MVs in MMVD then
I suspect the issue may be more fundamental and there may be issues with
other merge modes.

I'm guessing you have fuzzed bitstreams which led you to these issues,
would it be possible to share them?

Thanks a lot for your work,
Frank

[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 1091 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

[-- Attachment #2: Type: text/plain, Size: 163 bytes --]

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2026-01-06  8:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05  0:16 [FFmpeg-devel] [PATCH] avcodec/vvc: add boundary checks for CTU table access 0xBat via ffmpeg-devel
2026-01-05  0:16 ` [FFmpeg-devel] [PATCH] avcodec/vvc: clamp palette predictor size 0xBat via ffmpeg-devel
2026-01-05  0:16 ` [FFmpeg-devel] [PATCH] avcodec/vvc: validate reference picture list indices 0xBat via ffmpeg-devel
2026-01-06  7:58   ` [FFmpeg-devel] " Christophe Gisquet via ffmpeg-devel
2026-01-06  8:47     ` Frank Plowman via ffmpeg-devel [this message]
2026-01-06  8:01 ` [FFmpeg-devel] Re: [PATCH] avcodec/vvc: add boundary checks for CTU table access Christophe Gisquet via ffmpeg-devel
2026-01-06 19:35   ` Christophe Gisquet via ffmpeg-devel

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=7b958c6f-b4f6-4079-94b0-e517cb5b07da@frankplowman.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=post@frankplowman.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

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