<?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>Fri, 02 Oct 2026 12:11:39 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-54020 — dmaengine: sf-pdma: pdma_desc memory leak fix</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-54020</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;dmaengine: sf-pdma: pdma_desc memory leak fix&lt;/p&gt;
&lt;p&gt;Commit b2cc5c465c2c (&amp;#34;dmaengine: sf-pdma: Add multithread support for a
DMA channel&amp;#34;) changed sf_pdma_prep_dma_memcpy() to unconditionally
allocate a new sf_pdma_desc each time it is called.&lt;/p&gt;
&lt;p&gt;The driver previously recycled descs, by checking the in_use flag, only
allocating additional descs if the existing one was in use. This logic
was removed in commit b2cc5c465c2c (&amp;#34;dmaengine: sf-pdma: Add multithread
support for a DMA channel&amp;#34;), but sf_pdma_free_desc() was not changed to
handle the new behaviour.&lt;/p&gt;
&lt;p&gt;As a result, each time sf_pdma_prep_dma_memcpy() is called, the previous
descriptor is leaked, over time leading to memory starvation:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffffffe008447300 (size 192):
  comm &amp;#34;irq/39-mchp_dsc&amp;#34;, pid 343, jiffies 4294906910 (age 981.200s)
  hex dump (first 32 bytes):
    00 00 00 ff 00 00 00 00 b8 c1 00 00 00 00 00 00  ................
    00 00 70 08 10 00 00 00 00 00 00 c0 00 00 00 00  ..p.............
  backtrace:
    [&amp;lt;00000000064a04f4&amp;gt;] kmemleak_alloc+0x1e/0x28
    [&amp;lt;00000000018927a7&amp;gt;] kmem_cache_alloc+0x11e/0x178
    [&amp;lt;000000002aea8d16&amp;gt;] sf_pdma_prep_dma_memcpy+0x40/0x112&lt;/p&gt;
&lt;p&gt;Add the missing kfree() to sf_pdma_free_desc(), and remove the redundant
in_use flag.&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;dmaengine: sf-pdma: pdma_desc memory leak fix&lt;/p&gt;
&lt;p&gt;Commit b2cc5c465c2c (&amp;#34;dmaengine: sf-pdma: Add multithread support for a
DMA channel&amp;#34;) changed sf_pdma_prep_dma_memcpy() to unconditionally
allocate a new sf_pdma_desc each time it is called.&lt;/p&gt;
&lt;p&gt;The driver previously recycled descs, by checking the in_use flag, only
allocating additional descs if the existing one was in use. This logic
was removed in commit b2cc5c465c2c (&amp;#34;dmaengine: sf-pdma: Add multithread
support for a DMA channel&amp;#34;), but sf_pdma_free_desc() was not changed to
handle the new behaviour.&lt;/p&gt;
&lt;p&gt;As a result, each time sf_pdma_prep_dma_memcpy() is called, the previous
descriptor is leaked, over time leading to memory starvation:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffffffe008447300 (size 192):
  comm &amp;#34;irq/39-mchp_dsc&amp;#34;, pid 343, jiffies 4294906910 (age 981.200s)
  hex dump (first 32 bytes):
    00 00 00 ff 00 00 00 00 b8 c1 00 00 00 00 00 00  ................
    00 00 70 08 10 00 00 00 00 00 00 c0 00 00 00 00  ..p.............
  backtrace:
    [&amp;lt;00000000064a04f4&amp;gt;] kmemleak_alloc+0x1e/0x28
    [&amp;lt;00000000018927a7&amp;gt;] kmem_cache_alloc+0x11e/0x178
    [&amp;lt;000000002aea8d16&amp;gt;] sf_pdma_prep_dma_memcpy+0x40/0x112&lt;/p&gt;
&lt;p&gt;Add the missing kfree() to sf_pdma_free_desc(), and remove the redundant
in_use flag.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-54020</guid>
    </item>
  </channel>
</rss>
