CVE-2026-74454

drm/vc4: Supply the overflow slot size in BPOS, not the whole bin BO size

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 12:26 PM UTC
Updated: August 19, 2026 at 05:21 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.13 ≤ v < 6.1.1834.13 ≤ v < 6.12.1034.13 ≤ v < 6.18.444.13 ≤ v < 6.6.1514.13 ≤ v < 7.1.84.13 ≤ v < 7.24.13553c942f8b2cbc7394b4d4fa2f848b23a8f07451
Vendor states this is fixed in 0badb30871004d34df87be33e853536f0b69885f (fixed)
Vendor states this is fixed in 1e33ca7f44be64beed2735bb76b86eb65ba8c05b (fixed)
Vendor states this is fixed in 2f2291a119e9a8b696ae8bb36e86b75d272ceaea (fixed)
Vendor states this is fixed in 6395789e4739aa5177bbec0fa0f07ccc38d249b0 (fixed)
Vendor states this is fixed in 6cd5acf6f87c073622bd61e38fe99c47365cda9c (fixed)
Vendor states this is fixed in bb5656ae063f2711f56438cf2f1f5b613aea5f12 (fixed)
Vendor states this is fixed in 4.13 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card