[FFmpeg-devel] [libav-devel] [PATCH] vp8: check for too large dimensions

Andreas Cadhalpun andreas.cadhalpun at googlemail.com
Sun Jun 7 20:35:18 CEST 2015

Hi Ronald,

On 07.06.2015 19:37, Ronald S. Bultje wrote:
> On Sun, Jun 7, 2015 at 12:44 PM, Andreas Cadhalpun <
> andreas.cadhalpun at googlemail.com> wrote:
>> On 07.06.2015 17:52, Ronald S. Bultje wrote:
>>> We can't simply claim that 8k is not a valid dimension, that would make us
>>> a vp8-incompatible decoder if vp8 stream dimensions are allowed to be
>>> 8k.
>>> This could particularly happen in images (webp).
>> I'd change the error to AVERROR_PATCHWELCOME as Michael suggested, so feel
>> free to fix this limitation. ;)
> No, no, not so easy. For example, keyframes (like webp) would decode just
> fine even thougb mvmin/max is broken, so we're causing a regression here of
> something that worked fine before.

Hmm, so maybe the check could be moved to decode_mb_row_no_filter?

> Is this an actual bug? What is the behaviour that you're trying to fix? Is
> this some overflow noticed on some generated/fuzzed bitstream with
> -fsanitize=integer? Or are we decoding a sample differently from libvpx? Or
> something else?

The overflow of mv_max can cause it to be smaller than mv_min, which causes
av_clip to abort for ASSERT_LEVEL >= 2.

Best regards,

More information about the ffmpeg-devel mailing list