# CVE-2023-54150: drm/amd: Fix an out of bounds error in BIOS parser

> An out-of-bounds read in the AMD GPU BIOS parser can lead to memory corruption, potentially causing system crashes or arbitrary code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-54150, DEBIAN-CVE-2023-54150, GHSA-g4x6-vrjg-m8w6, UBUNTU-CVE-2023-54150

## What is CVE-2023-54150?

CVE-2023-54150 is a memory corruption vulnerability in Linux, published on 24 Dec 2025. 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: Fix an out of bounds error in BIOS parser

The array is hardcoded to 8 in atomfirmware.h, but firmware provides
a bigger one sometimes. Deferencing the larger array causes an out
of bounds error.

commit 4fc1ba4aa589 ("drm/amd/display: fix array index out of bound error
in bios parser") fixed some of this, but there are two other cases
not covered by it.  Fix those as well.

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


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

Apply the vendor's patch.

## Is CVE-2023-54150 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-54150 is a memory corruption vulnerability in Linux, published on 24 Dec 2025. 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-54150 in the wild and no public exploit code.

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

## Sources

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

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