Answer in brief
CVE-2026-74448 records a Unknown severity vulnerability in drm/amdkfd: fix QID bit leak in pqm_create_queue(). The current sources do not mark it as known exploited. The current feed maps 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8924e2594a15bdbd07f8696770864366d787ab70 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2ff5bb3645c72b3690e70c513a62a86600c4632f || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5f0f2ddeac738e2ca9d12cb76a1ff2904e85ecc3 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7c35bf94150d872e670a6632aa819d320279effb || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <38b73293f38658a4685ffcea666462024f858ad9 || >=0 <6.6.151 || >=0 <6.12.103 || >=0 <6.18.44 || >=0 <7.1.8 | 8924e2594a15bdbd07f8696770864366d787ab70, 2ff5bb3645c72b3690e70c513a62a86600c4632f, 5f0f2ddeac738e2ca9d12cb76a1ff2904e85ecc3, 7c35bf94150d872e670a6632aa819d320279effb, 38b73293f38658a4685ffcea666462024f858ad9, 6.6.151, 6.12.103, 6.18.44, 7.1.8 |
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/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)
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74448 records a Unknown severity vulnerability in drm/amdkfd: fix QID bit leak in pqm_create_queue(). The current sources do not mark it as known exploited. The current feed maps 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8924e2594a15bdbd07f8696770864366d787ab70 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2ff5bb3645c72b3690e70c513a62a86600c4632f || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5f0f2ddeac738e2ca9d12cb76a1ff2904e85ecc3 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7c35bf94150d872e670a6632aa819d320279effb || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <38b73293f38658a4685ffcea666462024f858ad9 || >=0 <6.6.151 || >=0 <6.12.103 || >=0 <6.18.44 || >=0 <7.1.8 | 8924e2594a15bdbd07f8696770864366d787ab70, 2ff5bb3645c72b3690e70c513a62a86600c4632f, 5f0f2ddeac738e2ca9d12cb76a1ff2904e85ecc3, 7c35bf94150d872e670a6632aa819d320279effb, 38b73293f38658a4685ffcea666462024f858ad9, 6.6.151, 6.12.103, 6.18.44, 7.1.8 |
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/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)
Quoted source text, attributed separately from HOL analysis.