CVE-2026-72095
HighIn 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.
CVSS 3.1 score
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected versions
Linux kernel versions
6.16
and later are affected. Fixed in
6.18.40,
7.1.5,
7.2
and their respective stable series.
References
3 totalFrequently asked questions
-
What is CVE-2026-72095?
CVE-2026-72095 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 6.16 onward and has been patched in 6.18.40, 7.1.5 and 7.2. CVE-2026-72095 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2026-72095?
CVE-2026-72095 has a CVSS score of 7.8 out of 10, rated High severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. -
Is there a patch available for CVE-2026-72095?
Yes. CVE-2026-72095 has been patched. Fixed versions include 6.18.40, 7.1.5 and 7.2. If you are running Linux kernel 6.16 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-72095 actively exploited?
No. CVE-2026-72095 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.