Linux Kernel up to 6.6.142/6.12.93/6.18.35/7.0.12 drm virtio_gpu_dma_fence_wait chain infinite loop

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.5$0-$5k1.25-

Summaryinfo

A vulnerability labeled as critical has been found in Linux Kernel up to 6.6.142/6.12.93/6.18.35/7.0.12. The impacted element is the function virtio_gpu_dma_fence_wait of the component drm. Such manipulation of the argument chain leads to infinite loop. This vulnerability is traded as CVE-2026-53190. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.6.142/6.12.93/6.18.35/7.0.12. Affected by this issue is the function virtio_gpu_dma_fence_wait of the component drm. The manipulation of the argument chain with an unknown input leads to a infinite loop vulnerability. Using CWE to declare the problem leads to CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. Impacted is availability. CVE summarizes:

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.

The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2026-53190 since 06/09/2026. Technical details are known, but there is no available exploit.

Upgrading to version 6.6.143, 6.12.94, 6.18.36 or 7.0.13 eliminates this vulnerability. Applying the patch 898bd0ccfed71651b881660c5d20ad73b5203174/73524e9f96a278b521f257a78a845c49eb522bc1/8348567a6afb24e2c9cafe8a321162d0eebe1411/c0fffc874c264292e769f26194a2a5e66ce31810/3f26bb732cc136ab20176697c92f32c9c84cb125 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Infinite loop
CWE: CWE-835 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.143/6.12.94/6.18.36/7.0.13
Patch: 898bd0ccfed71651b881660c5d20ad73b5203174/73524e9f96a278b521f257a78a845c49eb522bc1/8348567a6afb24e2c9cafe8a321162d0eebe1411/c0fffc874c264292e769f26194a2a5e66ce31810/3f26bb732cc136ab20176697c92f32c9c84cb125

Timelineinfo

06/09/2026 CVE reserved
06/25/2026 +16 days Advisory disclosed
06/25/2026 +0 days VulDB entry created
06/25/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-53190 (🔒)
GCVE (CVE): GCVE-0-2026-53190
GCVE (VulDB): GCVE-100-373754

Entryinfo

Created: 06/25/2026 12:13
Changes: 06/25/2026 12:13 (60)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!