<?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 14:29:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53777 — erofs: kill hooked chains to avoid loops on deduplicated compressed images</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53777</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;erofs: kill hooked chains to avoid loops on deduplicated compressed images&lt;/p&gt;
&lt;p&gt;After heavily stressing EROFS with several images which include a
hand-crafted image of repeated patterns for more than 46 days, I found
two chains could be linked with each other almost simultaneously and
form a loop so that the entire loop won&amp;#39;t be submitted.  As a
consequence, the corresponding file pages will remain locked forever.&lt;/p&gt;
&lt;p&gt;It can be _only_ observed on data-deduplicated compressed images.
For example, consider two chains with five pclusters in total:
	Chain 1:  2-&amp;gt;3-&amp;gt;4-&amp;gt;5    -- The tail pcluster is 5;
        Chain 2:  5-&amp;gt;1-&amp;gt;2       -- The tail pcluster is 2.&lt;/p&gt;
&lt;p&gt;Chain 2 could link to Chain 1 with pcluster 5; and Chain 1 could link
to Chain 2 at the same time with pcluster 2.&lt;/p&gt;
&lt;p&gt;Since hooked chains are all linked locklessly now, I have no idea how
to simply avoid the race.  Instead, let&amp;#39;s avoid hooked chains completely
until I could work out a proper way to fix this and end users finally
tell us that it&amp;#39;s needed to add it back.&lt;/p&gt;
&lt;p&gt;Actually, this optimization can be found with multi-threaded workloads
(especially even more often on deduplicated compressed images), yet I&amp;#39;m
not sure about the overall system impacts of not having this compared
with implementation complexity.&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;erofs: kill hooked chains to avoid loops on deduplicated compressed images&lt;/p&gt;
&lt;p&gt;After heavily stressing EROFS with several images which include a
hand-crafted image of repeated patterns for more than 46 days, I found
two chains could be linked with each other almost simultaneously and
form a loop so that the entire loop won&amp;#39;t be submitted.  As a
consequence, the corresponding file pages will remain locked forever.&lt;/p&gt;
&lt;p&gt;It can be _only_ observed on data-deduplicated compressed images.
For example, consider two chains with five pclusters in total:
	Chain 1:  2-&amp;gt;3-&amp;gt;4-&amp;gt;5    -- The tail pcluster is 5;
        Chain 2:  5-&amp;gt;1-&amp;gt;2       -- The tail pcluster is 2.&lt;/p&gt;
&lt;p&gt;Chain 2 could link to Chain 1 with pcluster 5; and Chain 1 could link
to Chain 2 at the same time with pcluster 2.&lt;/p&gt;
&lt;p&gt;Since hooked chains are all linked locklessly now, I have no idea how
to simply avoid the race.  Instead, let&amp;#39;s avoid hooked chains completely
until I could work out a proper way to fix this and end users finally
tell us that it&amp;#39;s needed to add it back.&lt;/p&gt;
&lt;p&gt;Actually, this optimization can be found with multi-threaded workloads
(especially even more often on deduplicated compressed images), yet I&amp;#39;m
not sure about the overall system impacts of not having this compared
with implementation complexity.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53777</guid>
    </item>
  </channel>
</rss>
