From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-46224][LOW] drm/xe: Fix bo leak in xe_dma_buf_init_obj() on allocation failure Date: Thu, 28 May 2026 08:41:16 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-46224 X-AL-KERNEL-Priority: LOW X-AL-KERNEL-Severity: LOW X-AL-KERNEL-Base-Severity: LOW X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 2 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: f9ad21b90162baf1d78f8036ff3813c3ec1ac88e List-Id: CVE: CVE-2026-46224 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: drm/xe: Fix bo leak in xe_dma_buf_init_obj() on allocation failure Commit: f9ad21b90162baf1d78f8036ff3813c3ec1ac88e Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f9ad21b90162baf1d78f8036ff3813c3ec1ac88e Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46224 Analysis date: Thu, 28 May 2026 08:41:16 -0400 ActionableScore: 2 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate / Low-like Manual review required: NO Summary: `xe_dma_buf_init_obj()` could leak a preallocated storage BO when `drm_gpuvm_resv_object_alloc()` failed, allowing a local user with xe DRM access to potentially cause resource exhaustion through repeated failing dma-buf imports. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-46224 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46224 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: LOW Manual review required: NO A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-46224 LOW CHECK Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';*CWE-401;*CWE-772;**CWE-400;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'xe_dma_buf_init_obj could leak the preallocated storage BO when drm_gpuvm_resv_object_alloc failed during dma-buf import setup. A local user with access to the Intel xe DRM device or render node may trigger the error path by repeatedly attempting imports under memory pressure, causing resource leakage over time. For the CVSS the PR:L is used because the paranoid scenario requires local device access rather than full administrative privileges. The issue is not network reachable. Impact is availability only through possible resource exhaustion, with no supported memory corruption, information disclosure, or privilege escalation primitive.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2) SKIP CVE-2026-46224 SKIP The Fixes patch not applied yet, so unlikely that actual: eb289a5f6cc668853f9b2ea6aca04afe58ed11c7 YES NO NO unknown MAYBE INIT LEAK ERRORPATH UAF HARDWARE MEMORY DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=2 ## 1. ActionableScore * Conservative score: 2 * Paranoid score: 2 * Final recommended bucket: **Ordinary Moderate / Low-like**:: ## 2. Signal breakdown Triggered signals: * Local unprivileged trigger: +1. A local user with access to the Intel xe DRM device or render node may reach the dma-buf import path. * Availability impact realistic: +1. Repeated failures could leak BO resources and eventually contribute to resource exhaustion. Limiting factors: * No memory corruption. The bug is a missing free on an allocation failure path. * No UAF, double free, OOB access, arbitrary write, information leak, or privilege escalation primitive. * No remote or network trigger. * Triggering requires an allocation failure in `drm_gpuvm_resv_object_alloc()`, so reliable abuse is conditional on memory pressure or failure injection-like conditions. ## 3. Reachability analysis The issue is local and requires access to the xe DRM device or render node. Containers may be affected if the render node is passed through, but the bug still requires hitting a specific ENOMEM path during dma-buf import setup. The path is not network reachable. It is relevant only on systems using the Intel xe driver, and practical exploitation depends on whether an attacker can repeatedly force the failing allocation path. ## 4. Severity interpretation This behaves like an ordinary Moderate or Low-like resource leak. The practical impact is availability degradation through leaked BO resources, not host compromise. There is no supported memory corruption or privilege escalation evidence. Even the paranoid interpretation remains availability-only. ## 5. One-sentence report phrase `xe_dma_buf_init_obj()` could leak a preallocated storage BO when `drm_gpuvm_resv_object_alloc()` failed, allowing a local user with xe DRM access to potentially cause resource exhaustion through repeated failing dma-buf imports. ## 6. Manual review recommendation NO MANUAL CHECK NEEDED This is a constrained resource leak on an allocation failure path with no memory corruption, information disclosure, privilege escalation, or network reachability. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: drm/xe: Fix bo leak in xe_dma_buf_init_obj() on allocation failure Commit: f9ad21b90162baf1d78f8036ff3813c3ec1ac88e Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f9ad21b90162baf1d78f8036ff3813c3ec1ac88e Commit description: When drm_gpuvm_resv_object_alloc() fails, the pre-allocated storage bo is not freed. Add xe_bo_free(storage) before returning the error. xe_dma_buf_init_obj() calls xe_bo_init_locked(), which frees the bo on error. Therefore, xe_dma_buf_init_obj() must also free the bo on its own error paths. Otherwise, since xe_gem_prime_import() cannot distinguish whether the failure originated from xe_dma_buf_init_obj() or from xe_bo_init_locked(), it cannot safely decide whether the bo should be freed. Add comments documenting the ownership semantics: on success, ownership of storage is transferred to the returned drm_gem_object; on failure, storage is freed before returning. v2: Add comments to explain the free logic. Fixes: eb289a5 ("drm/xe: Convert xe_dma_buf.c for exhaustive eviction") Cc: stable@vger.kernel.org Assisted-by: Claude:claude-opus-4.6 Reviewed-by: Matthew Brost Link: https://patch.msgid.link/20260408175255.3402838-4-shuicheng.lin@intel.com Signed-off-by: Shuicheng Lin (cherry picked from commit 78a6c5f ) Signed-off-by: Rodrigo Vivi Signed-off-by: Greg Kroah-Hartman Changed files: drivers/gpu/drm/xe/xe_dma_buf.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=f9ad21b90162baf1d78f8036ff3813c3ec1ac88e ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-46224 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-46224 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: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 4.7 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: 2 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: LOW KPANIC detected for this report: NO Published priority for this report (same as in Subject): LOW 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).