Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Reaxx via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>,
	Reaxx <cookieandcream560@gmail.com>
Subject: [FFmpeg-devel] Re: [PATCH] avcodec/rv60dec: add upper bound check for qp
Date: Fri, 7 Nov 2025 22:19:27 +0100
Message-ID: <CAJ9qJsvZU2nbZeJJ2Ty-RJiGjJ+Bd4TzFS5YkD_xroe3mLpoXw@mail.gmail.com> (raw)
In-Reply-To: <aQ5hAjwpIJh8Kw-M@neo>

Thanks for reviewing and applying the patch. Apologies for the incorrect
commit message , I appreciate you correcting it. Thanks again

On Fri, 7 Nov 2025 at 22:14, Michael Niedermayer via ffmpeg-devel <
ffmpeg-devel@ffmpeg.org> wrote:

> Hi Reaxx
>
> On Fri, Nov 07, 2025 at 06:20:38PM +0100, Reaxx via ffmpeg-devel wrote:
> > This patch fixes an out-of-bounds read in the RV60 decoder where qp can
> > reach 65, exceeding the rv60_qp_to_idx[64] array bounds. The previous fix
> > (61cbcaf93f) only covered intra frames. This adds validation at the
> source
> > for all frame types.
>
> >  rv60dec.c |    2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 57b6f4d726a8d8959a14807b0fa1fb162ce7bd74
> /var0001-avcodec-rv60dec-add-upper-bound-check-for-qp.patch
> > From c7a4ef1c2d235e73be849028c145949eac6ae9ef Mon Sep 17 00:00:00 2001
> > From: oblivionsage <cookieandcream560@gmail.com>
> > Date: Fri, 7 Nov 2025 18:08:14 +0100
> > Subject: [PATCH] avcodec/rv60dec: add upper bound check for qp
> >
> > The quantization parameter (qp) can exceed 63 when the base value
> > from frame header (0-63) is combined with the offset from slice data
> > (up to +2), resulting in qp=65. This causes out-of-bounds access to
> > the rv60_qp_to_idx[64] array in decode_cbp8(), decode_cbp16(), and
> > get_c4x4_set().
> >
>
> > Previous fix in commit 61cbcaf93f3b2e10124f4c63ce7cd8dad6505fb2 added
> validation only for intra
> > frames at a later stage. This patch adds validation at the source
> > in decode_slice() to prevent invalid qp values for all frame types.
>
> This is not correct, the current code is not just checking qp in the
> intra case
>
>
> >
> > Fixes: Out-of-bounds read reported by OSS-Fuzz
> (clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_RV60_fuzzer-5160167345291264)
>
> This is incorrect, this testcase does not trigger the issue fixed in this
> patch
>
> There is in fact no testcase for the issue this fixes to the best of
> my knowledge.
>
> i will apply this with a corrected commit message
>
> thx
>
>
> [...]
>
> --
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> I have often repented speaking, but never of holding my tongue.
> -- Xenocrates
> _______________________________________________
> ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
> To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
>
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

  reply	other threads:[~2025-11-07 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07 17:20 [FFmpeg-devel] " Reaxx via ffmpeg-devel
2025-11-07 21:13 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-11-07 21:19   ` Reaxx via ffmpeg-devel [this message]
2025-11-07 21:38     ` Michael Niedermayer via ffmpeg-devel
2025-11-07 21:49       ` Reaxx via ffmpeg-devel
2025-11-08  0:21         ` Michael Niedermayer 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=CAJ9qJsvZU2nbZeJJ2Ty-RJiGjJ+Bd4TzFS5YkD_xroe3mLpoXw@mail.gmail.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=cookieandcream560@gmail.com \
    --cc=michael@niedermayer.cc \
    /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