# CVE-2023-52916: media: aspeed: Fix memory overwrite if timing is 1600x900

> A memory overwrite in the Linux kernel's Aspeed media driver can cause a system crash when capturing 1600x900 video under tight memory conditions.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Sep 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2023-52916, DEBIAN-CVE-2023-52916, GHSA-722x-w6hg-5675, ROOT-OS-DEBIAN-11-CVE-2023-52916, ROOT-OS-UBUNTU-2204-CVE-2023-52916, UBUNTU-CVE-2023-52916

## What is CVE-2023-52916?

CVE-2023-52916 is a high-severity memory corruption vulnerability in Linux kernel, published on 6 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

media: aspeed: Fix memory overwrite if timing is 1600x900

When capturing 1600x900, system could crash when system memory usage is
tight.

The way to reproduce this issue:
1. Use 1600x900 to display on host
2. Mount ISO through 'Virtual media' on OpenBMC's web
3. Run script as below on host to do sha continuously
  #!/bin/bash
  while [ [1] ];
  do
	find /media -type f -printf '"%h/%f"\n' | xargs sha256sum
  done
4. Open KVM on OpenBMC's web

The size of macro block captured is 8x8. Therefore, we should make sure
the height of src-buf is 8 aligned to fix this issue.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2023-52916?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2023-52916?

Apply the vendor's patch.

## Is CVE-2023-52916 being exploited?

There is no known exploitation of CVE-2023-52916 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52916 and fix it if it is affected.

What it is: CVE-2023-52916 is a high-severity memory corruption vulnerability in Linux kernel, published on 6 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52916 in the wild and no public exploit code.

Affected product: Linux kernel. 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-52916/ (Markdown: https://insights.sbomify.com/CVE-2023-52916/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-52916
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-52916
- OSV: https://osv.dev/vulnerability/CVE-2023-52916

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-52916/
Summaries are generated and may contain mistakes; the official description above is the record.