https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 08 Oct 2026 10:10:22 +0000 https://vulnerability.circl.lu/vuln/cve-2025-37930 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/nouveau: Fix WARN_ON in nouveau_fence_context_kill()</p> <p>Nouveau is mostly designed in a way that it&#39;s expected that fences only ever get signaled through nouveau_fence_signal(). However, in at least one other place, nouveau_fence_done(), can signal fences, too. If that happens (race) a signaled fence remains in the pending list for a while, until it gets removed by nouveau_fence_update().</p> <p>Should nouveau_fence_context_kill() run in the meantime, this would be a bug because the function would attempt to set an error code on an already signaled fence.</p> <p>Have nouveau_fence_context_kill() check for a fence being signaled.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/nouveau: Fix WARN_ON in nouveau_fence_context_kill()</p> <p>Nouveau is mostly designed in a way that it&#39;s expected that fences only ever get signaled through nouveau_fence_signal(). However, in at least one other place, nouveau_fence_done(), can signal fences, too. If that happens (race) a signaled fence remains in the pending list for a while, until it gets removed by nouveau_fence_update().</p> <p>Should nouveau_fence_context_kill() run in the meantime, this would be a bug because the function would attempt to set an error code on an already signaled fence.</p> <p>Have nouveau_fence_context_kill() check for a fence being signaled.</p> https://vulnerability.circl.lu/vuln/cve-2025-37930