<?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>Mon, 28 Sep 2026 09:41:25 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49935 — dma-buf/dma-resv: check if the new fence is really later</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49935</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-buf/dma-resv: check if the new fence is really later&lt;/p&gt;
&lt;p&gt;Previously when we added a fence to a dma_resv object we always
assumed the the newer than all the existing fences.&lt;/p&gt;
&lt;p&gt;With Jason&amp;#39;s work to add an UAPI to explicit export/import that&amp;#39;s not
necessary the case any more. So without this check we would allow
userspace to force the kernel into an use after free error.&lt;/p&gt;
&lt;p&gt;Since the change is very small and defensive it&amp;#39;s probably a good
idea to backport this to stable kernels as well just in case others
are using the dma_resv object in the same way.&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-buf/dma-resv: check if the new fence is really later&lt;/p&gt;
&lt;p&gt;Previously when we added a fence to a dma_resv object we always
assumed the the newer than all the existing fences.&lt;/p&gt;
&lt;p&gt;With Jason&amp;#39;s work to add an UAPI to explicit export/import that&amp;#39;s not
necessary the case any more. So without this check we would allow
userspace to force the kernel into an use after free error.&lt;/p&gt;
&lt;p&gt;Since the change is very small and defensive it&amp;#39;s probably a good
idea to backport this to stable kernels as well just in case others
are using the dma_resv object in the same way.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49935</guid>
    </item>
  </channel>
</rss>
