HomeDescription
A heap-buffer-overflow read vulnerability was found in libaom, the reference AV1 codec implementation. A missing bounds check in the SVC (Scalable Video Coding) layer ID control function allows setting a spatial_layer_id exceeding the configured number of layers. This causes an out-of-bounds heap read of approximately 40,728 bytes when computing a layer context array index. An attacker who can influence SVC encoder parameters in a network-facing service could exploit this for information disclosure (heap content leak) or denial of service (segmentation fault from hitting unmapped memory).
PUBLISHED Reserved 2026-06-19 | Published 2026-06-19 | Updated 2026-07-06 | Assigner redhat
HIGH: 7.1CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H
Problem types
Out-of-bounds Read
Product status
Default status
affected
3.14.0-0.1.hum1 (rpm) before *
unaffected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
unaffected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Default status
affected
Timeline
| 2026-06-19: | Reported to Red Hat. |
| 2026-06-19: | Made public. |
Credits
Red Hat would like to thank The FuzzAnything Team (FuzzAnything) for reporting this issue.
References
access.redhat.com/security/cve/CVE-2026-56210 vdb-entry
bugzilla.redhat.com/show_bug.cgi?id=2490801 (RHBZ#2490801) issue-tracking
security.access.redhat.com/...2/vex/2026/cve-2026-56210.json
access.redhat.com/errata/RHSA-2026:30814 vendor-advisory
access.redhat.com/errata/RHSA-2026:30814 (RHSA-2026:30814) vendor-advisory
access.redhat.com/security/cve/CVE-2026-56210 vdb-entry
aomedia.googlesource.com/aom/+/a93ba0ffaa
bugzilla.redhat.com/show_bug.cgi?id=2490801 (RHBZ#2490801) issue-tracking
issues.chromium.org/issues/503975732
cve.org (CVE-2026-56210)
nvd.nist.gov (CVE-2026-56210)
Download JSON