From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-53144][MODERATE REGULAR] drm/amdkfd: fix NULL dereference in get_queue_ids() Date: Mon, 29 Jun 2026 12:47:40 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-53144 X-AL-KERNEL-Priority: MODERATE REGULAR X-AL-KERNEL-Severity: MODERATE REGULAR X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 3 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: 62bd09e23a23da70f9aae02748eba3e6bd93095d List-Id: CVE: CVE-2026-53144 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: drm/amdkfd: fix NULL dereference in get_queue_ids() Commit: 62bd09e23a23da70f9aae02748eba3e6bd93095d Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=62bd09e23a23da70f9aae02748eba3e6bd93095d Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53144 Analysis date: Mon, 29 Jun 2026 12:47:40 -0400 ActionableScore: 3 ActionableScore lower bound: unknown Actionable bucket: Borderline Moderate, manual review recommended Manual review required: YES Summary: A local user with access to the AMD KFD debug trap ioctl can pass a NULL queue array with a nonzero queue count, causing a NULL pointer dereference in queue invalidation and a kernel panic. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-53144 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53144 The original announcement does not normally provide a security severity estimate, CVSS assessment, or enough information to determine whether the reported kernel bug represents a practically relevant security issue. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. It combines an autonomous classifier with LLM-assisted technical analysis and a separate ActionableScore mechanism. The purpose of this report is to prioritize Linux kernel CVEs before manual review, identify cases that require prompt investigation, and support automatic closure of issues that are unlikely to have meaningful security impact. Published priority for this report: MODERATE REGULAR Manual review required: YES A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-53144 MODERATE CHECK Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H';**CWE-476;*CWE-20;CWE-754;BEST CVSS score: '5.5';DESCR 'A NULL pointer dereference in the AMD KFD debug trap path occurs because get_queue_ids can return NULL when usr_queue_id_array is NULL and num_queues is nonzero. The callers only check IS_ERR, so NULL is treated as a valid pointer and suspend_queues can later pass it to q_array_invalidate, causing a kernel crash during queue invalidation. For the CVSS the PR:L because a local process with access to the AMD KFD ioctl path can supply the invalid queue array parameters. The issue is not network reachable and requires local userspace interaction with the GPU driver interface. Impact is denial of service via kernel panic only, with no supported evidence of confidentiality impact, integrity impact, UAF, or privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline Moderate, manual review recommended (with actual score 3) SKIP CVE-2026-53144 SKIP No affected files built, so skip this CVE NO - - unknown MAYBE DANGER NULLPTR SIMPLEFIX HARDWARE DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=3 ## 1. ActionableScore * Conservative score: **3** * Paranoid score: **3** * Final recommended bucket: **Borderline Moderate, manual review recommended**:: ## 2. Signal breakdown * **Local unprivileged trigger: +1** Userspace can trigger the bug through `kfd_ioctl_set_debug_trap()` by passing `num_queues > 0` with a zero `queue_array_ptr`, assuming access to the AMD KFD device interface. * **Reliable kernel crash / strong DoS: +1** The commit explicitly states that this leads to a NULL pointer dereference and kernel panic via `q_array_invalidate()`. * **Availability impact realistic: +1** The trigger appears simple and deterministic once the ioctl path is reachable. This is a host kernel crash, not just a warning or recoverable error. * **No memory corruption bonus: +0** This is a NULL pointer dereference. The patch does not indicate UAF, OOB write, type confusion, stale callback, refcount misuse, or attacker-controlled object reuse. * **No LPE bonus: +0** There is no supported privilege escalation primitive. Impact is DoS only. * **No remote/network exposure: +0** The affected path is a local GPU driver ioctl path, not network reachable. ## 3. Reachability analysis A local process with access to the AMD KFD device interface can likely trigger the bug. In many deployments, `/dev/kfd` access is granted to users in GPU-related groups such as `render` or `video`, so this should not automatically be treated as requiring full root privileges. Containers may matter if GPU devices are passed through or exposed to workloads. The path is hardware and driver dependent: systems without AMD KFD enabled or without accessible AMD GPU compute devices are not exposed. ## 4. Severity interpretation This behaves like an **ordinary to borderline Moderate local DoS**, not an Important-class vulnerability. The realistic impact is a kernel panic caused by a NULL dereference. Theoretical memory corruption or privilege escalation is not supported by the patch or commit message, and the changed code simply converts an invalid NULL pointer plus nonzero queue count into `ERR_PTR(-EINVAL)`. ## 5. One-sentence report phrase A local user with access to the AMD KFD debug trap ioctl can pass a NULL queue array with a nonzero queue count, causing a NULL pointer dereference in queue invalidation and a kernel panic. ## 6. Manual review recommendation **MANUAL CHECK RECOMMENDED** Manual review is useful to confirm real deployment exposure, especially `/dev/kfd` permissions, AMD GPU presence, and whether untrusted users or containers can access the KFD ioctl path. This does not require Important handling unless additional evidence shows memory corruption or privilege escalation beyond the NULL dereference DoS. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: drm/amdkfd: fix NULL dereference in get_queue_ids() Commit: 62bd09e23a23da70f9aae02748eba3e6bd93095d Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=62bd09e23a23da70f9aae02748eba3e6bd93095d Commit description: 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. Fixes: a70a93f ("drm/amdkfd: add debug suspend and resume process queues operation") Signed-off-by: Muhammad Bilal Signed-off-by: Alex Deucher (cherry picked from commit f165a82 ) Cc: stable@vger.kernel.org Signed-off-by: Greg Kroah-Hartman Changed files: drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c Diff excerpt: Not included in this email. See the upstream URL for the full patch. Full patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=62bd09e23a23da70f9aae02748eba3e6bd93095d ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-53144 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53144 The original CVE announcement normally does not include a security-level estimate. In particular, it may not contain a CVSS assessment, an impact level, or enough information to determine whether the reported bug is a practically relevant security issue. One purpose of this parallel CVE list is to provide that missing technical and prioritization information. The original goal of the AL-KERNEL project was to prioritize Linux kernel CVE analysis automatically before manual review. The system can also help identify non-security issues that may be suitable for automatic closure. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. The first analysis stage combines an autonomous classifier with additional LLM-based analysis. The autonomous classifier runs locally on a CPU and is based on a backpropagation neural network. Together, these mechanisms produce a technical vulnerability description, identify likely weakness types, estimate CVSS severity, and provide input for ActionableScore. Two CVSS estimates are retained because incomplete kernel vulnerability information often permits more than one defensible interpretation: Conservative CVSS vector: Not available The Best / paranoid CVSS vector: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 5.5 The conservative vector represents a lower-impact interpretation. The Best/paranoid vector intentionally represents a plausible upper-bound interpretation and should not automatically be treated as demonstrated real-world impact. CVSS may also need to be adjusted for a particular Linux deployment, because actual reachability, privileges, enabled kernel configuration, hardware, namespaces, exposed device nodes, and other environmental conditions can differ significantly between systems. A separate ActionableScore mechanism evaluates practical remediation urgency. Its analysis may include reachability, attack prerequisites, subsystem exposure, memory-corruption characteristics, denial-of-service reliability, and possible confidentiality, integrity, or privilege-escalation impact. Conservative ActionableScore: unknown Paranoid ActionableScore: 3 The final base severity is taken directly from the second tab-separated field of the AL-KERNEL classification result. ActionableScore does not replace or independently override that final AL-KERNEL decision, and if ActionableScore adjusted impact level of ALKERNEL, then you would see self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7. For an AL-KERNEL result of MODERATE, this report uses the following additional presentation split: ActionableScore below 5 -> MODERATE REGULAR ActionableScore 5 or more -> MODERATE 7.0 The distinction between MODERATE REGULAR and MODERATE 7.0 makes it possible to identify Moderate issues that should receive manual analysis and fixes before lower-priority MODERATE REGULAR issues. In many cases, MODERATE REGULAR fixes may wait for a later rebase or routine update. There is one override in which MODERATE REGULAR becomes MODERATE 7.0 even when the ActionableScore is below 5. When the AL-KERNEL result contains the KPANIC flag, a MODERATE result is always presented as MODERATE 7.0. The KPANIC flag selected with few regexps without usage of AI at all, so it helps to detect cases when Kernel Crash happens and similar (to filter False-Negative results from the LLM usage). KPANIC indicates that a reliable kernel crash, kernel panic, or similarly serious kernel availability impact was identified by the classification workflow. AL-KERNEL base severity for this report: MODERATE KPANIC detected for this report: NO Published priority for this report (same as in Subject): MODERATE REGULAR These results are intended to support engineering triage. They are machine-generated estimates, and cases marked for manual review should be validated by a human security engineer before final disposition. For more info read docs linked from here: https://kernelcve.org/ (and you can submit you own patch there to generate such a report for non-existant CVE-id yet). Note that in many cases this AI tool selects higher severity, than real is (means you can expect Importants instead of Moderate 7.0 or Moderates 7.0 instead of regular Moderates). If you see such cases, please use reply email interface to add additional manual analyses info to this particular CVE. And please, please, let me know when you see Lows instead of Importants or Important instead of Low (because particular for such cases I need to tune this AI tool to make it better for this one and next similar). My contact email for such notifications is alexanjelausa@gmail.com (and both send reply to CVE record itself too and see "reply" button below for howto reply).