<?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 18:04:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50145 — dmaengine: sf-pdma: Add multithread support for a DMA channel</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50145</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: Add multithread support for a DMA channel&lt;/p&gt;
&lt;p&gt;When we get a DMA channel and try to use it in multiple threads it
will cause oops and hanging the system.&lt;/p&gt;
&lt;p&gt;% echo 64 &amp;gt; /sys/module/dmatest/parameters/threads_per_chan
% echo 10000 &amp;gt; /sys/module/dmatest/parameters/iterations
% echo 1 &amp;gt; /sys/module/dmatest/parameters/run
[   89.480664] Unable to handle kernel NULL pointer dereference at virtual
               address 00000000000000a0
[   89.488725] Oops [#1]
[   89.494708] CPU: 2 PID: 1008 Comm: dma0chan0-copy0 Not tainted
               5.17.0-rc5
[   89.509385] epc : vchan_find_desc+0x32/0x46
[   89.513553]  ra : sf_pdma_tx_status+0xca/0xd6&lt;/p&gt;
&lt;p&gt;This happens because of data race. Each thread rewrite channels&amp;#39;s
descriptor as soon as device_prep_dma_memcpy() is called. It leads to the
situation when the driver thinks that it uses right descriptor that
actually is freed or substituted for other one.&lt;/p&gt;
&lt;p&gt;With current fixes a descriptor changes its value only when it has
been used. A new descriptor is acquired from vc-&amp;gt;desc_issued queue that
is already filled with descriptors that are ready to be sent. Threads
have no direct access to DMA channel descriptor. Now it is just possible
to queue a descriptor for further processing.&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: Add multithread support for a DMA channel&lt;/p&gt;
&lt;p&gt;When we get a DMA channel and try to use it in multiple threads it
will cause oops and hanging the system.&lt;/p&gt;
&lt;p&gt;% echo 64 &amp;gt; /sys/module/dmatest/parameters/threads_per_chan
% echo 10000 &amp;gt; /sys/module/dmatest/parameters/iterations
% echo 1 &amp;gt; /sys/module/dmatest/parameters/run
[   89.480664] Unable to handle kernel NULL pointer dereference at virtual
               address 00000000000000a0
[   89.488725] Oops [#1]
[   89.494708] CPU: 2 PID: 1008 Comm: dma0chan0-copy0 Not tainted
               5.17.0-rc5
[   89.509385] epc : vchan_find_desc+0x32/0x46
[   89.513553]  ra : sf_pdma_tx_status+0xca/0xd6&lt;/p&gt;
&lt;p&gt;This happens because of data race. Each thread rewrite channels&amp;#39;s
descriptor as soon as device_prep_dma_memcpy() is called. It leads to the
situation when the driver thinks that it uses right descriptor that
actually is freed or substituted for other one.&lt;/p&gt;
&lt;p&gt;With current fixes a descriptor changes its value only when it has
been used. A new descriptor is acquired from vc-&amp;gt;desc_issued queue that
is already filled with descriptors that are ready to be sent. Threads
have no direct access to DMA channel descriptor. Now it is just possible
to queue a descriptor for further processing.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50145</guid>
    </item>
  </channel>
</rss>
