# CVE-2024-49970: drm/amd/display: Implement bounds check for stream encoder creation in DCN401

> An out-of-bounds write in the AMD display driver allows attackers to cause memory corruption, potentially leading to code execution or system crashes.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 21 Oct 2024
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-51850, AZL-51852, BELL-CVE-2024-49970, DEBIAN-CVE-2024-49970, GHSA-w7w7-6353-385q, ROOT-OS-DEBIAN-11-CVE-2024-49970, ROOT-OS-DEBIAN-12-CVE-2024-49970, ROOT-OS-UBUNTU-2204-CVE-2024-49970, ROOT-OS-UBUNTU-2404-CVE-2024-49970, UBUNTU-CVE-2024-49970

## What is CVE-2024-49970?

CVE-2024-49970 is a medium-severity memory corruption vulnerability in Linux kernel, published on 21 Oct 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:

drm/amd/display: Implement bounds check for stream encoder creation in DCN401

'stream_enc_regs' array is an array of dcn10_stream_enc_registers
structures. The array is initialized with four elements, corresponding
to the four calls to stream_enc_regs() in the array initializer. This
means that valid indices for this array are 0, 1, 2, and 3.

The error message 'stream_enc_regs' 4 <= 5 below, is indicating that
there is an attempt to access this array with an index of 5, which is
out of bounds. This could lead to undefined behavior

Here, eng_id is used as an index to access the stream_enc_regs array. If
eng_id is 5, this would result in an out-of-bounds access on the
stream_enc_regs array.

Thus fixing Buffer overflow error in dcn401_stream_encoder_create

Found by smatch:
drivers/gpu/drm/amd/amdgpu/../display/dc/resource/dcn401/dcn401_resource.c:1209 dcn401_stream_encoder_create() error: buffer overflow 'stream_enc_regs' 4 <= 5

Weakness: CWE-129 (Improper Validation of Array Index)

## Which versions are affected by CVE-2024-49970?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-49970?

Apply the vendor's patch.

## Is CVE-2024-49970 being exploited?

There is no known exploitation of CVE-2024-49970 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-2024-49970 and fix it if it is affected.

What it is: CVE-2024-49970 is a medium-severity memory corruption vulnerability in Linux kernel, published on 21 Oct 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-2024-49970 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-2024-49970/ (Markdown: https://insights.sbomify.com/CVE-2024-49970/index.md)
```

## Sources

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

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