Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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)

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 0f88894aa628680747ae27760e5f627f901a435f – < 8924e2594a15bdbd07f8696770864366d787ab70
    • affected c0ef1c8ef70bfa3487ea84f794d7a1f0fea0735d – < 2ff5bb3645c72b3690e70c513a62a86600c4632f
    • affected fddc45026311c05a5355fd34b9dc0a1d7eaef4a2 – < 5f0f2ddeac738e2ca9d12cb76a1ff2904e85ecc3
    • affected fddc45026311c05a5355fd34b9dc0a1d7eaef4a2 – < 7c35bf94150d872e670a6632aa819d320279effb
    • affected fddc45026311c05a5355fd34b9dc0a1d7eaef4a2 – < 38b73293f38658a4685ffcea666462024f858ad9
    • affected 9d61e2b81f5fc90c87975879809346e7c90ea5f9
    • affected d86ba913bbfd1afafacbfb750001ffc6bfe29da0
    • affected 6.6.87 – < 6.6.151
    • affected 6.12.23 – < 6.12.103
    • affected 6.13.11 – < 6.14
    • affected 6.14.2 – < 6.15
  • Linux · Linux

    • affected 6.15
    • unaffected < 6.15
    • unaffected 6.6.151 – ≤ 6.6.*
    • unaffected 6.12.103 – ≤ 6.12.*
    • unaffected 6.18.44 – ≤ 6.18.*
    • unaffected 7.1.8 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74448 badge
[![CVE-2026-74448](https://cveledger.app/badge/CVE-2026-74448.svg)](https://cveledger.app/cve/CVE-2026-74448)

Record last updated .