CVE-2026-53190
drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait()
Vexday Risk Score
3Low
SSVC decision (CISA)
Track
No exploitation signal → monitor
CVSS —EPSS 0.2%KEV nãoPoC —Nuclei —Metasploit —Patch —
Lifecycle
25 Jun 2026Published on NVD
Recommendation: Monitor — no exploitation signal at the moment.
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.
Affected products
Linux · LinuxWant to know if your infrastructure is exposed to this?
Talk to TrueHacking →References
https://git.kernel.org/stable/c/3f26bb732cc136ab20176697c92f32c9c84cb125https://git.kernel.org/stable/c/73524e9f96a278b521f257a78a845c49eb522bc1https://git.kernel.org/stable/c/8348567a6afb24e2c9cafe8a321162d0eebe1411https://git.kernel.org/stable/c/898bd0ccfed71651b881660c5d20ad73b5203174https://git.kernel.org/stable/c/c0fffc874c264292e769f26194a2a5e66ce31810