CVE-2026-53144 Details
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)
A NULL pointer dereference vulnerability has been identified in the Linux kernel's AMD GPU queue management component (drm/amdkfd). This issue occurs when the 'usr_queue_id_array' is NULL and 'num_queues' is greater than zero. The 'get_queue_ids()' function then returns NULL, which is not properly handled by the callers. This oversight allows userspace to trigger a kernel panic by sending a debug trap ioctl with a zero queue array pointer and a positive queue count. The vulnerability has been addressed by modifying the 'get_queue_ids()' function to return an error pointer when 'num_queues' is non-zero and the queue array pointer is absent, ensuring that the NULL case is only treated as a valid no-operation when 'num_queues' is zero.
The vulnerability has been fixed in the Linux kernel. Users should upgrade to the latest version.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/2bd550b547deabef98bd3b017ff743b7c34d3a6d | kernel.org | Patch |
| https://git.kernel.org/stable/c/62bd09e23a23da70f9aae02748eba3e6bd93095d | kernel.org | Patch |
| https://git.kernel.org/stable/c/72e259a32084c42816152c346096d2edd4213e23 | kernel.org | Patch |
| https://git.kernel.org/stable/c/daeceb0fe2a19651c58bbfa3d9d515ecb6ca8996 | kernel.org | Patch |
| https://git.kernel.org/stable/c/e1965e8913cfbf17622ca12638e7a07f68ba0848 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-476 | NULL Pointer Dereference | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.5, < 6.6.143 >= 6.7, < 6.12.94 >= 6.13, < 6.18.36 >= 6.19, < 7.0.13 7.1 rc1 7.1 rc2 7.1 rc3 7.1 rc4 7.1 rc5 7.1 rc6 |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 7, 2026 | Initial Analysis | [email protected] |
| Jun 25, 2026 | New CVE Received | kernel.org |