From: Tong Wu via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> To: ffmpeg-devel@ffmpeg.org Cc: Tong Wu <code@ffmpeg.org> Subject: [FFmpeg-devel] [PATCH] avcodec/vaapi_encode: avoid potential overflow (PR #20421) Message-ID: <175694010490.25.8169504599751349776@463a07221176> (raw) PR #20421 opened by Tong Wu (tong1wu) URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20421 Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20421.patch The max_frame_size in byte will be filled in VAEncMiscParameterBufferMaxFrameSize which receives size in bit. This requires max_frame_size * 8. Signed-off-by: Tong Wu <wutong1208@outlook.com> >From 971e1dec185529f05f33076c2b6eb1b1210b91e1 Mon Sep 17 00:00:00 2001 From: Tong Wu <wutong1208@outlook.com> Date: Thu, 4 Sep 2025 06:51:24 +0800 Subject: [PATCH] avcodec/vaapi_encode: avoid potential overflow The max_frame_size in byte will be filled in VAEncMiscParameterBufferMaxFrameSize which receives size in bit. This requires max_frame_size * 8. Signed-off-by: Tong Wu <wutong1208@outlook.com> --- libavcodec/vaapi_encode.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavcodec/vaapi_encode.h b/libavcodec/vaapi_encode.h index 8e3eab9f27..1fa1e99a31 100644 --- a/libavcodec/vaapi_encode.h +++ b/libavcodec/vaapi_encode.h @@ -360,7 +360,7 @@ int ff_vaapi_encode_close(AVCodecContext *avctx); { "max_frame_size", \ "Maximum frame size (in bytes)",\ OFFSET(common.max_frame_size), AV_OPT_TYPE_INT, \ - { .i64 = 0 }, 0, INT_MAX, FLAGS } + { .i64 = 0 }, 0, INT_MAX / 8, FLAGS } #define VAAPI_ENCODE_RC_MODE(name, desc) \ { #name, desc, 0, AV_OPT_TYPE_CONST, { .i64 = RC_MODE_ ## name }, \ -- 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-09-03 22:56 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=175694010490.25.8169504599751349776@463a07221176 \ --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