<?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>Thu, 08 Oct 2026 11:01:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-37858 — fs/jfs: Prevent integer overflow in AG size calculation</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-37858</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;fs/jfs: Prevent integer overflow in AG size calculation&lt;/p&gt;
&lt;p&gt;The JFS filesystem calculates allocation group (AG) size using 1 &amp;lt;&amp;lt;
l2agsize in dbExtendFS(). When l2agsize exceeds 31 (possible with &amp;gt;2TB
aggregates on 32-bit systems), this 32-bit shift operation causes undefined
behavior and improper AG sizing.&lt;/p&gt;
&lt;p&gt;On 32-bit architectures:
- Left-shifting 1 by 32+ bits results in 0 due to integer overflow
- This creates invalid AG sizes (0 or garbage values) in
sbi-&amp;gt;bmap-&amp;gt;db_agsize
- Subsequent block allocations would reference invalid AG structures
- Could lead to:
  - Filesystem corruption during extend operations
  - Kernel crashes due to invalid memory accesses
  - Security vulnerabilities via malformed on-disk structures&lt;/p&gt;
&lt;p&gt;Fix by casting to s64 before shifting:
bmp-&amp;gt;db_agsize = (s64)1 &amp;lt;&amp;lt; l2agsize;&lt;/p&gt;
&lt;p&gt;This ensures 64-bit arithmetic even on 32-bit architectures. The cast
matches the data type of db_agsize (s64) and follows similar patterns in
JFS block calculation code.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with SVACE.&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;fs/jfs: Prevent integer overflow in AG size calculation&lt;/p&gt;
&lt;p&gt;The JFS filesystem calculates allocation group (AG) size using 1 &amp;lt;&amp;lt;
l2agsize in dbExtendFS(). When l2agsize exceeds 31 (possible with &amp;gt;2TB
aggregates on 32-bit systems), this 32-bit shift operation causes undefined
behavior and improper AG sizing.&lt;/p&gt;
&lt;p&gt;On 32-bit architectures:
- Left-shifting 1 by 32+ bits results in 0 due to integer overflow
- This creates invalid AG sizes (0 or garbage values) in
sbi-&amp;gt;bmap-&amp;gt;db_agsize
- Subsequent block allocations would reference invalid AG structures
- Could lead to:
  - Filesystem corruption during extend operations
  - Kernel crashes due to invalid memory accesses
  - Security vulnerabilities via malformed on-disk structures&lt;/p&gt;
&lt;p&gt;Fix by casting to s64 before shifting:
bmp-&amp;gt;db_agsize = (s64)1 &amp;lt;&amp;lt; l2agsize;&lt;/p&gt;
&lt;p&gt;This ensures 64-bit arithmetic even on 32-bit architectures. The cast
matches the data type of db_agsize (s64) and follows similar patterns in
JFS block calculation code.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with SVACE.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-37858</guid>
    </item>
  </channel>
</rss>
