CVE-2026-53190
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 6.6.143
- Linux Kernel < 6.12.94
- Linux Kernel < 6.18.36
- Linux Kernel < 7.0.13
- Linux Kernel 7.1
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-53190.md and follow it. Check whether this project is affected by CVE-2026-53190. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/3f26bb732cc136ab20176697c92f32c9c84cb125
- https://git.kernel.org/stable/c/73524e9f96a278b521f257a78a845c49eb522bc1
- https://git.kernel.org/stable/c/8348567a6afb24e2c9cafe8a321162d0eebe1411
- https://git.kernel.org/stable/c/898bd0ccfed71651b881660c5d20ad73b5203174
- https://git.kernel.org/stable/c/c0fffc874c264292e769f26194a2a5e66ce31810
References
- https://git.kernel.org/stable/c/3f26bb732cc136ab20176697c92f32c9c84cb125
- https://git.kernel.org/stable/c/73524e9f96a278b521f257a78a845c49eb522bc1
- https://git.kernel.org/stable/c/8348567a6afb24e2c9cafe8a321162d0eebe1411
- https://git.kernel.org/stable/c/898bd0ccfed71651b881660c5d20ad73b5203174
- https://git.kernel.org/stable/c/c0fffc874c264292e769f26194a2a5e66ce31810