From: xjdeng <micro6947-at-gmail.com@ffmpeg.org> To: ffmpeg-devel@ffmpeg.org Cc: xjdeng <micro6947@gmail.com> Subject: [FFmpeg-devel] [PATCH] libavcodec/utils: Ensure allocated buffer is zero-initialized Date: Thu, 26 Jun 2025 12:07:07 +0800 Message-ID: <20250626040707.1295-1-micro6947@gmail.com> (raw) In `av_fast_padded_mallocz`, the allocated buffer's zero-initialization is not guaranteed. This is because it calls `av_fast_malloc`, which in turn calls `fast_malloc` with `zero_realloc=0`. Consequently, the memory returned by the underlying `av_malloc` (used within `fast_malloc`) is not guaranteed to be zero-initialized. Furthermore, if `*size` is adjusted to be greater than `min_size + AV_INPUT_BUFFER_PADDING_SIZE`, the subsequent `memset` operation will not cover the entire allocated buffer, leaving a portion of it uninitialized. To ensure the entire allocated buffer is properly zero-initialized, we should use `FFMAX` to adjust the `memset` range. Signed-off-by: xjdeng <micro6947@gmail.com> --- libavcodec/utils.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libavcodec/utils.c b/libavcodec/utils.c index f2686b6863..e2afce71ef 100644 --- a/libavcodec/utils.c +++ b/libavcodec/utils.c @@ -72,8 +72,8 @@ void av_fast_padded_mallocz(void *ptr, unsigned int *size, size_t min_size) return; } av_fast_malloc(p, size, min_size + AV_INPUT_BUFFER_PADDING_SIZE); - if (*p) - memset(*p, 0, min_size + AV_INPUT_BUFFER_PADDING_SIZE); + if (*p) + memset(*p, 0, FFMAX(*size, min_size + AV_INPUT_BUFFER_PADDING_SIZE)); } int av_codec_is_encoder(const AVCodec *avcodec) -- 2.27.0.windows.1 _______________________________________________ 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 reply other threads:[~2025-06-26 4:07 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-26 4:07 xjdeng [this message] 2025-06-26 14:07 ` Zhao Zhili
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=20250626040707.1295-1-micro6947@gmail.com \ --to=micro6947-at-gmail.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=micro6947@gmail.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