Skip to main content
VulnerabilityPublished Updated

CVE-2026-53190: Linux kernel · drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in c0fffc874c264292e769f26194a2a5e66ce31810 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:49 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in c0fffc874c264292e769f26194a2a5e66ce31810, 8348567a6afb24e2c9cafe8a321162d0eebe1411, 73524e9f96a278b521f257a78a845c49eb522bc1 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ eba57fb5498f2858768321e64570caea188455b8, < c0fffc874c264292e769f26194a2a5e66ce31810
Fixed in
  • c0fffc874c264292e769f26194a2a5e66ce31810
LinuxLinuxAffected
  • ≥ eba57fb5498f2858768321e64570caea188455b8, < 8348567a6afb24e2c9cafe8a321162d0eebe1411
Fixed in
  • 8348567a6afb24e2c9cafe8a321162d0eebe1411
LinuxLinuxAffected
  • ≥ eba57fb5498f2858768321e64570caea188455b8, < 73524e9f96a278b521f257a78a845c49eb522bc1
Fixed in
  • 73524e9f96a278b521f257a78a845c49eb522bc1
LinuxLinuxAffected
  • ≥ eba57fb5498f2858768321e64570caea188455b8, < 898bd0ccfed71651b881660c5d20ad73b5203174
Fixed in
  • 898bd0ccfed71651b881660c5d20ad73b5203174
LinuxLinuxAffected
  • ≥ eba57fb5498f2858768321e64570caea188455b8, < 3f26bb732cc136ab20176697c92f32c9c84cb125
Fixed in
  • 3f26bb732cc136ab20176697c92f32c9c84cb125
LinuxLinuxAffected
  • =6.5
Fixed in–

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.

References

Community reviews

Loading reviews…