همهٔ گزارش‌ها
متوسط

kernel: dma-fence: Make dma_fence_dedup_array() robust against 0-count input

متن اصلی

نسخه‌های متأثر

نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده

بهره‌برداری

CVE-2026-72095

احتمال بهره‌برداری در ۳۰ روز آینده: 0.17%

FIRST EPSS · ۱۴۰۵/۰۸/۲۸

شرح آسیب‌پذیری

In the Linux kernel, the following vulnerability has been resolved: dma-fence: Make dma_fence_dedup_array() robust against 0-count input dma_fence_dedup_array() returns 1 when called with num_fences == 0: the for-loop body never executes, j stays at 0, and the final return ++j yields 1. This contradicts both the kernel-doc ("Return: Number of unique fences remaining in the array") and the natural expectation that 0 input gives 0 output. The caller _dma_fence_unwrap_merge() bails out via the if (count == 0 || count == 1) fast path and so is save. But amdgpu_userq_wait*() could reach the dedup call with a zero local count and dereference an uninitialized fence slot in the array. Make the contract match the documentation by returning 0 early. This also skips an unnecessary sort() call on an empty array.

A flaw was found in the Linux kernel's dma-fence component. The dma_fence_dedup_array() function incorrectly handles zero-count input, leading to a memory corruption vulnerability. A local attacker could potentially exploit this by triggering specific conditions in the amdgpu_userq_wait_*() functions, which may cause a system crash or lead to further compromise.