<?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>Tue, 29 Sep 2026 14:33:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-56712 — udmabuf: fix memory leak on last export_udmabuf() error path</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-56712</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;udmabuf: fix memory leak on last export_udmabuf() error path&lt;/p&gt;
&lt;p&gt;In export_udmabuf(), if dma_buf_fd() fails because the FD table is full, a
dma_buf owning the udmabuf has already been created; but the error handling
in udmabuf_create() will tear down the udmabuf without doing anything about
the containing dma_buf.&lt;/p&gt;
&lt;p&gt;This leaves a dma_buf in memory that contains a dangling pointer; though
that doesn&amp;#39;t seem to lead to anything bad except a memory leak.&lt;/p&gt;
&lt;p&gt;Fix it by moving the dma_buf_fd() call out of export_udmabuf() so that we
can give it different error handling.&lt;/p&gt;
&lt;p&gt;Note that the shape of this code changed a lot in commit 5e72b2b41a21
(&amp;#34;udmabuf: convert udmabuf driver to use folios&amp;#34;); but the memory leak
seems to have existed since the introduction of udmabuf.&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;udmabuf: fix memory leak on last export_udmabuf() error path&lt;/p&gt;
&lt;p&gt;In export_udmabuf(), if dma_buf_fd() fails because the FD table is full, a
dma_buf owning the udmabuf has already been created; but the error handling
in udmabuf_create() will tear down the udmabuf without doing anything about
the containing dma_buf.&lt;/p&gt;
&lt;p&gt;This leaves a dma_buf in memory that contains a dangling pointer; though
that doesn&amp;#39;t seem to lead to anything bad except a memory leak.&lt;/p&gt;
&lt;p&gt;Fix it by moving the dma_buf_fd() call out of export_udmabuf() so that we
can give it different error handling.&lt;/p&gt;
&lt;p&gt;Note that the shape of this code changed a lot in commit 5e72b2b41a21
(&amp;#34;udmabuf: convert udmabuf driver to use folios&amp;#34;); but the memory leak
seems to have existed since the introduction of udmabuf.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-56712</guid>
    </item>
  </channel>
</rss>
