Integer overflow in libaom internal function img_alloc_helper can lead to heap buffer overflow. This function can be reached via 3 callers: * Calling aom_img_alloc() with a large value of the d_w, d_h, or align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aom_image_t struct may be invalid. * Calling aom_img_wrap() with a large value of the d_w, d_h, or align parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aom_image_t struct may be invalid. * Calling aom_img_alloc_with_border() with a large value of the d_w, d_h, align, size_align, or border parameter may result in integer overflows in the calculations of buffer sizes and offsets and some fields of the returned aom_image_t struct may be invalid. References: https://issues.chromium.org/issues/332382766
Created aom tracking bugs for this issue: Affects: epel-all [bug 2292397] Created chromium tracking bugs for this issue: Affects: epel-all [bug 2292398] Affects: fedora-all [bug 2292399]
Created aom tracking bugs for this issue: Affects: epel-all [bug 2292400] Created chromium tracking bugs for this issue: Affects: epel-all [bug 2292402] Affects: fedora-all [bug 2292403]