<?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-29T21:01:41.781887+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-2026-93192</id>
    <title>CVE-2026-93192 — drm/v3d: Clear queue-&gt;active_job when v3d_fence_create() fails</title>
    <updated>2026-09-29T21:01:41.804610+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/v3d: Clear queue-&gt;active_job when v3d_fence_create() fails</p>
<p>The run_job() callbacks for BIN, RENDER, TFU and CSD assign the incoming
job to queue-&gt;active_job before calling v3d_fence_create(). If
v3d_fence_create() fails, the callback returns NULL without clearing
active_job, leaving a dangling pointer.</p>
<p>Create a failure path in all run_job() callbacks that clears the active
job before returning NULL. The BIN path takes queue-&gt;queue_lock around the
clear as it races against v3d_overflow_mem_work(); RENDER, TFU and CSD
paths have no concurrent reader, so the clear is lock-free.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-93192"/>
  </entry>
</feed>
