<?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>Thu, 01 Oct 2026 01:16:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-49880 — ext4: fix off by one issue in alloc_flex_gd()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-49880</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;ext4: fix off by one issue in alloc_flex_gd()&lt;/p&gt;
&lt;p&gt;Wesley reported an issue:&lt;/p&gt;
&lt;p&gt;==================================================================
EXT4-fs (dm-5): resizing filesystem from 7168 to 786432 blocks
------------[ cut here ]------------
kernel BUG at fs/ext4/resize.c:324!
CPU: 9 UID: 0 PID: 3576 Comm: resize2fs Not tainted 6.11.0+ #27
RIP: 0010:ext4_resize_fs+0x1212/0x12d0
Call Trace:
 __ext4_ioctl+0x4e0/0x1800
 ext4_ioctl+0x12/0x20
 __x64_sys_ioctl+0x99/0xd0
 x64_sys_call+0x1206/0x20d0
 do_syscall_64+0x72/0x110
 entry_SYSCALL_64_after_hwframe+0x76/0x7e
==================================================================&lt;/p&gt;
&lt;p&gt;While reviewing the patch, Honza found that when adjusting resize_bg in
alloc_flex_gd(), it was possible for flex_gd-&amp;gt;resize_bg to be bigger than
flexbg_size.&lt;/p&gt;
&lt;p&gt;The reproduction of the problem requires the following:&lt;/p&gt;
&lt;p&gt;o_group = flexbg_size * 2 * n;
 o_size = (o_group + 1) * group_size;
 n_group: [o_group + flexbg_size, o_group + flexbg_size * 2)
 o_size = (n_group + 1) * group_size;&lt;/p&gt;
&lt;p&gt;Take n=0,flexbg_size=16 as an example:&lt;/p&gt;
&lt;p&gt;last:15
|o---------------|--------------n-|
o_group:0    resize to      n_group:30&lt;/p&gt;
&lt;p&gt;The corresponding reproducer is:&lt;/p&gt;
&lt;p&gt;img=test.img
rm -f $img
truncate -s 600M $img
mkfs.ext4 -F $img -b 1024 -G 16 8M
dev=`losetup -f --show $img`
mkdir -p /tmp/test
mount $dev /tmp/test
resize2fs $dev 248M&lt;/p&gt;
&lt;p&gt;Delete the problematic plus 1 to fix the issue, and add a WARN_ON_ON…&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;ext4: fix off by one issue in alloc_flex_gd()&lt;/p&gt;
&lt;p&gt;Wesley reported an issue:&lt;/p&gt;
&lt;p&gt;==================================================================
EXT4-fs (dm-5): resizing filesystem from 7168 to 786432 blocks
------------[ cut here ]------------
kernel BUG at fs/ext4/resize.c:324!
CPU: 9 UID: 0 PID: 3576 Comm: resize2fs Not tainted 6.11.0+ #27
RIP: 0010:ext4_resize_fs+0x1212/0x12d0
Call Trace:
 __ext4_ioctl+0x4e0/0x1800
 ext4_ioctl+0x12/0x20
 __x64_sys_ioctl+0x99/0xd0
 x64_sys_call+0x1206/0x20d0
 do_syscall_64+0x72/0x110
 entry_SYSCALL_64_after_hwframe+0x76/0x7e
==================================================================&lt;/p&gt;
&lt;p&gt;While reviewing the patch, Honza found that when adjusting resize_bg in
alloc_flex_gd(), it was possible for flex_gd-&amp;gt;resize_bg to be bigger than
flexbg_size.&lt;/p&gt;
&lt;p&gt;The reproduction of the problem requires the following:&lt;/p&gt;
&lt;p&gt;o_group = flexbg_size * 2 * n;
 o_size = (o_group + 1) * group_size;
 n_group: [o_group + flexbg_size, o_group + flexbg_size * 2)
 o_size = (n_group + 1) * group_size;&lt;/p&gt;
&lt;p&gt;Take n=0,flexbg_size=16 as an example:&lt;/p&gt;
&lt;p&gt;last:15
|o---------------|--------------n-|
o_group:0    resize to      n_group:30&lt;/p&gt;
&lt;p&gt;The corresponding reproducer is:&lt;/p&gt;
&lt;p&gt;img=test.img
rm -f $img
truncate -s 600M $img
mkfs.ext4 -F $img -b 1024 -G 16 8M
dev=`losetup -f --show $img`
mkdir -p /tmp/test
mount $dev /tmp/test
resize2fs $dev 248M&lt;/p&gt;
&lt;p&gt;Delete the problematic plus 1 to fix the issue, and add a WARN_ON_ON…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-49880</guid>
    </item>
  </channel>
</rss>
