Home

Description

An arbitrary address write 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 an attacker to inject an arbitrary pointer into the cyclic refresh map field via crafted image pixel values. The encoder then writes approximately 1,200 bytes at the attacker-controlled address. This is fully deterministic and does not require a separate information leak. An attacker who can supply frames to a network-facing libaom encoder with SVC enabled could exploit this for denial of service or potential code execution.

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:N/I:L/A:H

Problem types

Out-of-bounds Write

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-56209 vdb-entry

bugzilla.redhat.com/show_bug.cgi?id=2490800 (RHBZ#2490800) issue-tracking

security.access.redhat.com/...2/vex/2026/cve-2026-56209.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-56209 vdb-entry

aomedia.googlesource.com/aom/+/a93ba0ffaa

bugzilla.redhat.com/show_bug.cgi?id=2490800 (RHBZ#2490800) issue-tracking

issues.chromium.org/issues/503993984

cve.org (CVE-2026-56209)

nvd.nist.gov (CVE-2026-56209)

Download JSON