CVE-2026-53190

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 6, 2026

Advisory Details (5)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c0fffc874c264292e769f26194a2a5e66ce31810
generic

drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/898bd0ccfed71651b881660c5d20ad73b5203174
generic

drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8348567a6afb24e2c9cafe8a321162d0eebe1411
generic

drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/73524e9f96a278b521f257a78a845c49eb522bc1
generic

drm/virtio: fix dma_fence refcount leak on error in virtio_gpu_dma_fence_wait() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f26bb732cc136ab20176697c92f32c9c84cb125

Vendor Advisories for CVE-2026-53190(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1—

Data Freshness Timeline

(refreshed 5× in last 7d / 63× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 186 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 19:41 UTCEG score recompute
  11. 2026-08-30 19:41 UTCVendor advisory
  12. 2026-08-30 19:41 UTCGHSA enrichment
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-28 02:55 UTCEG score recompute
  17. 2026-08-28 02:55 UTCVendor advisory
  18. 2026-08-28 02:55 UTCGHSA enrichment
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-24 13:47 UTCEG score recompute
  23. 2026-08-24 13:47 UTCVendor advisory
  24. 2026-08-24 13:47 UTCGHSA enrichment
  25. 2026-08-23 12:18 UTCEG score recompute
Show 75 more
  1. 2026-08-23 12:18 UTCVendor advisory
  2. 2026-08-23 12:18 UTCGHSA enrichment
  3. 2026-08-23 00:19 UTCEPSS rescore
  4. 2026-08-22 10:48 UTCEG score recompute
  5. 2026-08-22 10:48 UTCVendor advisory
  6. 2026-08-22 10:48 UTCGHSA enrichment
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-21 08:40 UTCEG score recompute
  9. 2026-08-21 08:40 UTCVendor advisory
  10. 2026-08-21 08:40 UTCGHSA enrichment
  11. 2026-08-20 22:55 UTCEPSS rescore
  12. 2026-08-20 07:11 UTCEG score recompute
  13. 2026-08-20 07:11 UTCVendor advisory
  14. 2026-08-20 07:11 UTCGHSA enrichment
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-19 01:34 UTCEG score recompute
  17. 2026-08-19 01:34 UTCVendor advisory
  18. 2026-08-19 01:34 UTCGHSA enrichment
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 11:31 UTCEG score recompute
  22. 2026-08-17 11:31 UTCVendor advisory
  23. 2026-08-17 11:31 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 10:03 UTCEG score recompute
  26. 2026-08-16 10:03 UTCVendor advisory
  27. 2026-08-16 10:03 UTCGHSA enrichment
  28. 2026-08-16 02:14 UTCEPSS rescore
  29. 2026-08-15 08:35 UTCEG score recompute
  30. 2026-08-15 08:35 UTCVendor advisory
  31. 2026-08-15 08:35 UTCGHSA enrichment
  32. 2026-08-15 01:30 UTCEPSS rescore
  33. 2026-08-14 04:56 UTCEG score recompute
  34. 2026-08-14 04:56 UTCVendor advisory
  35. 2026-08-14 04:56 UTCGHSA enrichment
  36. 2026-08-13 22:00 UTCEPSS rescore
  37. 2026-08-13 03:28 UTCEG score recompute
  38. 2026-08-13 03:28 UTCGHSA enrichment
  39. 2026-08-12 13:51 UTCEPSS rescore
  40. 2026-08-12 02:00 UTCEG score recompute
  41. 2026-08-12 02:00 UTCVendor advisory
  42. 2026-08-12 02:00 UTCGHSA enrichment
  43. 2026-08-11 00:32 UTCEG score recompute
  44. 2026-08-11 00:32 UTCVendor advisory
  45. 2026-08-11 00:32 UTCGHSA enrichment
  46. 2026-08-11 00:00 UTCEPSS rescore
  47. 2026-08-09 23:04 UTCEG score recompute
  48. 2026-08-09 23:04 UTCVendor advisory
  49. 2026-08-09 23:04 UTCGHSA enrichment
  50. 2026-08-09 13:46 UTCEPSS rescore
  51. 2026-08-08 21:36 UTCEG score recompute
  52. 2026-08-08 21:36 UTCVendor advisory
  53. 2026-08-08 21:36 UTCGHSA enrichment
  54. 2026-08-08 16:37 UTCEPSS rescore
  55. 2026-08-07 20:07 UTCEG score recompute
  56. 2026-08-07 20:07 UTCGHSA enrichment
  57. 2026-08-06 18:39 UTCEG score recompute
  58. 2026-08-06 18:39 UTCVendor advisory
  59. 2026-08-06 18:39 UTCGHSA enrichment
  60. 2026-08-06 13:47 UTCEPSS rescore
  61. 2026-08-05 19:17 UTCEPSS rescore
  62. 2026-08-05 17:11 UTCEG score recompute
  63. 2026-08-05 17:11 UTCGHSA enrichment
  64. 2026-08-04 15:10 UTCEPSS rescore
  65. 2026-08-04 15:07 UTCEG score recompute
  66. 2026-08-04 15:07 UTCVendor advisory
  67. 2026-08-04 15:07 UTCGHSA enrichment
  68. 2026-08-04 10:39 UTCEPSS rescore
  69. 2026-08-03 10:36 UTCEPSS rescore
  70. 2026-08-03 07:53 UTCGHSA enrichment
  71. 2026-08-02 06:24 UTCEG score recompute
  72. 2026-08-02 06:24 UTCVendor advisory
  73. 2026-08-02 06:24 UTCGHSA enrichment
  74. 2026-08-02 02:27 UTCEPSS rescore
  75. 2026-08-01 04:55 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-53190?
CVE-2026-53190 is a medium vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/virtio: fix dmafence refcount leak on error in virtiogpudmafence_wait() dmafenceunwrapforeach() internally calls dmafenceunwrap_first() which does cursor->chain = dmafenceget(head), taking an extra reference. On normal loop…
When was CVE-2026-53190 disclosed?
CVE-2026-53190 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53190 actively exploited?
CVE-2026-53190 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53190?
CVE-2026-53190 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53190?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53190, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53190

Explore →

Is Your Infrastructure Affected by CVE-2026-53190?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs