<?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 15:10:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23474 — mtd: Avoid boot crash in RedBoot partition table parser</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23474</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mtd: Avoid boot crash in RedBoot partition table parser&lt;/p&gt;
&lt;p&gt;Given CONFIG_FORTIFY_SOURCE=y and a recent compiler,
commit 439a1bcac648 (&amp;#34;fortify: Use __builtin_dynamic_object_size() when
available&amp;#34;) produces the warning below and an oops.&lt;/p&gt;
&lt;p&gt;Searching for RedBoot partition table in 50000000.flash at offset 0x7e0000
    ------------[ cut here ]------------
    WARNING: lib/string_helpers.c:1035 at 0xc029e04c, CPU#0: swapper/0/1
    memcmp: detected buffer overflow: 15 byte read of buffer size 14
    Modules linked in:
    CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.19.0 #1 NONE&lt;/p&gt;
&lt;p&gt;As Kees said, &amp;#34;&amp;#39;names&amp;#39; is pointing to the final &amp;#39;namelen&amp;#39; many bytes
of the allocation ... &amp;#39;namelen&amp;#39; could be basically any length at all.
This fortify warning looks legit to me -- this code used to be reading
beyond the end of the allocation.&amp;#34;&lt;/p&gt;
&lt;p&gt;Since the size of the dynamic allocation is calculated with strlen()
we can use strcmp() instead of memcmp() and remain within bounds.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC S7-1500 CPU 1518-4 PN/DP MFP, Siemens SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP, Siemens SIPLUS S7-1500 CPU 1518-4 PN/DP MFP&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mtd: Avoid boot crash in RedBoot partition table parser&lt;/p&gt;
&lt;p&gt;Given CONFIG_FORTIFY_SOURCE=y and a recent compiler,
commit 439a1bcac648 (&amp;#34;fortify: Use __builtin_dynamic_object_size() when
available&amp;#34;) produces the warning below and an oops.&lt;/p&gt;
&lt;p&gt;Searching for RedBoot partition table in 50000000.flash at offset 0x7e0000
    ------------[ cut here ]------------
    WARNING: lib/string_helpers.c:1035 at 0xc029e04c, CPU#0: swapper/0/1
    memcmp: detected buffer overflow: 15 byte read of buffer size 14
    Modules linked in:
    CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.19.0 #1 NONE&lt;/p&gt;
&lt;p&gt;As Kees said, &amp;#34;&amp;#39;names&amp;#39; is pointing to the final &amp;#39;namelen&amp;#39; many bytes
of the allocation ... &amp;#39;namelen&amp;#39; could be basically any length at all.
This fortify warning looks legit to me -- this code used to be reading
beyond the end of the allocation.&amp;#34;&lt;/p&gt;
&lt;p&gt;Since the size of the dynamic allocation is calculated with strlen()
we can use strcmp() instead of memcmp() and remain within bounds.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23474</guid>
    </item>
  </channel>
</rss>
