Skip to main content
VulnerabilityPublished Updated

CVE-2026-53144: Linux kernel · drm/amdkfd: fix NULL dereference in get_queue_ids()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in e1965e8913cfbf17622ca12638e7a07f68ba0848 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:49 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in e1965e8913cfbf17622ca12638e7a07f68ba0848, daeceb0fe2a19651c58bbfa3d9d515ecb6ca8996, 72e259a32084c42816152c346096d2edd4213e23 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ a70a93fa568b4f05aba548dadb673703eccf5480, < e1965e8913cfbf17622ca12638e7a07f68ba0848
Fixed in
  • e1965e8913cfbf17622ca12638e7a07f68ba0848
LinuxLinuxAffected
  • ≥ a70a93fa568b4f05aba548dadb673703eccf5480, < daeceb0fe2a19651c58bbfa3d9d515ecb6ca8996
Fixed in
  • daeceb0fe2a19651c58bbfa3d9d515ecb6ca8996
LinuxLinuxAffected
  • ≥ a70a93fa568b4f05aba548dadb673703eccf5480, < 72e259a32084c42816152c346096d2edd4213e23
Fixed in
  • 72e259a32084c42816152c346096d2edd4213e23
LinuxLinuxAffected
  • ≥ a70a93fa568b4f05aba548dadb673703eccf5480, < 62bd09e23a23da70f9aae02748eba3e6bd93095d
Fixed in
  • 62bd09e23a23da70f9aae02748eba3e6bd93095d
LinuxLinuxAffected
  • ≥ a70a93fa568b4f05aba548dadb673703eccf5480, < 2bd550b547deabef98bd3b017ff743b7c34d3a6d
Fixed in
  • 2bd550b547deabef98bd3b017ff743b7c34d3a6d
LinuxLinuxAffected
  • =6.5
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: fix NULL dereference in get_queue_ids() When usr_queue_id_array is NULL and num_queues is non-zero, get_queue_ids() returns NULL. The callers check only IS_ERR() on the return value; since IS_ERR(NULL) == false the check passes, and suspend_queues() calls q_array_invalidate() which immediately dereferences NULL while iterating num_queues times. Userspace can trigger this via kfd_ioctl_set_debug_trap() by supplying num_queues > 0 with a zero queue_array_ptr, causing a kernel panic. A NULL usr_queue_id_array with num_queues == 0 is a legitimate no-op (q_array_invalidate never executes, and resume_queues already guards all queue_ids dereferences behind a NULL check). Return ERR_PTR(-EINVAL) only when num_queues is non-zero and the pointer is absent; both callers already propagate IS_ERR() returns correctly to userspace. (cherry picked from commit f165a82cdf503884bb1797771c61b2fcc72113d4)

References

Community reviews

Loading reviews…