<?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://cve.radiocsirt.org</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>Wed, 07 Oct 2026 17:25:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50864 — nilfs2: fix shift-out-of-bounds due to too large exponent of block size</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-50864</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;nilfs2: fix shift-out-of-bounds due to too large exponent of block size&lt;/p&gt;
&lt;p&gt;If field s_log_block_size of superblock data is corrupted and too large,
init_nilfs() and load_nilfs() still can trigger a shift-out-of-bounds
warning followed by a kernel panic (if panic_on_warn is set):&lt;/p&gt;
&lt;p&gt;shift exponent 38973 is too large for 32-bit type &amp;#39;int&amp;#39;
 Call Trace:
  &amp;lt;TASK&amp;gt;
  dump_stack_lvl+0xcd/0x134
  ubsan_epilogue+0xb/0x50
  __ubsan_handle_shift_out_of_bounds.cold.12+0x17b/0x1f5
  init_nilfs.cold.11+0x18/0x1d [nilfs2]
  nilfs_mount+0x9b5/0x12b0 [nilfs2]
  ...&lt;/p&gt;
&lt;p&gt;This fixes the issue by adding and using a new helper function for getting
block size with sanity check.&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;nilfs2: fix shift-out-of-bounds due to too large exponent of block size&lt;/p&gt;
&lt;p&gt;If field s_log_block_size of superblock data is corrupted and too large,
init_nilfs() and load_nilfs() still can trigger a shift-out-of-bounds
warning followed by a kernel panic (if panic_on_warn is set):&lt;/p&gt;
&lt;p&gt;shift exponent 38973 is too large for 32-bit type &amp;#39;int&amp;#39;
 Call Trace:
  &amp;lt;TASK&amp;gt;
  dump_stack_lvl+0xcd/0x134
  ubsan_epilogue+0xb/0x50
  __ubsan_handle_shift_out_of_bounds.cold.12+0x17b/0x1f5
  init_nilfs.cold.11+0x18/0x1d [nilfs2]
  nilfs_mount+0x9b5/0x12b0 [nilfs2]
  ...&lt;/p&gt;
&lt;p&gt;This fixes the issue by adding and using a new helper function for getting
block size with sanity check.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-50864</guid>
    </item>
  </channel>
</rss>
