← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-72095

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-72095

Key Details

CVECVE-2026-72095
CVSS Score / Version
7.8 (High) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS Prose
attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products
Linux Kernel

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

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. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-72095
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-72095
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.