CVE-2026-74448

drm/amdkfd: fix QID bit leak in pqm_create_queue()

N/A
Published: August 15, 2026 at 12:26 PM UTC
Updated: August 18, 2026 at 07:16 AM 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
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: fix QID bit leak in pqm_create_queue() When MES is enabled and amdgpu_amdkfd_alloc_kernel_mem() fails during the first queue creation for a process, pqm_create_queue() returns early via 'return retval' without going through the err_create_queue cleanup label. This means clear_bit(*qid, pqm->queue_slot_bitmap) is never called, leaving the reserved QID bit permanently set in queue_slot_bitmap. Over time this leaks QID slots, potentially exhausting all available queue slots. Fix this by replacing 'return retval' with 'goto err_allocate_pqn' so that clear_bit() is always called on the error path without touching the uninitialized pqn pointer. AILIKFD-813 (cherry picked from commit a107f74c38edbb80d6ab64dcaeeb292c14e9779f)

Affected

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

v ≥ 6.13.11v ≥ 6.14.26.12.23 ≤ v < 6.12.1036.13.11 ≤ v < 6.146.14.2 ≤ v < 6.156.15 ≤ v < 6.18.446.15 ≤ v < 7.1.86.15 ≤ v < 7.26.6.87 ≤ v < 6.6.1510f88894aa628680747ae27760e5f627f901a435f6.12.236.13.116.14.26.156.6.879d61e2b81f5fc90c87975879809346e7c90ea5f9c0ef1c8ef70bfa3487ea84f794d7a1f0fea0735dd86ba913bbfd1afafacbfb750001ffc6bfe29da0fddc45026311c05a5355fd34b9dc0a1d7eaef4a2
Vendor states this is fixed in 2ff5bb3645c72b3690e70c513a62a86600c4632f (fixed)
Vendor states this is fixed in 38b73293f38658a4685ffcea666462024f858ad9 (fixed)
Vendor states this is fixed in 5f0f2ddeac738e2ca9d12cb76a1ff2904e85ecc3 (fixed)
Vendor states this is fixed in 7c35bf94150d872e670a6632aa819d320279effb (fixed)
Vendor states this is fixed in 8924e2594a15bdbd07f8696770864366d787ab70 (fixed)
Vendor states this is fixed in 6.12.103 (unaffected)
Affected range stops below 6.14, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.15 (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.

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