CVE-2026-74447

drm/amdkfd: fix uint32_t overflow in EOP ring buffer size alignment

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 12:26 PM UTC
Updated: October 16, 2026 at 08:17 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%
SSVC
No known exploit

Description

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)

Affected

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

42ea9cf2f16b7131cb7302acb3dac510968f8bdc6.12.756.18.166.19.67.0acfc84cfa70aca5b970faf152979bc97b9f8b0c0c6ce687077cc67e4f3cbd0c89cb356fbbce91f4cee0dc6c66a913260311876a4b2b53fe0b9bc3f94
Vendor states this is fixed in 273548eb997c6be85230c1236b18784b09f6203c (fixed)
Vendor states this is fixed in 6dc0b4b39ed4f11ef70f76ecea8537e35f45342b (fixed)
Vendor states this is fixed in 7c54bd225d83bc1bcb44430ed4b4d3a5c36b1961 (fixed)
Vendor states this is fixed in 83463a96ea3c7d8ae636a4d6a0ba63c9ce410724 (fixed)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Affected range stops below 6.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 7.0 (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.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

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