# CVE-2023-6879: heap buffer overflow in libaom > A heap buffer overflow in libaom during multi-threaded encoding allows attackers to execute arbitrary code or cause denial of service. - **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 27 Dec 2023 - **Updated:** 23 Jun 2026 - **Also known as:** AZL-62423, BELL-CVE-2023-6879, DEBIAN-CVE-2023-6879, ECHO-6b7d-5ca9-c352, GHSA-fvcr-3mhq-rw2x, ROOT-OS-DEBIAN-11-CVE-2023-6879, ROOT-OS-DEBIAN-12-CVE-2023-6879, SUSE-SU-2024:0517-1, SUSE-SU-2024:4333-1, UBUNTU-CVE-2023-6879 ## What is CVE-2023-6879? CVE-2023-6879 is a critical memory corruption vulnerability in Fedoraproject Fedora, published on 27 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Increasing the resolution of video frames, while performing a multi-threaded encode, can result in a heap overflow in av1_loop_restoration_dealloc(). Weakness: CWE-787 (Out-of-bounds Write), CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2023-6879? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libaom` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 3.7.1-150400.3.9.1 | | `libaom-devel-doc` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 3.7.1-150400.3.9.1 | | `libyuv` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 20230517+a377993-150400.9.3.1 | | `libaom` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 3.7.1-150400.3.9.1 | | `libaom-devel-doc` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 3.7.1-150400.3.9.1 | | `libyuv` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 20230517+a377993-150400.9.3.1 | | `libaom` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 3.2.0-150400.3.3.1 | | `libaom` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 3.7.1-150400.3.9.1 | | `libaom-devel-doc` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 3.7.1-150400.3.9.1 | | `libyuv` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 20230517+a377993-150400.9.3.1 | | `libaom` | SUSE:Linux Enterprise Real Time 15 SP4 | All versions | 3.2.0-150400.3.3.1 | | `libaom` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 3.7.1-150400.3.9.1 | | `libaom-devel-doc` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 3.7.1-150400.3.9.1 | | `libyuv` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 20230517+a377993-150400.9.3.1 | | `libaom` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 3.7.1-150400.3.9.1 | | `libaom-devel-doc` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 3.7.1-150400.3.9.1 | | `libyuv` | SUSE:Linux Enterprise Server for SAP Applications 15 SP4 | All versions | 20230517+a377993-150400.9.3.1 | | `libaom` | SUSE:Manager Proxy 4.3 | All versions | 3.7.1-150400.3.9.1 | | `libaom-devel-doc` | SUSE:Manager Proxy 4.3 | All versions | 3.7.1-150400.3.9.1 | | `libyuv` | SUSE:Manager Proxy 4.3 | All versions | 20230517+a377993-150400.9.3.1 | | `libaom` | SUSE:Manager Server 4.3 | All versions | 3.7.1-150400.3.9.1 | | `libaom-devel-doc` | SUSE:Manager Server 4.3 | All versions | 3.7.1-150400.3.9.1 | | `libyuv` | SUSE:Manager Server 4.3 | All versions | 20230517+a377993-150400.9.3.1 | | `libaom` | openSUSE:Leap 15.5 | All versions | 3.2.0-150400.3.3.1 | | `libaom` | openSUSE:Leap 15.5 | All versions | 3.7.1-150400.3.9.1 | | `libaom-devel-doc` | openSUSE:Leap 15.5 | All versions | 3.7.1-150400.3.9.1 | | `libyuv` | openSUSE:Leap 15.5 | All versions | 20230517+a377993-150400.9.3.1 | Products: Aomedia Aomedia, Fedoraproject Fedora. ## How do I fix CVE-2023-6879? Apply the vendor's patch. ## Is CVE-2023-6879 being exploited? There is no known exploitation of CVE-2023-6879 in the wild and no public exploit code. ## Other vulnerabilities in Fedoraproject Fedora - [CVE-2021-30475](https://insights.sbomify.com/CVE-2021-30475/): Memory corruption in n/a (critical 9.8) - [CVE-2021-30474](https://insights.sbomify.com/CVE-2021-30474/): Use after free in n/a (critical 9.8) - [CVE-2021-30473](https://insights.sbomify.com/CVE-2021-30473/): Use after free in n/a (critical 9.8) - [CVE-2020-36129](https://insights.sbomify.com/CVE-2020-36129/): Memory corruption in n/a (high 8.8) - [CVE-2020-36131](https://insights.sbomify.com/CVE-2020-36131/): Memory corruption in n/a (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-6879 and fix it if it is affected. What it is: CVE-2023-6879 is a critical memory corruption vulnerability in Fedoraproject Fedora, published on 27 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-6879 in the wild and no public exploit code. Affected product: Fedoraproject Fedora. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-6879/ (Markdown: https://insights.sbomify.com/CVE-2023-6879/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-6879 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-6879 - OSV: https://osv.dev/vulnerability/CVE-2023-6879 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-6879/ Summaries are generated and may contain mistakes; the official description above is the record.