<?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>Sat, 03 Oct 2026 23:41:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38419 — remoteproc: core: Cleanup acquired resources when rproc_handle_resources() fails in rproc_attach()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-38419</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: Cleanup acquired resources when rproc_handle_resources() fails in rproc_attach()&lt;/p&gt;
&lt;p&gt;When rproc-&amp;gt;state = RPROC_DETACHED and rproc_attach() is used
to attach to the remote processor, if rproc_handle_resources()
returns a failure, the resources allocated by imx_rproc_prepare()
should be released, otherwise the following memory leak will occur.&lt;/p&gt;
&lt;p&gt;Since almost the same thing is done in imx_rproc_prepare() and
rproc_resource_cleanup(), Function rproc_resource_cleanup() is able
to deal with empty lists so it is better to fix the &amp;#34;goto&amp;#34; statements
in rproc_attach(). replace the &amp;#34;unprepare_device&amp;#34; goto statement with
&amp;#34;clean_up_resources&amp;#34; and get rid of the &amp;#34;unprepare_device&amp;#34; label.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff0000861c5d00 (size 128):
comm &amp;#34;kworker/u12:3&amp;#34;, pid 59, jiffies 4294893509 (age 149.220s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 02 88 00 00 00 00 00 00 10 00 00 00 00 00 ............
backtrace:
 [&amp;lt;00000000f949fe18&amp;gt;] slab_post_alloc_hook+0x98/0x37c
 [&amp;lt;00000000adbfb3e7&amp;gt;] __kmem_cache_alloc_node+0x138/0x2e0
 [&amp;lt;00000000521c0345&amp;gt;] kmalloc_trace+0x40/0x158
 [&amp;lt;000000004e330a49&amp;gt;] rproc_mem_entry_init+0x60/0xf8
 [&amp;lt;000000002815755e&amp;gt;] imx_rproc_prepare+0xe0/0x180
 [&amp;lt;0000000003f61b4e&amp;gt;] rproc_boot+0x2ec/0x528
 [&amp;lt;00000000e7e994ac&amp;gt;] rproc_add+0x124/0x17c
 [&amp;lt;0000000048594076&amp;gt;] imx_rproc_probe+0x4ec/0x5d4
 [&amp;lt;00000000efc298a1&amp;gt;] platform_probe+0x68/0xd8
 [&amp;lt;0000…&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: Cleanup acquired resources when rproc_handle_resources() fails in rproc_attach()&lt;/p&gt;
&lt;p&gt;When rproc-&amp;gt;state = RPROC_DETACHED and rproc_attach() is used
to attach to the remote processor, if rproc_handle_resources()
returns a failure, the resources allocated by imx_rproc_prepare()
should be released, otherwise the following memory leak will occur.&lt;/p&gt;
&lt;p&gt;Since almost the same thing is done in imx_rproc_prepare() and
rproc_resource_cleanup(), Function rproc_resource_cleanup() is able
to deal with empty lists so it is better to fix the &amp;#34;goto&amp;#34; statements
in rproc_attach(). replace the &amp;#34;unprepare_device&amp;#34; goto statement with
&amp;#34;clean_up_resources&amp;#34; and get rid of the &amp;#34;unprepare_device&amp;#34; label.&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff0000861c5d00 (size 128):
comm &amp;#34;kworker/u12:3&amp;#34;, pid 59, jiffies 4294893509 (age 149.220s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 02 88 00 00 00 00 00 00 10 00 00 00 00 00 ............
backtrace:
 [&amp;lt;00000000f949fe18&amp;gt;] slab_post_alloc_hook+0x98/0x37c
 [&amp;lt;00000000adbfb3e7&amp;gt;] __kmem_cache_alloc_node+0x138/0x2e0
 [&amp;lt;00000000521c0345&amp;gt;] kmalloc_trace+0x40/0x158
 [&amp;lt;000000004e330a49&amp;gt;] rproc_mem_entry_init+0x60/0xf8
 [&amp;lt;000000002815755e&amp;gt;] imx_rproc_prepare+0xe0/0x180
 [&amp;lt;0000000003f61b4e&amp;gt;] rproc_boot+0x2ec/0x528
 [&amp;lt;00000000e7e994ac&amp;gt;] rproc_add+0x124/0x17c
 [&amp;lt;0000000048594076&amp;gt;] imx_rproc_probe+0x4ec/0x5d4
 [&amp;lt;00000000efc298a1&amp;gt;] platform_probe+0x68/0xd8
 [&amp;lt;0000…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-38419</guid>
    </item>
  </channel>
</rss>
