# CVE-2026-23468: drm/amdgpu: Limit BO list entry count to prevent resource exhaustion

> A local attacker can cause resource exhaustion and denial of service in the Linux kernel by submitting excessive buffer object list entries to the amdgpu driver.

- **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:** 3 Apr 2026
- **Updated:** 1 Jun 2026
- **Also known as:** AZL-81840, BELL-CVE-2026-23468, DEBIAN-CVE-2026-23468, GHSA-mgj5-5f6h-8742, ROOT-OS-DEBIAN-11-CVE-2026-23468, ROOT-OS-DEBIAN-12-CVE-2026-23468, ROOT-OS-DEBIAN-13-CVE-2026-23468, ROOT-OS-UBUNTU-2204-CVE-2026-23468, ROOT-OS-UBUNTU-2404-CVE-2026-23468, UBUNTU-CVE-2026-23468

## What is CVE-2026-23468?

CVE-2026-23468 is a medium-severity denial of service vulnerability in Linux kernel, published on 3 Apr 2026. 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/amdgpu: Limit BO list entry count to prevent resource exhaustion

Userspace can pass an arbitrary number of BO list entries via the
bo_number field. Although the previous multiplication overflow check
prevents out-of-bounds allocation, a large number of entries could still
cause excessive memory allocation (up to potentially gigabytes) and
unnecessarily long list processing times.

Introduce a hard limit of 128k entries per BO list, which is more than
sufficient for any realistic use case (e.g., a single list containing all
buffers in a large scene). This prevents memory exhaustion attacks and
ensures predictable performance.

Return -EINVAL if the requested entry count exceeds the limit

(cherry picked from commit 688b87d39e0aa8135105b40dc167d74b5ada5332)

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-23468?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-23468?

Apply the vendor's patch.

## Is CVE-2026-23468 being exploited?

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

What it is: CVE-2026-23468 is a medium-severity denial of service vulnerability in Linux kernel, published on 3 Apr 2026. 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-2026-23468 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-2026-23468/ (Markdown: https://insights.sbomify.com/CVE-2026-23468/index.md)
```

## Sources

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

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