# CVE-2026-74454: drm/vc4: Supply the overflow slot size in BPOS, not the whole bin BO size

> A Linux kernel DRM bug allows GPU DMA to corrupt arbitrary memory, potentially leading to code execution or system crashes.

- **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:** 15 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** AZL-96162, BELL-CVE-2026-74454, DEBIAN-CVE-2026-74454, GHSA-c238-677w-2p87, UBUNTU-CVE-2026-74454

## What is CVE-2026-74454?

CVE-2026-74454 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 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/vc4: Supply the overflow slot size in BPOS, not the whole bin BO size

vc4_overflow_mem_work() points BPOA at a 512KB slot inside the 16MB
binner BO, but writes the size of the whole BO to BPOS. On every binner
out-of-memory event the PTB is therefore authorized to write tile lists
across all the other slots (which may hold the tile state, tile alloc and
overflow memory of in-flight jobs) and, for any slot but the first, past
the end of the binner BO into unrelated CMA memory.

Since CMA pages are recycled into page cache and user allocations, this
is arbitrary memory corruption by GPU DMA. In practice it shows up as GPU
hangs with corrupted control list pointers, userspace heap corruption, a
GPU that stays permanently wedged after the first hang, and occasional
full system crashes, whenever a job overflows the initial binner slot.

The bug dates back to the conversion from a dedicated overflow BO (where
writing the full BO size was correct) to the slotted binner BO.

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


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

Apply the vendor's patch.

## Is CVE-2026-74454 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74454 and fix it if it is affected.

What it is: CVE-2026-74454 is a high-severity memory corruption vulnerability in Linux, published on 15 Aug 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-74454 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-2026-74454/ (Markdown: https://insights.sbomify.com/CVE-2026-74454/index.md)
```

## Sources

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

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