<?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 17:11:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23238 — romfs: check sb_set_blocksize() return value</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-23238</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens RUGGEDCOM RST2428P&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;romfs: check sb_set_blocksize() return value&lt;/p&gt;
&lt;p&gt;romfs_fill_super() ignores the return value of sb_set_blocksize(), which
can fail if the requested block size is incompatible with the block
device&amp;#39;s configuration.&lt;/p&gt;
&lt;p&gt;This can be triggered by setting a loop device&amp;#39;s block size larger than
PAGE_SIZE using ioctl(LOOP_SET_BLOCK_SIZE, 32768), then mounting a romfs
filesystem on that device.&lt;/p&gt;
&lt;p&gt;When sb_set_blocksize(sb, ROMBSIZE) is called with ROMBSIZE=4096 but the
device has logical_block_size=32768, bdev_validate_blocksize() fails
because the requested size is smaller than the device&amp;#39;s logical block
size. sb_set_blocksize() returns 0 (failure), but romfs ignores this and
continues mounting.&lt;/p&gt;
&lt;p&gt;The superblock&amp;#39;s block size remains at the device&amp;#39;s logical block size
(32768). Later, when sb_bread() attempts I/O with this oversized block
size, it triggers a kernel BUG in folio_set_bh():&lt;/p&gt;
&lt;p&gt;kernel BUG at fs/buffer.c:1582!
    BUG_ON(size &amp;gt; PAGE_SIZE);&lt;/p&gt;
&lt;p&gt;Fix by checking the return value of sb_set_blocksize() and failing the
mount with -EINVAL if it returns 0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens RUGGEDCOM RST2428P&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;romfs: check sb_set_blocksize() return value&lt;/p&gt;
&lt;p&gt;romfs_fill_super() ignores the return value of sb_set_blocksize(), which
can fail if the requested block size is incompatible with the block
device&amp;#39;s configuration.&lt;/p&gt;
&lt;p&gt;This can be triggered by setting a loop device&amp;#39;s block size larger than
PAGE_SIZE using ioctl(LOOP_SET_BLOCK_SIZE, 32768), then mounting a romfs
filesystem on that device.&lt;/p&gt;
&lt;p&gt;When sb_set_blocksize(sb, ROMBSIZE) is called with ROMBSIZE=4096 but the
device has logical_block_size=32768, bdev_validate_blocksize() fails
because the requested size is smaller than the device&amp;#39;s logical block
size. sb_set_blocksize() returns 0 (failure), but romfs ignores this and
continues mounting.&lt;/p&gt;
&lt;p&gt;The superblock&amp;#39;s block size remains at the device&amp;#39;s logical block size
(32768). Later, when sb_bread() attempts I/O with this oversized block
size, it triggers a kernel BUG in folio_set_bh():&lt;/p&gt;
&lt;p&gt;kernel BUG at fs/buffer.c:1582!
    BUG_ON(size &amp;gt; PAGE_SIZE);&lt;/p&gt;
&lt;p&gt;Fix by checking the return value of sb_set_blocksize() and failing the
mount with -EINVAL if it returns 0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-23238</guid>
    </item>
  </channel>
</rss>
