dma-fence: Make dma_fence_dedup_array() robust against 0-count input (CVE-2026-72095) | HOL Guard CVE

High · CVSS 7.8CVE-2026-72095

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

Answer in brief

CVE-2026-72095 records a High severity (CVSS 7.8) vulnerability in dma-fence: Make dma_fence_dedup_array() robust against 0-count input. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 15, 2026Updated Aug 17, 2026Source checked Sep 29, 2026First seen by HOL Aug 15, 2026Material review Aug 17, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.8
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=575ec9b0c2f11f40535ea737ed5a64792780d1ef <7aa8f3dba53422465dbe1be8dbb7240304462bb2 \|\| >=575ec9b0c2f11f40535ea737ed5a64792780d1ef <e2d9a2ea178a5da0b4a6693e8ebca5c7fc4d7051 \|\| >=575ec9b0c2f11f40535ea737ed5a64792780d1ef <77a9298741f8f9e8b963c977f5582ab21c6d3427	7aa8f3dba53422465dbe1be8dbb7240304462bb2, e2d9a2ea178a5da0b4a6693e8ebca5c7fc4d7051, 77a9298741f8f9e8b963c977f5582ab21c6d3427
Linux/Linuxgeneric	6.16	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 7aa8f3dba53422465dbe1be8dbb7240304462bb2 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 15, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.