<?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>Thu, 01 Oct 2026 04:39:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43145 — remoteproc: imx_rproc: Fix invalid loaded resource table detection</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43145</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: imx_rproc: Fix invalid loaded resource table detection&lt;/p&gt;
&lt;p&gt;imx_rproc_elf_find_loaded_rsc_table() may incorrectly report a loaded
resource table even when the current firmware does not provide one.&lt;/p&gt;
&lt;p&gt;When the device tree contains a &amp;#34;rsc-table&amp;#34; entry, priv-&amp;gt;rsc_table is
non-NULL and denotes where a resource table would be located if one is
present in memory. However, when the current firmware has no resource
table, rproc-&amp;gt;table_ptr is NULL. The function still returns
priv-&amp;gt;rsc_table, and the remoteproc core interprets this as a valid loaded
resource table.&lt;/p&gt;
&lt;p&gt;Fix this by returning NULL from imx_rproc_elf_find_loaded_rsc_table() when
there is no resource table for the current firmware (i.e. when
rproc-&amp;gt;table_ptr is NULL). This aligns the function&amp;#39;s semantics with the
remoteproc core: a loaded resource table is only reported when a valid
table_ptr exists.&lt;/p&gt;
&lt;p&gt;With this change, starting firmware without a resource table no longer
triggers a crash.&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: imx_rproc: Fix invalid loaded resource table detection&lt;/p&gt;
&lt;p&gt;imx_rproc_elf_find_loaded_rsc_table() may incorrectly report a loaded
resource table even when the current firmware does not provide one.&lt;/p&gt;
&lt;p&gt;When the device tree contains a &amp;#34;rsc-table&amp;#34; entry, priv-&amp;gt;rsc_table is
non-NULL and denotes where a resource table would be located if one is
present in memory. However, when the current firmware has no resource
table, rproc-&amp;gt;table_ptr is NULL. The function still returns
priv-&amp;gt;rsc_table, and the remoteproc core interprets this as a valid loaded
resource table.&lt;/p&gt;
&lt;p&gt;Fix this by returning NULL from imx_rproc_elf_find_loaded_rsc_table() when
there is no resource table for the current firmware (i.e. when
rproc-&amp;gt;table_ptr is NULL). This aligns the function&amp;#39;s semantics with the
remoteproc core: a loaded resource table is only reported when a valid
table_ptr exists.&lt;/p&gt;
&lt;p&gt;With this change, starting firmware without a resource table no longer
triggers a crash.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43145</guid>
    </item>
  </channel>
</rss>
