<?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:57:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38418 — remoteproc: core: Release rproc-&gt;clean_table after rproc_attach() fails</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38418</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;remoteproc: core: Release rproc-&amp;gt;clean_table after rproc_attach() fails&lt;/p&gt;
&lt;p&gt;When rproc-&amp;gt;state = RPROC_DETACHED is attached to remote processor
through rproc_attach(), if rproc_handle_resources() returns failure,
then the clean table should be released, otherwise the following
memory leak will occur.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff000086a99800 (size 1024):
comm &amp;#34;kworker/u12:3&amp;#34;, pid 59, jiffies 4294893670 (age 121.140s)
hex dump (first 32 bytes):
00 00 00 00 00 80 00 00 00 00 00 00 00 00 10 00 ............
00 00 00 00 00 00 08 00 00 00 00 00 00 00 00 00 ............
backtrace:
 [&amp;lt;000000008bbe4ca8&amp;gt;] slab_post_alloc_hook+0x98/0x3fc
 [&amp;lt;000000003b8a272b&amp;gt;] __kmem_cache_alloc_node+0x13c/0x230
 [&amp;lt;000000007a507c51&amp;gt;] __kmalloc_node_track_caller+0x5c/0x260
 [&amp;lt;0000000037818dae&amp;gt;] kmemdup+0x34/0x60
 [&amp;lt;00000000610f7f57&amp;gt;] rproc_boot+0x35c/0x56c
 [&amp;lt;0000000065f8871a&amp;gt;] rproc_add+0x124/0x17c
 [&amp;lt;00000000497416ee&amp;gt;] imx_rproc_probe+0x4ec/0x5d4
 [&amp;lt;000000003bcaa37d&amp;gt;] platform_probe+0x68/0xd8
 [&amp;lt;00000000771577f9&amp;gt;] really_probe+0x110/0x27c
 [&amp;lt;00000000531fea59&amp;gt;] __driver_probe_device+0x78/0x12c
 [&amp;lt;0000000080036a04&amp;gt;] driver_probe_device+0x3c/0x118
 [&amp;lt;000000007e0bddcb&amp;gt;] __device_attach_driver+0xb8/0xf8
 [&amp;lt;000000000cf1fa33&amp;gt;] bus_for_each_drv+0x84/0xe4
 [&amp;lt;000000001a53b53e&amp;gt;] __device_attach+0xfc/0x18c
 [&amp;lt;00000000d1a2a32c&amp;gt;] device_initial_probe+0x14/0x20
 [&amp;lt;00000000d8f8b7ae&amp;gt;] bus_probe_device+0xb0/0xb4
 unreferenced object 0xffff0000864c9690 (size…&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;remoteproc: core: Release rproc-&amp;gt;clean_table after rproc_attach() fails&lt;/p&gt;
&lt;p&gt;When rproc-&amp;gt;state = RPROC_DETACHED is attached to remote processor
through rproc_attach(), if rproc_handle_resources() returns failure,
then the clean table should be released, otherwise the following
memory leak will occur.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff000086a99800 (size 1024):
comm &amp;#34;kworker/u12:3&amp;#34;, pid 59, jiffies 4294893670 (age 121.140s)
hex dump (first 32 bytes):
00 00 00 00 00 80 00 00 00 00 00 00 00 00 10 00 ............
00 00 00 00 00 00 08 00 00 00 00 00 00 00 00 00 ............
backtrace:
 [&amp;lt;000000008bbe4ca8&amp;gt;] slab_post_alloc_hook+0x98/0x3fc
 [&amp;lt;000000003b8a272b&amp;gt;] __kmem_cache_alloc_node+0x13c/0x230
 [&amp;lt;000000007a507c51&amp;gt;] __kmalloc_node_track_caller+0x5c/0x260
 [&amp;lt;0000000037818dae&amp;gt;] kmemdup+0x34/0x60
 [&amp;lt;00000000610f7f57&amp;gt;] rproc_boot+0x35c/0x56c
 [&amp;lt;0000000065f8871a&amp;gt;] rproc_add+0x124/0x17c
 [&amp;lt;00000000497416ee&amp;gt;] imx_rproc_probe+0x4ec/0x5d4
 [&amp;lt;000000003bcaa37d&amp;gt;] platform_probe+0x68/0xd8
 [&amp;lt;00000000771577f9&amp;gt;] really_probe+0x110/0x27c
 [&amp;lt;00000000531fea59&amp;gt;] __driver_probe_device+0x78/0x12c
 [&amp;lt;0000000080036a04&amp;gt;] driver_probe_device+0x3c/0x118
 [&amp;lt;000000007e0bddcb&amp;gt;] __device_attach_driver+0xb8/0xf8
 [&amp;lt;000000000cf1fa33&amp;gt;] bus_for_each_drv+0x84/0xe4
 [&amp;lt;000000001a53b53e&amp;gt;] __device_attach+0xfc/0x18c
 [&amp;lt;00000000d1a2a32c&amp;gt;] device_initial_probe+0x14/0x20
 [&amp;lt;00000000d8f8b7ae&amp;gt;] bus_probe_device+0xb0/0xb4
 unreferenced object 0xffff0000864c9690 (size…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38418</guid>
    </item>
  </channel>
</rss>
