<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 04:58:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-72095 — dma-fence: Make dma_fence_dedup_array() robust against 0-count input</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-72095</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-fence: Make dma_fence_dedup_array() robust against 0-count input&lt;/p&gt;
&lt;p&gt;dma_fence_dedup_array() returns 1 when called with num_fences == 0:
the for-loop body never executes, j stays at 0, and the final
`return ++j` yields 1. This contradicts both the kernel-doc (&amp;#34;Return:
Number of unique fences remaining in the array&amp;#34;) and the natural
expectation that 0 input gives 0 output.&lt;/p&gt;
&lt;p&gt;The caller __dma_fence_unwrap_merge() bails out via the
`if (count == 0 || count == 1)` fast path and so is save.&lt;/p&gt;
&lt;p&gt;But amdgpu_userq_wait_*() could reach the dedup call with a zero local
count and dereference an uninitialized fence slot in the array.&lt;/p&gt;
&lt;p&gt;Make the contract match the documentation by returning 0 early. This
also skips an unnecessary sort() call on an empty array.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dma-fence: Make dma_fence_dedup_array() robust against 0-count input&lt;/p&gt;
&lt;p&gt;dma_fence_dedup_array() returns 1 when called with num_fences == 0:
the for-loop body never executes, j stays at 0, and the final
`return ++j` yields 1. This contradicts both the kernel-doc (&amp;#34;Return:
Number of unique fences remaining in the array&amp;#34;) and the natural
expectation that 0 input gives 0 output.&lt;/p&gt;
&lt;p&gt;The caller __dma_fence_unwrap_merge() bails out via the
`if (count == 0 || count == 1)` fast path and so is save.&lt;/p&gt;
&lt;p&gt;But amdgpu_userq_wait_*() could reach the dedup call with a zero local
count and dereference an uninitialized fence slot in the array.&lt;/p&gt;
&lt;p&gt;Make the contract match the documentation by returning 0 early. This
also skips an unnecessary sort() call on an empty array.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-72095</guid>
    </item>
  </channel>
</rss>
