Answer in brief
CVE-2026-74454 records a Unknown severity vulnerability in drm/vc4: Supply the overflow slot size in BPOS, not the whole bin BO size. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <2f2291a119e9a8b696ae8bb36e86b75d272ceaea || >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <0badb30871004d34df87be33e853536f0b69885f || >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <6cd5acf6f87c073622bd61e38fe99c47365cda9c || >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <1e33ca7f44be64beed2735bb76b86eb65ba8c05b || >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <6395789e4739aa5177bbec0fa0f07ccc38d249b0 | 2f2291a119e9a8b696ae8bb36e86b75d272ceaea, 0badb30871004d34df87be33e853536f0b69885f, 6cd5acf6f87c073622bd61e38fe99c47365cda9c, 1e33ca7f44be64beed2735bb76b86eb65ba8c05b, 6395789e4739aa5177bbec0fa0f07ccc38d249b0 |
| Linux/Linuxgeneric | 4.13 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74454 records a Unknown severity vulnerability in drm/vc4: Supply the overflow slot size in BPOS, not the whole bin BO size. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <2f2291a119e9a8b696ae8bb36e86b75d272ceaea || >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <0badb30871004d34df87be33e853536f0b69885f || >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <6cd5acf6f87c073622bd61e38fe99c47365cda9c || >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <1e33ca7f44be64beed2735bb76b86eb65ba8c05b || >=553c942f8b2cbc7394b4d4fa2f848b23a8f07451 <6395789e4739aa5177bbec0fa0f07ccc38d249b0 | 2f2291a119e9a8b696ae8bb36e86b75d272ceaea, 0badb30871004d34df87be33e853536f0b69885f, 6cd5acf6f87c073622bd61e38fe99c47365cda9c, 1e33ca7f44be64beed2735bb76b86eb65ba8c05b, 6395789e4739aa5177bbec0fa0f07ccc38d249b0 |
| Linux/Linuxgeneric | 4.13 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.