Answer in brief
CVE-2026-53190 records a Medium severity (CVSS 5.5) vulnerability in drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait(). 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.
CVSS is 5.5. 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.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | 6.5 | Not reported |
| Linux/Linuxgeneric | >=eba57fb5498f2858768321e64570caea188455b8 <898bd0ccfed71651b881660c5d20ad73b5203174 || >=eba57fb5498f2858768321e64570caea188455b8 <73524e9f96a278b521f257a78a845c49eb522bc1 || >=eba57fb5498f2858768321e64570caea188455b8 <8348567a6afb24e2c9cafe8a321162d0eebe1411 || >=eba57fb5498f2858768321e64570caea188455b8 <c0fffc874c264292e769f26194a2a5e66ce31810 || >=eba57fb5498f2858768321e64570caea188455b8 <3f26bb732cc136ab20176697c92f32c9c84cb125 | 898bd0ccfed71651b881660c5d20ad73b5203174, 73524e9f96a278b521f257a78a845c49eb522bc1, 8348567a6afb24e2c9cafe8a321162d0eebe1411, c0fffc874c264292e769f26194a2a5e66ce31810, 3f26bb732cc136ab20176697c92f32c9c84cb125 |
Published upstream
Jun 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.