Description
In the Linux kernel, the following vulnerability has been resolved:

drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait()

dma_fence_unwrap_for_each() internally calls dma_fence_unwrap_first()
which does cursor->chain = dma_fence_get(head), taking an extra
reference. On normal loop completion, dma_fence_unwrap_next()
releases this via dma_fence_chain_walk() -> dma_fence_put().

When virtio_gpu_do_fence_wait() fails and the function returns early
from inside the loop, the cursor->chain reference is never released.
This is the only caller in the entire kernel that does an early return
inside dma_fence_unwrap_for_each.

Add dma_fence_put(itr.chain) before the early return.
Published: 2026-06-25
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Linux kernel contains a reference‑count leak in the virtio GPU driver. When the function virtio_gpu_dma_fence_wait fails and returns early, a cursor chain reference is not released, causing a gradual build‑up of unreleased DMA fence objects. Over time this leak can exhaust kernel memory, degrade performance and potentially result in a denial of service. The weakness is a resource leak (CWE‑414).

Affected Systems

All Linux kernel builds that ship the virtio GPU driver prior to the commit adding the missing dma_fence_put are affected. No specific version range is given, so any kernel that has not applied the patch is at risk.

Risk and Exploitability

The vulnerability is not listed in CISA KEV and lacks an EPSS score, so the exploitation probability is unknown. Based on the description, it is inferred that an attacker would need to trigger the failure path in virtio_gpu_do_fence_wait, which is likely limited to workloads that exercise GPU acceleration or privileged users. Consequently, the risk is chiefly an internal denial of service rather than remote code execution.

Generated by OpenCVE AI on June 25, 2026 at 11:58 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to a Linux kernel release containing the patch for virtio_gpu_dma_fence_wait
  • Reboot the system or reload the virtio GPU module after applying the patch
  • If a kernel upgrade cannot be performed immediately, restrict or revoke access to the virtio GPU device to prevent the error path from being exercised by untrusted workloads

Generated by OpenCVE AI on June 25, 2026 at 11:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 25 Jun 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-414

Thu, 25 Jun 2026 09:15:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait() dma_fence_unwrap_for_each() internally calls dma_fence_unwrap_first() which does cursor->chain = dma_fence_get(head), taking an extra reference. On normal loop completion, dma_fence_unwrap_next() releases this via dma_fence_chain_walk() -> dma_fence_put(). When virtio_gpu_do_fence_wait() fails and the function returns early from inside the loop, the cursor->chain reference is never released. This is the only caller in the entire kernel that does an early return inside dma_fence_unwrap_for_each. Add dma_fence_put(itr.chain) before the early return.
Title drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-06-25T08:39:02.366Z

Reserved: 2026-06-09T07:44:35.390Z

Link: CVE-2026-53190

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-25T12:00:14Z

Weaknesses