Bug 2492822 (CVE-2026-53190) - CVE-2026-53190 kernel: drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait()
Summary: CVE-2026-53190 kernel: drm/virtio: fix dma_fence refcount leak on error in vi...
Keywords:
Status: NEW
Alias: CVE-2026-53190
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-25 10:07 UTC by OSIDB Bzimport
Modified: 2026-06-29 14:03 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-06-25 10:07:35 UTC
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.

Comment 1 Mauro Matteo Cascella 2026-06-29 13:58:39 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026062557-CVE-2026-53190-819e@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.