From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] fftools/ffmpeg_mux_init: fix a memory leak in ffmpeg_mux_init.c Date: Fri, 12 Apr 2024 10:41:25 -0300 Message-ID: <405113c3-a170-4a69-9b20-3a98292f6b60@gmail.com> (raw) In-Reply-To: <20240412130935.1368867-1-lumingyindetect@163.com> On 4/12/2024 10:09 AM, LuMingYin wrote: > In the file ffmpeg_mux_init.c located at /FFmpeg/fftools/, a pointer variable named pts is defined at line 2830. At line 2836, this pointer is allocated a dynamic memory area using the function av_malloc_array. When the if statement at line 2852 evaluates to true, there are two possible scenarios. The first scenario is when nb_ch > INT_MAX - size. In this case, the program should release the dynamic memory area pointed to by pts before returning. The second scenario is when the realloc operation for the pts pointer fails. In this case, since the av_realloc_f function releases the original memory in case of reallocation failure, there is no need to release the memory area pointed to by pts. Because the handling of these two scenarios differs, to fix the memory leak issue caused by the first scenario, my patch separates the treatment of these cases. > > Signed-off-by: LuMingYin <lumingyindetect@163.com> > --- > fftools/ffmpeg_mux_init.c | 8 ++++++-- > 1 file changed, 6 insertions(+), 2 deletions(-) > > diff --git a/fftools/ffmpeg_mux_init.c b/fftools/ffmpeg_mux_init.c > index 6d8bd5bcdf..1f27e4e4f4 100644 > --- a/fftools/ffmpeg_mux_init.c > +++ b/fftools/ffmpeg_mux_init.c > @@ -2849,8 +2849,12 @@ static int parse_forced_key_frames(void *log, KeyframeForceCtx *kf, > unsigned int nb_ch = mux->fc->nb_chapters; > int j; > > - if (nb_ch > INT_MAX - size || > - !(pts = av_realloc_f(pts, size += nb_ch - 1, > + if (nb_ch > INT_MAX - size) { > + av_freep(&pts); > + return AVERROR(ENOMEM); There's a fail label at the end that frees pts. You should set ret to AVERROR(ENOMEM) and goto it. An alternative could be something like > diff --git a/fftools/ffmpeg_mux_init.c b/fftools/ffmpeg_mux_init.c > index 1d0a210450..0d93f0eff2 100644 > --- a/fftools/ffmpeg_mux_init.c > +++ b/fftools/ffmpeg_mux_init.c > @@ -2959,10 +2959,11 @@ static int parse_forced_key_frames(void *log, KeyframeForceCtx *kf, > unsigned int nb_ch = mux->fc->nb_chapters; > int j; > > - if (nb_ch > INT_MAX - size || > - !(pts = av_realloc_f(pts, size += nb_ch - 1, > - sizeof(*pts)))) > - return AVERROR(ENOMEM); > + if (nb_ch > (INT_MAX - size) / sizeof(*pts) || > + av_reallocp(&pts, (size += nb_ch - 1) * sizeof(*pts))) { > + ret = AVERROR(ENOMEM); > + goto fail; > + } > > if (p[8]) { > ret = av_parse_time(&t, p + 8, 1); Where av_reallocp() will set pts to NULL after freeing, so the free in the fail label will be a no-op, and we always jump to fail on failure in case it's extended to do further cleaning. _______________________________________________ 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".
next prev parent reply other threads:[~2024-04-12 13:41 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-12 13:09 LuMingYin 2024-04-12 13:41 ` James Almer [this message] 2024-04-12 16:51 ` lumingyindetect 2024-04-13 2:37 LuMingYin
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=405113c3-a170-4a69-9b20-3a98292f6b60@gmail.com \ --to=jamrial@gmail.com \ --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