<?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 19:16:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40113 — remoteproc: qcom: pas: Shutdown lite ADSP DTB on X1E</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40113</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: qcom: pas: Shutdown lite ADSP DTB on X1E&lt;/p&gt;
&lt;p&gt;The ADSP firmware on X1E has separate firmware binaries for the main
firmware and the DTB. The same applies for the &amp;#34;lite&amp;#34; firmware loaded by
the boot firmware.&lt;/p&gt;
&lt;p&gt;When preparing to load the new ADSP firmware we shutdown the lite_pas_id
for the main firmware, but we don&amp;#39;t shutdown the corresponding lite pas_id
for the DTB. The fact that we&amp;#39;re leaving it &amp;#34;running&amp;#34; forever becomes
obvious if you try to reuse (or just access) the memory region used by the
&amp;#34;lite&amp;#34; firmware: The &amp;amp;adsp_boot_mem is accessible, but accessing the
&amp;amp;adsp_boot_dtb_mem results in a crash.&lt;/p&gt;
&lt;p&gt;We don&amp;#39;t support reusing the memory regions currently, but nevertheless we
should not keep part of the lite firmware running. Fix this by adding the
lite_dtb_pas_id and shutting it down as well.&lt;/p&gt;
&lt;p&gt;We don&amp;#39;t have a way to detect if the lite firmware is actually running yet,
so ignore the return status of qcom_scm_pas_shutdown() for now. This was
already the case before, the assignment to &amp;#34;ret&amp;#34; is not used anywhere.&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: qcom: pas: Shutdown lite ADSP DTB on X1E&lt;/p&gt;
&lt;p&gt;The ADSP firmware on X1E has separate firmware binaries for the main
firmware and the DTB. The same applies for the &amp;#34;lite&amp;#34; firmware loaded by
the boot firmware.&lt;/p&gt;
&lt;p&gt;When preparing to load the new ADSP firmware we shutdown the lite_pas_id
for the main firmware, but we don&amp;#39;t shutdown the corresponding lite pas_id
for the DTB. The fact that we&amp;#39;re leaving it &amp;#34;running&amp;#34; forever becomes
obvious if you try to reuse (or just access) the memory region used by the
&amp;#34;lite&amp;#34; firmware: The &amp;amp;adsp_boot_mem is accessible, but accessing the
&amp;amp;adsp_boot_dtb_mem results in a crash.&lt;/p&gt;
&lt;p&gt;We don&amp;#39;t support reusing the memory regions currently, but nevertheless we
should not keep part of the lite firmware running. Fix this by adding the
lite_dtb_pas_id and shutting it down as well.&lt;/p&gt;
&lt;p&gt;We don&amp;#39;t have a way to detect if the lite firmware is actually running yet,
so ignore the return status of qcom_scm_pas_shutdown() for now. This was
already the case before, the assignment to &amp;#34;ret&amp;#34; is not used anywhere.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40113</guid>
    </item>
  </channel>
</rss>
