<?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>Wed, 30 Sep 2026 21:34:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-71161 — dm-verity: disable recursive forward error correction</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-71161</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;dm-verity: disable recursive forward error correction&lt;/p&gt;
&lt;p&gt;There are two problems with the recursive correction:&lt;/p&gt;
&lt;p&gt;1. It may cause denial-of-service. In fec_read_bufs, there is a loop that
has 253 iterations. For each iteration, we may call verity_hash_for_block
recursively. There is a limit of 4 nested recursions - that means that
there may be at most 253^4 (4 billion) iterations. Red Hat QE team
actually created an image that pushes dm-verity to this limit - and this
image just makes the udev-worker process get stuck in the &amp;#39;D&amp;#39; state.&lt;/p&gt;
&lt;p&gt;2. It doesn&amp;#39;t work. In fec_read_bufs we store data into the variable
&amp;#34;fio-&amp;gt;bufs&amp;#34;, but fio bufs is shared between recursive invocations, if
&amp;#34;verity_hash_for_block&amp;#34; invoked correction recursively, it would
overwrite partially filled fio-&amp;gt;bufs.&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;dm-verity: disable recursive forward error correction&lt;/p&gt;
&lt;p&gt;There are two problems with the recursive correction:&lt;/p&gt;
&lt;p&gt;1. It may cause denial-of-service. In fec_read_bufs, there is a loop that
has 253 iterations. For each iteration, we may call verity_hash_for_block
recursively. There is a limit of 4 nested recursions - that means that
there may be at most 253^4 (4 billion) iterations. Red Hat QE team
actually created an image that pushes dm-verity to this limit - and this
image just makes the udev-worker process get stuck in the &amp;#39;D&amp;#39; state.&lt;/p&gt;
&lt;p&gt;2. It doesn&amp;#39;t work. In fec_read_bufs we store data into the variable
&amp;#34;fio-&amp;gt;bufs&amp;#34;, but fio bufs is shared between recursive invocations, if
&amp;#34;verity_hash_for_block&amp;#34; invoked correction recursively, it would
overwrite partially filled fio-&amp;gt;bufs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-71161</guid>
    </item>
  </channel>
</rss>
