<?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>Fri, 02 Oct 2026 09:48:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-36965 — remoteproc: mediatek: Make sure IPI buffer fits in L2TCM</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-36965</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: mediatek: Make sure IPI buffer fits in L2TCM&lt;/p&gt;
&lt;p&gt;The IPI buffer location is read from the firmware that we load to the
System Companion Processor, and it&amp;#39;s not granted that both the SRAM
(L2TCM) size that is defined in the devicetree node is large enough
for that, and while this is especially true for multi-core SCP, it&amp;#39;s
still useful to check on single-core variants as well.&lt;/p&gt;
&lt;p&gt;Failing to perform this check may make this driver perform R/W
operations out of the L2TCM boundary, resulting (at best) in a
kernel panic.&lt;/p&gt;
&lt;p&gt;To fix that, check that the IPI buffer fits, otherwise return a
failure and refuse to boot the relevant SCP core (or the SCP at
all, if this is single core).&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: mediatek: Make sure IPI buffer fits in L2TCM&lt;/p&gt;
&lt;p&gt;The IPI buffer location is read from the firmware that we load to the
System Companion Processor, and it&amp;#39;s not granted that both the SRAM
(L2TCM) size that is defined in the devicetree node is large enough
for that, and while this is especially true for multi-core SCP, it&amp;#39;s
still useful to check on single-core variants as well.&lt;/p&gt;
&lt;p&gt;Failing to perform this check may make this driver perform R/W
operations out of the L2TCM boundary, resulting (at best) in a
kernel panic.&lt;/p&gt;
&lt;p&gt;To fix that, check that the IPI buffer fits, otherwise return a
failure and refuse to boot the relevant SCP core (or the SCP at
all, if this is single core).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-36965</guid>
    </item>
  </channel>
</rss>
