<?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 22:06:39 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90279 — md/raid5: round bitmap stripes with sector division</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90279</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/raid5: round bitmap stripes with sector division&lt;/p&gt;
&lt;p&gt;raid5_bitmap_sector_map() aligns the array range to full RAID5 stripe
widths before converting it to component sectors. That width is
chunk_sectors multiplied by the number of data disks, and it is not
always a power of two.&lt;/p&gt;
&lt;p&gt;Reproduce with a 4-disk RAID5, 1024-sector chunks, and three data disks.
The full-stripe width is 3072 sectors. For a one-sector write at array
sector 3072, correct rounding gives array range [3072, 6144), which maps
to component range [1024, 2048). The old round_down()/round_up() logic
instead gives [1024, 4096), which maps to [0, 1024).&lt;/p&gt;
&lt;p&gt;Use sector_div() based arithmetic so the rounded range is aligned to the
actual RAID5 stripe width.&lt;/p&gt;
&lt;p&gt;The deterministic mapper test now reports the fixed component range as
[1024, 2048), while the old mask-based range was [0, 1024).&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/raid5: round bitmap stripes with sector division&lt;/p&gt;
&lt;p&gt;raid5_bitmap_sector_map() aligns the array range to full RAID5 stripe
widths before converting it to component sectors. That width is
chunk_sectors multiplied by the number of data disks, and it is not
always a power of two.&lt;/p&gt;
&lt;p&gt;Reproduce with a 4-disk RAID5, 1024-sector chunks, and three data disks.
The full-stripe width is 3072 sectors. For a one-sector write at array
sector 3072, correct rounding gives array range [3072, 6144), which maps
to component range [1024, 2048). The old round_down()/round_up() logic
instead gives [1024, 4096), which maps to [0, 1024).&lt;/p&gt;
&lt;p&gt;Use sector_div() based arithmetic so the rounded range is aligned to the
actual RAID5 stripe width.&lt;/p&gt;
&lt;p&gt;The deterministic mapper test now reports the fixed component range as
[1024, 2048), while the old mask-based range was [0, 1024).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90279</guid>
    </item>
  </channel>
</rss>
