Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: usepgp via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: usepgp <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH] Fix flacdec int overflow with a saturated add (PR #20900)
Date: Wed, 12 Nov 2025 17:48:49 -0000
Message-ID: <176296973017.25.8332553935218562573@2cb04c0e5124> (raw)

PR #20900 opened by usepgp
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20900
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20900.patch

A chromium fuzzer identified this potential UB int overflow.


>From d55c6e8a2c49319eb779ec795fdd657cbc524fc7 Mon Sep 17 00:00:00 2001
From: Ted Meyer <tmathmeyer@chromium.org>
Date: Wed, 15 Oct 2025 14:00:18 -0700
Subject: [PATCH] Fix flacdec int overflow with a saturated add

A chromium fuzzer identified this.
---
 libavformat/flacdec.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libavformat/flacdec.c b/libavformat/flacdec.c
index e80b49307d..219bc4e416 100644
--- a/libavformat/flacdec.c
+++ b/libavformat/flacdec.c
@@ -47,7 +47,7 @@ static void reset_index_position(int64_t metadata_head_size, AVStream *st)
     FFStream *const sti = ffstream(st);
     /* the real seek index offset should be the size of metadata blocks with the offset in the frame blocks */
     for (int i = 0; i < sti->nb_index_entries; i++)
-        sti->index_entries[i].pos += metadata_head_size;
+        sti->index_entries[i].pos = av_sat_add64(sti->index_entries[i].pos, metadata_head_size);
 }
 
 static const uint16_t sr_table[16] = {
-- 
2.49.1

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

                 reply	other threads:[~2025-11-12 17:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=176296973017.25.8332553935218562573@2cb04c0e5124 \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=code@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