<?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>Mon, 28 Sep 2026 18:16:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40241 — erofs: fix crafted invalid cases for encoded extents</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40241</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: fix crafted invalid cases for encoded extents&lt;/p&gt;
&lt;p&gt;Robert recently reported two corrupted images that can cause system
crashes, which are related to the new encoded extents introduced
in Linux 6.15:&lt;/p&gt;
&lt;p&gt;- The first one [1] has plen != 0 (e.g. plen == 0x2000000) but
    (plen &amp;amp; Z_EROFS_EXTENT_PLEN_MASK) == 0. It is used to represent
    special extents such as sparse extents (!EROFS_MAP_MAPPED), but
    previously only plen == 0 was handled;&lt;/p&gt;
&lt;p&gt;- The second one [2] has pa 0xffffffffffdcffed and plen 0xb4000,
    then &amp;#34;cur [0xfffffffffffff000] += bvec.bv_len [0x1000]&amp;#34; in
    &amp;#34;} while ((cur += bvec.bv_len) &amp;lt; end);&amp;#34; wraps around, causing an
    out-of-bound access of pcl-&amp;gt;compressed_bvecs[] in
    z_erofs_submit_queue().  EROFS only supports 48-bit physical block
    addresses (up to 1EiB for 4k blocks), so add a sanity check to
    enforce this.&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: fix crafted invalid cases for encoded extents&lt;/p&gt;
&lt;p&gt;Robert recently reported two corrupted images that can cause system
crashes, which are related to the new encoded extents introduced
in Linux 6.15:&lt;/p&gt;
&lt;p&gt;- The first one [1] has plen != 0 (e.g. plen == 0x2000000) but
    (plen &amp;amp; Z_EROFS_EXTENT_PLEN_MASK) == 0. It is used to represent
    special extents such as sparse extents (!EROFS_MAP_MAPPED), but
    previously only plen == 0 was handled;&lt;/p&gt;
&lt;p&gt;- The second one [2] has pa 0xffffffffffdcffed and plen 0xb4000,
    then &amp;#34;cur [0xfffffffffffff000] += bvec.bv_len [0x1000]&amp;#34; in
    &amp;#34;} while ((cur += bvec.bv_len) &amp;lt; end);&amp;#34; wraps around, causing an
    out-of-bound access of pcl-&amp;gt;compressed_bvecs[] in
    z_erofs_submit_queue().  EROFS only supports 48-bit physical block
    addresses (up to 1EiB for 4k blocks), so add a sanity check to
    enforce this.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40241</guid>
    </item>
  </channel>
</rss>
