<?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>Sat, 03 Oct 2026 13:20:45 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-07242</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-07242</link>
      <description>bdu:2025-07242</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-07242</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-49880</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-49880</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-49880</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0152 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</link>
      <description>certfr-2025-avi-0152</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0152</guid>
    </item>
    <item>
      <title>EUVD-2026-313384</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313384</link>
      <description>EUVD-2026-313384</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313384</guid>
    </item>
    <item>
      <title>fkie_cve-2024-49880</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-49880</link>
      <description>&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;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://cve.radiocsirt.org/vuln/fkie_cve-2024-49880</guid>
    </item>
    <item>
      <title>GHSA-9r6q-3r52-hh42</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9r6q-3r52-hh42</link>
      <description>&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;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://cve.radiocsirt.org/vuln/ghsa-9r6q-3r52-hh42</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:14500-1 — kernel-devel-6.11.8-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</link>
      <description>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-6.11.8-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:14500-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-49880</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-49880</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 194 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: fix off by one issue in alloc_flex_gd() Wesley reported an issue: ================================================================== 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 ================================================================== 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. The reproduction of the problem requires the following:  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; Take n=0,flexbg_size=16 as an example:               last:15 |o---------------|--------------n-| o_group:0    resize to      n_group:30 The corresponding reproducer is: 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 Delete the problematic plus 1 to fix the issue, and add a WARN_ON_ONCE() to pre…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 194 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: fix off by one issue in alloc_flex_gd() Wesley reported an issue: ================================================================== 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 ================================================================== 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. The reproduction of the problem requires the following:  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; Take n=0,flexbg_size=16 as an example:               last:15 |o---------------|--------------n-| o_group:0    resize to      n_group:30 The corresponding reproducer is: 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 Delete the problematic plus 1 to fix the issue, and add a WARN_ON_ONCE() to pre…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-49880</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-3251 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere, nicht näher bekannte Auswirkungen zu erzielen..&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-3251</guid>
    </item>
  </channel>
</rss>
