# CVE-2026-74448: drm/amdkfd: fix QID bit leak in pqm_create_queue()

> A local attacker can exhaust GPU queue slots by triggering a memory allocation failure, causing denial of service for subsequent queue creations.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** AZL-96450, BELL-CVE-2026-74448, DEBIAN-CVE-2026-74448, GHSA-8x3r-qg94-9qh5, UBUNTU-CVE-2026-74448

## What is CVE-2026-74448?

CVE-2026-74448 is a denial of service vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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)

## Which versions are affected by CVE-2026-74448?


## How do I fix CVE-2026-74448?

Apply the vendor's patch.

## Is CVE-2026-74448 being exploited?

There is no known exploitation of CVE-2026-74448 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74448 and fix it if it is affected.

What it is: CVE-2026-74448 is a denial of service vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74448 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-74448/ (Markdown: https://insights.sbomify.com/CVE-2026-74448/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-74448
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-74448
- OSV: https://osv.dev/vulnerability/CVE-2026-74448

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-74448/
Summaries are generated and may contain mistakes; the official description above is the record.