<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T20:52:11.527644+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-71314</id>
    <title>CVE-2025-71314 — drm/panthor: Recover from panthor_gpu_flush_caches() failures</title>
    <updated>2026-09-29T20:52:11.529030+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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'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'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></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-71314"/>
  </entry>
</feed>
