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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade aom | Aug 22, 2024 | Jun 5, 2024 |
| Debian | — | Upgrade aom | Aug 22, 2024 | Jun 5, 2024 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Jun 5, 2024 |
| Suse | — | Upgrade libaom3Upgrade libaom-develUpgrade libaom-devel-docUpgrade aom-toolsUpgrade libaom0Upgrade libaom3-32bit | Jun 17, 2024 | Jun 5, 2024 |
| Ubuntu | — | Upgrade libaom3Upgrade libaom-devUpgrade aom-toolsUpgrade libaom0 | Jun 7, 2024 | Jun 5, 2024 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub