<?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 23:33:00 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-22124 — md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-22124</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;md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb&lt;/p&gt;
&lt;p&gt;In clustermd, separate write-intent-bitmaps are used for each cluster
node:&lt;/p&gt;
&lt;p&gt;0                    4k                     8k                    12k
-------------------------------------------------------------------
| idle                | md super            | bm super [0] + bits |
| bm bits[0, contd]   | bm super[1] + bits  | bm bits[1, contd]   |
| bm super[2] + bits  | bm bits [2, contd]  | bm super[3] + bits  |
| bm bits [3, contd]  |                     |                     |&lt;/p&gt;
&lt;p&gt;So in node 1, pg_index in __write_sb_page() could equal to
bitmap-&amp;gt;storage.file_pages. Then bitmap_limit will be calculated to
0. md_super_write() will be called with 0 size.
That means the first 4k sb area of node 1 will never be updated
through filemap_write_page().
This bug causes hang of mdadm/clustermd_tests/01r1_Grow_resize.&lt;/p&gt;
&lt;p&gt;Here use (pg_index % bitmap-&amp;gt;storage.file_pages) to make calculation
of bitmap_limit correct.&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;md/md-bitmap: fix wrong bitmap_limit for clustermd when write sb&lt;/p&gt;
&lt;p&gt;In clustermd, separate write-intent-bitmaps are used for each cluster
node:&lt;/p&gt;
&lt;p&gt;0                    4k                     8k                    12k
-------------------------------------------------------------------
| idle                | md super            | bm super [0] + bits |
| bm bits[0, contd]   | bm super[1] + bits  | bm bits[1, contd]   |
| bm super[2] + bits  | bm bits [2, contd]  | bm super[3] + bits  |
| bm bits [3, contd]  |                     |                     |&lt;/p&gt;
&lt;p&gt;So in node 1, pg_index in __write_sb_page() could equal to
bitmap-&amp;gt;storage.file_pages. Then bitmap_limit will be calculated to
0. md_super_write() will be called with 0 size.
That means the first 4k sb area of node 1 will never be updated
through filemap_write_page().
This bug causes hang of mdadm/clustermd_tests/01r1_Grow_resize.&lt;/p&gt;
&lt;p&gt;Here use (pg_index % bitmap-&amp;gt;storage.file_pages) to make calculation
of bitmap_limit correct.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-22124</guid>
    </item>
  </channel>
</rss>
