<?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://cve.radiocsirt.org</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, 06 Oct 2026 22:21:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52492 — dmaengine: fix NULL pointer in channel unregistration function</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2023-52492</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: fix NULL pointer in channel unregistration function&lt;/p&gt;
&lt;p&gt;__dma_async_device_channel_register() can fail. In case of failure,
chan-&amp;gt;local is freed (with free_percpu()), and chan-&amp;gt;local is nullified.
When dma_async_device_unregister() is called (because of managed API or
intentionally by DMA controller driver), channels are unconditionally
unregistered, leading to this NULL pointer:
[    1.318693] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d0
[...]
[    1.484499] Call trace:
[    1.486930]  device_del+0x40/0x394
[    1.490314]  device_unregister+0x20/0x7c
[    1.494220]  __dma_async_device_channel_unregister+0x68/0xc0&lt;/p&gt;
&lt;p&gt;Look at dma_async_device_register() function error path, channel device
unregistration is done only if chan-&amp;gt;local is not NULL.&lt;/p&gt;
&lt;p&gt;Then add the same condition at the beginning of
__dma_async_device_channel_unregister() function, to avoid NULL pointer
issue whatever the API used to reach this function.&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: fix NULL pointer in channel unregistration function&lt;/p&gt;
&lt;p&gt;__dma_async_device_channel_register() can fail. In case of failure,
chan-&amp;gt;local is freed (with free_percpu()), and chan-&amp;gt;local is nullified.
When dma_async_device_unregister() is called (because of managed API or
intentionally by DMA controller driver), channels are unconditionally
unregistered, leading to this NULL pointer:
[    1.318693] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000d0
[...]
[    1.484499] Call trace:
[    1.486930]  device_del+0x40/0x394
[    1.490314]  device_unregister+0x20/0x7c
[    1.494220]  __dma_async_device_channel_unregister+0x68/0xc0&lt;/p&gt;
&lt;p&gt;Look at dma_async_device_register() function error path, channel device
unregistration is done only if chan-&amp;gt;local is not NULL.&lt;/p&gt;
&lt;p&gt;Then add the same condition at the beginning of
__dma_async_device_channel_unregister() function, to avoid NULL pointer
issue whatever the API used to reach this function.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2023-52492</guid>
    </item>
  </channel>
</rss>
