https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 20:51:50 +0000 https://vulnerability.circl.lu/vuln/cve-2025-71314 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/panthor: Recover from panthor_gpu_flush_caches() failures</p> <p>We have seen a few cases where the whole memory subsystem is blocked and flush operations never complete. When that happens, we want to:</p> <p>- schedule a reset, so we can recover from this situation - in the reset path, we need to reset the pending_reqs so we can send new commands after the reset - if more panthor_gpu_flush_caches() operations are queued after the timeout, we skip them and return -EIO directly to avoid needless waits (the memory block won&#39;t miraculously work again)</p> <p>Note that we drop the WARN_ON()s because these hangs can be triggered with buggy GPU jobs created by the UMD, and there&#39;s no way we can prevent it. We do keep the error messages though.</p> <p>v2: - New patch</p> <p>v3: - Collect R-b - Explicitly mention the fact we dropped the WARN_ON()s in the commit message</p> <p>v4: - No changes</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>drm/panthor: Recover from panthor_gpu_flush_caches() failures</p> <p>We have seen a few cases where the whole memory subsystem is blocked and flush operations never complete. When that happens, we want to:</p> <p>- schedule a reset, so we can recover from this situation - in the reset path, we need to reset the pending_reqs so we can send new commands after the reset - if more panthor_gpu_flush_caches() operations are queued after the timeout, we skip them and return -EIO directly to avoid needless waits (the memory block won&#39;t miraculously work again)</p> <p>Note that we drop the WARN_ON()s because these hangs can be triggered with buggy GPU jobs created by the UMD, and there&#39;s no way we can prevent it. We do keep the error messages though.</p> <p>v2: - New patch</p> <p>v3: - Collect R-b - Explicitly mention the fact we dropped the WARN_ON()s in the commit message</p> <p>v4: - No changes</p> https://vulnerability.circl.lu/vuln/cve-2025-71314