Answer in brief
CVE-2026-74447 records a High severity (CVSS 7.8) vulnerability in drm/amdkfd: fix uint32_t overflow in EOP ring buffer size alignment. 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.
CVSS is 7.8. 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 | >=ee0dc6c66a913260311876a4b2b53fe0b9bc3f94 <273548eb997c6be85230c1236b18784b09f6203c || >=acfc84cfa70aca5b970faf152979bc97b9f8b0c0 <6dc0b4b39ed4f11ef70f76ecea8537e35f45342b || >=42ea9cf2f16b7131cb7302acb3dac510968f8bdc <7c54bd225d83bc1bcb44430ed4b4d3a5c36b1961 || >=42ea9cf2f16b7131cb7302acb3dac510968f8bdc <83463a96ea3c7d8ae636a4d6a0ba63c9ce410724 || c6ce687077cc67e4f3cbd0c89cb356fbbce91f4c || >=6.12.75 <6.12.103 || >=6.18.16 <6.18.44 || >=6.19.6 <6.20 | 273548eb997c6be85230c1236b18784b09f6203c, 6dc0b4b39ed4f11ef70f76ecea8537e35f45342b, 7c54bd225d83bc1bcb44430ed4b4d3a5c36b1961, 83463a96ea3c7d8ae636a4d6a0ba63c9ce410724, 6.12.103, 6.18.44, 6.20 |
| Linux/Linuxgeneric | 7.0 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 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/amdkfd: fix uint32_t overflow in EOP ring buffer size alignment eop_ring_buffer_size in struct queue_properties is a u32. In kfd_queue_acquire_buffers() the expected EOP buffer size is computed as ALIGN(eop_ring_buffer_size, PAGE_SIZE); ALIGN uses typeof(x), so the addition is done in 32-bit. A user-supplied size of 0xFFFFF001 wraps to 0, causing kfd_queue_buffer_get() to skip its exact-size check (gated on size != 0) and accept any BO mapped at the address. On GFX8/GFX9 the MQD cp_hqd_eop_control is then programmed for an 8KB EOP ring backed by a 4KB BO, so CP EOP writes can land past the buffer and fault the GPU. Cast the operand to u64 so the alignment is computed in 64-bit; the size check in kfd_queue_buffer_get() then rejects the oversized request. (cherry picked from commit ae443117b742c357bfef3a7bddabf76fcf86e9ef)
Quoted source text, attributed separately from HOL analysis.