CVE-2026-74448: drm/amdkfd: fix QID bit leak in pqm_create_queue()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 2ff5bb3645c72b3690e70c513a62a86600c4632f, 38b73293f38658a4685ffcea666462024f858ad9, 5f0f2ddeac738e2ca9d12cb76a1ff2904e85ecc3; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 2ff5bb3645c72b3690e70c513a62a86600c4632f, 38b73293f38658a4685ffcea666462024f858ad9, 5f0f2ddeac738e2ca9d12cb76a1ff2904e85ecc3; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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)
- Published
- Aug 15, 2026
- Updated
- Aug 18, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 9d61e2b81f5fc90c87975879809346e7c90ea5f9, d86ba913bbfd1afafacbfb750001ffc6bfe29da0, 6.15affected
- 0f88894aa628680747ae27760e5f627f901a435f and later · before 8924e2594a15bdbd07f8696770864366d787ab70affected · git
- c0ef1c8ef70bfa3487ea84f794d7a1f0fea0735d and later · before 2ff5bb3645c72b3690e70c513a62a86600c4632faffected · git
- fddc45026311c05a5355fd34b9dc0a1d7eaef4a2 and later · before 5f0f2ddeac738e2ca9d12cb76a1ff2904e85ecc3affected · git
- fddc45026311c05a5355fd34b9dc0a1d7eaef4a2 and later · before 7c35bf94150d872e670a6632aa819d320279effbaffected · git
- fddc45026311c05a5355fd34b9dc0a1d7eaef4a2 and later · before 38b73293f38658a4685ffcea666462024f858ad9affected · git
- 6.6.87 and later · before 6.6.151affected · semver
- 6.12.23 and later · before 6.12.103affected · semver
- 6.13.11 and later · before 6.14affected · semver
- 6.14.2 and later · before 6.15affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74441Aug 15, 2026 · usb: typec: ucsi: Fix race condition and ordering in port unregistration0Monitor
- ← EarlierCVE-2026-74442Aug 15, 2026 · drm/vmwgfx: avoid destroy_workqueue(NULL) on vkms init failure0Monitor
- Later →CVE-2026-74451Aug 15, 2026 · drm/panthor: validate firmware interface structure sizes31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2ff5bb3645c72b3690e70c513a62a86600c4632f | Vendor (CNA) |
| Linux Linux | 38b73293f38658a4685ffcea666462024f858ad9 | Vendor (CNA) |
| Linux Linux | 5f0f2ddeac738e2ca9d12cb76a1ff2904e85ecc3 | Vendor (CNA) |
| Linux Linux | 6.12.103 | Vendor (CNA) |
| Linux Linux | 6.14 | Vendor (CNA) |
| Linux Linux | 6.15 | Vendor (CNA) |
| Linux Linux | 6.6.151 | Vendor (CNA) |
| Linux Linux | 7c35bf94150d872e670a6632aa819d320279effb | Vendor (CNA) |
| Linux Linux | 8924e2594a15bdbd07f8696770864366d787ab70 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.105-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0854 · Aug 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.