From: Ard Biesheuvel via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Ard Biesheuvel <ardb@google.com>
Subject: [FFmpeg-devel] Re: [PATCH] avcodec/adpcm: fix heap-buffer-overflow in IMA MAGIX decoding
Date: Wed, 11 Feb 2026 10:20:02 +0100
Message-ID: <CAGnOC3Yfc0Dpx1g4YrjH2SXy-xXUBhOHOkikp9d2MqOXjyY7kQ@mail.gmail.com> (raw)
In-Reply-To: <20260211082848.638506-1-ardb+git@google.com>
L.S.,
On Wed, Feb 11, 2026 at 9:28 AM Ard Biesheuvel <ardb+git@google.com> wrote:
>
> From: Ard Biesheuvel <ardb@google.com>
>
This message is a duplicate and may be disregarded - due to poor
coordination between my colleague and myself (mea culpa), we ended up
sending the same patch twice, via different channels.
Please refer to this version instead:
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21730
> The IMA MAGIX decoder calculates the output buffer size (nb_samples)
> based on the actual input packet size (buf_size) via get_nb_samples().
> However, the decoding loop previously relied on avctx->block_align to
> determine the iteration count.
>
> When block_align is larger than the actual packet size (e.g., a 71-byte
> packet with block_align=16384), the loop attempts to process more data
> than available. This results in out-of-bounds reads from the input
> bytestream and out-of-bounds writes to the allocated output buffer.
>
> Fix this by adding a check for remaining input bytes (>= 8) to the loop
> condition, ensuring the loop terminates when the input is exhausted.
>
> oss-fuzz: https://oss-fuzz.com/testcase-detail/4847227777646592
> Co-authored-by: CodeMender <codemender-patching@google.com>
> Signed-off-by: Ard Biesheuvel <ardb@google.com>
> ---
> libavcodec/adpcm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavcodec/adpcm.c b/libavcodec/adpcm.c
> index bd9ad2933f..2828cb8c31 100644
> --- a/libavcodec/adpcm.c
> +++ b/libavcodec/adpcm.c
> @@ -1799,7 +1799,7 @@ static int adpcm_decode_frame(AVCodecContext *avctx, AVFrame *frame,
> }
> }
>
> - for (int m = 0; m < avctx->block_align-8; m += 8) {
> + for (int m = 0; m < avctx->block_align-8 && bytestream2_get_bytes_left(&gb) >= 8; m += 8) {
> uint32_t v0 = bytestream2_get_le32u(&gb);
> uint32_t v1 = bytestream2_get_le32u(&gb);
>
> --
> 2.53.0.239.g8d8fc8a987-goog
>
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2026-02-11 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 8:28 [FFmpeg-devel] " Ard Biesheuvel via ffmpeg-devel
2026-02-11 9:20 ` Ard Biesheuvel via ffmpeg-devel [this message]
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=CAGnOC3Yfc0Dpx1g4YrjH2SXy-xXUBhOHOkikp9d2MqOXjyY7kQ@mail.gmail.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=ardb@google.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