From: Ted Meyer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Ted Meyer <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PR] Fix out-of-bounds av_freep call in stsd parser (PR #21641)
Date: Wed, 04 Feb 2026 00:39:51 -0000
Message-ID: <177016559194.25.9838724582723861250@4457048688e7> (raw)
PR #21641 opened by Ted Meyer (usepgp)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21641
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21641.patch
`sc->stsd_count` can exceed `entries` if in ff_mov_read_stsd_entries
there are multiple skipped stsd blocks. In this case, the `stsd_count`
can get incremented too far, and when failure occurs, an OOB free
happens.
>From 0eb0d70175402e987a03f93ffe1191aa77f81ba6 Mon Sep 17 00:00:00 2001
From: Ted Meyer <tmathmeyer@chromium.org>
Date: Tue, 3 Feb 2026 16:31:50 -0800
Subject: [PATCH] Fix out-of-bounds av_freep call in stsd parser
`sc->stsd_count` can exceed `entries` if in ff_mov_read_stsd_entries
there are multiple skipped stsd blocks. In this case, the `stsd_count`
can get incremented too far, and when failure occurs, an OOB free
happens.
---
libavformat/mov.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavformat/mov.c b/libavformat/mov.c
index d19b213ffa..4deb76d37c 100644
--- a/libavformat/mov.c
+++ b/libavformat/mov.c
@@ -3254,7 +3254,7 @@ static int mov_read_stsd(MOVContext *c, AVIOContext *pb, MOVAtom atom)
fail:
if (sc->extradata) {
int j;
- for (j = 0; j < sc->stsd_count; j++)
+ for (j = 0; j < entries; j++)
av_freep(&sc->extradata[j]);
}
--
2.52.0
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2026-02-04 0:40 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=177016559194.25.9838724582723861250@4457048688e7 \
--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