<?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>Fri, 02 Oct 2026 22:39:41 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-01715</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-01715</link>
      <description>bdu:2025-01715</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-01715</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-43859</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-43859</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2024-43859</guid>
    </item>
    <item>
      <title>certfr-2024-avi-0837 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2024-avi-0837</link>
      <description>certfr-2024-avi-0837</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2024-avi-0837</guid>
    </item>
    <item>
      <title>EUVD-2026-313143</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-313143</link>
      <description>EUVD-2026-313143</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-313143</guid>
    </item>
    <item>
      <title>fkie_cve-2024-43859</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-43859</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to truncate preallocated blocks in f2fs_file_open()&lt;/p&gt;
&lt;p&gt;chenyuwen reports a f2fs bug as below:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0000000000000011
 fscrypt_set_bio_crypt_ctx+0x78/0x1e8
 f2fs_grab_read_bio+0x78/0x208
 f2fs_submit_page_read+0x44/0x154
 f2fs_get_read_data_page+0x288/0x5f4
 f2fs_get_lock_data_page+0x60/0x190
 truncate_partial_data_page+0x108/0x4fc
 f2fs_do_truncate_blocks+0x344/0x5f0
 f2fs_truncate_blocks+0x6c/0x134
 f2fs_truncate+0xd8/0x200
 f2fs_iget+0x20c/0x5ac
 do_garbage_collect+0x5d0/0xf6c
 f2fs_gc+0x22c/0x6a4
 f2fs_disable_checkpoint+0xc8/0x310
 f2fs_fill_super+0x14bc/0x1764
 mount_bdev+0x1b4/0x21c
 f2fs_mount+0x20/0x30
 legacy_get_tree+0x50/0xbc
 vfs_get_tree+0x5c/0x1b0
 do_new_mount+0x298/0x4cc
 path_mount+0x33c/0x5fc
 __arm64_sys_mount+0xcc/0x15c
 invoke_syscall+0x60/0x150
 el0_svc_common+0xb8/0xf8
 do_el0_svc+0x28/0xa0
 el0_svc+0x24/0x84
 el0t_64_sync_handler+0x88/0xec&lt;/p&gt;
&lt;p&gt;It is because inode.i_crypt_info is not initialized during below path:
- mount
 - f2fs_fill_super
  - f2fs_disable_checkpoint
   - f2fs_gc
    - f2fs_iget
     - f2fs_truncate&lt;/p&gt;
&lt;p&gt;So, let&amp;#39;s relocate truncation of preallocated blocks to f2fs_file_open(),
after fscrypt_file_open().&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;f2fs: fix to truncate preallocated blocks in f2fs_file_open()&lt;/p&gt;
&lt;p&gt;chenyuwen reports a f2fs bug as below:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0000000000000011
 fscrypt_set_bio_crypt_ctx+0x78/0x1e8
 f2fs_grab_read_bio+0x78/0x208
 f2fs_submit_page_read+0x44/0x154
 f2fs_get_read_data_page+0x288/0x5f4
 f2fs_get_lock_data_page+0x60/0x190
 truncate_partial_data_page+0x108/0x4fc
 f2fs_do_truncate_blocks+0x344/0x5f0
 f2fs_truncate_blocks+0x6c/0x134
 f2fs_truncate+0xd8/0x200
 f2fs_iget+0x20c/0x5ac
 do_garbage_collect+0x5d0/0xf6c
 f2fs_gc+0x22c/0x6a4
 f2fs_disable_checkpoint+0xc8/0x310
 f2fs_fill_super+0x14bc/0x1764
 mount_bdev+0x1b4/0x21c
 f2fs_mount+0x20/0x30
 legacy_get_tree+0x50/0xbc
 vfs_get_tree+0x5c/0x1b0
 do_new_mount+0x298/0x4cc
 path_mount+0x33c/0x5fc
 __arm64_sys_mount+0xcc/0x15c
 invoke_syscall+0x60/0x150
 el0_svc_common+0xb8/0xf8
 do_el0_svc+0x28/0xa0
 el0_svc+0x24/0x84
 el0t_64_sync_handler+0x88/0xec&lt;/p&gt;
&lt;p&gt;It is because inode.i_crypt_info is not initialized during below path:
- mount
 - f2fs_fill_super
  - f2fs_disable_checkpoint
   - f2fs_gc
    - f2fs_iget
     - f2fs_truncate&lt;/p&gt;
&lt;p&gt;So, let&amp;#39;s relocate truncation of preallocated blocks to f2fs_file_open(),
after fscrypt_file_open().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-43859</guid>
    </item>
    <item>
      <title>GHSA-xw4r-xjqg-mh9q</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xw4r-xjqg-mh9q</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix to truncate preallocated blocks in f2fs_file_open()&lt;/p&gt;
&lt;p&gt;chenyuwen reports a f2fs bug as below:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0000000000000011
 fscrypt_set_bio_crypt_ctx+0x78/0x1e8
 f2fs_grab_read_bio+0x78/0x208
 f2fs_submit_page_read+0x44/0x154
 f2fs_get_read_data_page+0x288/0x5f4
 f2fs_get_lock_data_page+0x60/0x190
 truncate_partial_data_page+0x108/0x4fc
 f2fs_do_truncate_blocks+0x344/0x5f0
 f2fs_truncate_blocks+0x6c/0x134
 f2fs_truncate+0xd8/0x200
 f2fs_iget+0x20c/0x5ac
 do_garbage_collect+0x5d0/0xf6c
 f2fs_gc+0x22c/0x6a4
 f2fs_disable_checkpoint+0xc8/0x310
 f2fs_fill_super+0x14bc/0x1764
 mount_bdev+0x1b4/0x21c
 f2fs_mount+0x20/0x30
 legacy_get_tree+0x50/0xbc
 vfs_get_tree+0x5c/0x1b0
 do_new_mount+0x298/0x4cc
 path_mount+0x33c/0x5fc
 __arm64_sys_mount+0xcc/0x15c
 invoke_syscall+0x60/0x150
 el0_svc_common+0xb8/0xf8
 do_el0_svc+0x28/0xa0
 el0_svc+0x24/0x84
 el0t_64_sync_handler+0x88/0xec&lt;/p&gt;
&lt;p&gt;It is because inode.i_crypt_info is not initialized during below path:
- mount
 - f2fs_fill_super
  - f2fs_disable_checkpoint
   - f2fs_gc
    - f2fs_iget
     - f2fs_truncate&lt;/p&gt;
&lt;p&gt;So, let&amp;#39;s relocate truncation of preallocated blocks to f2fs_file_open(),
after fscrypt_file_open().&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;f2fs: fix to truncate preallocated blocks in f2fs_file_open()&lt;/p&gt;
&lt;p&gt;chenyuwen reports a f2fs bug as below:&lt;/p&gt;
&lt;p&gt;Unable to handle kernel NULL pointer dereference at virtual address 0000000000000011
 fscrypt_set_bio_crypt_ctx+0x78/0x1e8
 f2fs_grab_read_bio+0x78/0x208
 f2fs_submit_page_read+0x44/0x154
 f2fs_get_read_data_page+0x288/0x5f4
 f2fs_get_lock_data_page+0x60/0x190
 truncate_partial_data_page+0x108/0x4fc
 f2fs_do_truncate_blocks+0x344/0x5f0
 f2fs_truncate_blocks+0x6c/0x134
 f2fs_truncate+0xd8/0x200
 f2fs_iget+0x20c/0x5ac
 do_garbage_collect+0x5d0/0xf6c
 f2fs_gc+0x22c/0x6a4
 f2fs_disable_checkpoint+0xc8/0x310
 f2fs_fill_super+0x14bc/0x1764
 mount_bdev+0x1b4/0x21c
 f2fs_mount+0x20/0x30
 legacy_get_tree+0x50/0xbc
 vfs_get_tree+0x5c/0x1b0
 do_new_mount+0x298/0x4cc
 path_mount+0x33c/0x5fc
 __arm64_sys_mount+0xcc/0x15c
 invoke_syscall+0x60/0x150
 el0_svc_common+0xb8/0xf8
 do_el0_svc+0x28/0xa0
 el0_svc+0x24/0x84
 el0t_64_sync_handler+0x88/0xec&lt;/p&gt;
&lt;p&gt;It is because inode.i_crypt_info is not initialized during below path:
- mount
 - f2fs_fill_super
  - f2fs_disable_checkpoint
   - f2fs_gc
    - f2fs_iget
     - f2fs_truncate&lt;/p&gt;
&lt;p&gt;So, let&amp;#39;s relocate truncation of preallocated blocks to f2fs_file_open(),
after fscrypt_file_open().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xw4r-xjqg-mh9q</guid>
    </item>
    <item>
      <title>msrc_CVE-2024-43859 — f2fs: fix to truncate preallocated blocks in f2fs_file_open()</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2024-43859</link>
      <description>msrc_CVE-2024-43859</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2024-43859</guid>
    </item>
    <item>
      <title>NCSC-2026-0074 — Kwetsbaarheden verholpen in Google Android en Samsung Mobile</title>
      <link>https://cve.radiocsirt.org/vuln/ncsc-2026-0074</link>
      <description>NCSC-2026-0074</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ncsc-2026-0074</guid>
    </item>
    <item>
      <title>OESA-2024-2124 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2024-2124</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
bna: ensure the copied buf is NUL terminated&#13;
&#13;
Currently, we allocate a nbytes-sized kernel buffer and copy nbytes from
userspace to that buffer. Later, we use sscanf on this buffer but we don&amp;amp;apos;t
ensure that the string is terminated inside the buffer, this can lead to
OOB read when using sscanf. Fix this issue by using memdup_user_nul
instead of memdup_user.(CVE-2024-36934)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
nilfs2: fix potential kernel bug due to lack of writeback flag waiting&#13;
&#13;
Destructive writes to a block device on which nilfs2 is mounted can cause
a kernel bug in the folio/page writeback start routine or writeback end
routine (__folio_start_writeback in the log below):&#13;
&#13;
 kernel BUG at mm/page-writeback.c:3070!
 Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
 ...
 RIP: 0010:__folio_start_writeback+0xbaa/0x10e0
 Code: 25 ff 0f 00 00 0f 84 18 01 00 00 e8 40 ca c6 ff e9 17 f6 ff ff
  e8 36 ca c6 ff 4c 89 f7 48 c7 c6 80 c0 12 84 e8 e7 b3 0f 00 90 &amp;amp;lt;0f&amp;amp;gt;
  0b e8 1f ca c6 ff 4c 89 f7 48 c7 c6 a0 c6 12 84 e8 d0 b3 0f 00
 ...
 Call Trace:
  &amp;amp;lt;TASK&amp;amp;gt;
  nilfs_segctor_do_construct+0x4654/0x69d0 [nilfs2]
  nilfs_segctor_construct+0x181/0x6b0 [nilfs2]
  nilfs_segctor_thread+0x548/0x11c0 [nilfs2]
  kthread+0x2f0/0x390
  ret_from_fork+0x4b/0x80
  ret_from_fork_asm+0x1a/0x30
  &amp;amp;lt;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
bna: ensure the copied buf is NUL terminated&#13;
&#13;
Currently, we allocate a nbytes-sized kernel buffer and copy nbytes from
userspace to that buffer. Later, we use sscanf on this buffer but we don&amp;amp;apos;t
ensure that the string is terminated inside the buffer, this can lead to
OOB read when using sscanf. Fix this issue by using memdup_user_nul
instead of memdup_user.(CVE-2024-36934)&#13;
&#13;
In the Linux kernel, the following vulnerability has been resolved:&#13;
&#13;
nilfs2: fix potential kernel bug due to lack of writeback flag waiting&#13;
&#13;
Destructive writes to a block device on which nilfs2 is mounted can cause
a kernel bug in the folio/page writeback start routine or writeback end
routine (__folio_start_writeback in the log below):&#13;
&#13;
 kernel BUG at mm/page-writeback.c:3070!
 Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
 ...
 RIP: 0010:__folio_start_writeback+0xbaa/0x10e0
 Code: 25 ff 0f 00 00 0f 84 18 01 00 00 e8 40 ca c6 ff e9 17 f6 ff ff
  e8 36 ca c6 ff 4c 89 f7 48 c7 c6 80 c0 12 84 e8 e7 b3 0f 00 90 &amp;amp;lt;0f&amp;amp;gt;
  0b e8 1f ca c6 ff 4c 89 f7 48 c7 c6 a0 c6 12 84 e8 d0 b3 0f 00
 ...
 Call Trace:
  &amp;amp;lt;TASK&amp;amp;gt;
  nilfs_segctor_do_construct+0x4654/0x69d0 [nilfs2]
  nilfs_segctor_construct+0x181/0x6b0 [nilfs2]
  nilfs_segctor_thread+0x548/0x11c0 [nilfs2]
  kthread+0x2f0/0x390
  ret_from_fork+0x4b/0x80
  ret_from_fork_asm+0x1a/0x30
  &amp;amp;lt;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2024-2124</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-43859</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-43859</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 89 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to truncate preallocated blocks in f2fs_file_open() chenyuwen reports a f2fs bug as below: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000011  fscrypt_set_bio_crypt_ctx+0x78/0x1e8  f2fs_grab_read_bio+0x78/0x208  f2fs_submit_page_read+0x44/0x154  f2fs_get_read_data_page+0x288/0x5f4  f2fs_get_lock_data_page+0x60/0x190  truncate_partial_data_page+0x108/0x4fc  f2fs_do_truncate_blocks+0x344/0x5f0  f2fs_truncate_blocks+0x6c/0x134  f2fs_truncate+0xd8/0x200  f2fs_iget+0x20c/0x5ac  do_garbage_collect+0x5d0/0xf6c  f2fs_gc+0x22c/0x6a4  f2fs_disable_checkpoint+0xc8/0x310  f2fs_fill_super+0x14bc/0x1764  mount_bdev+0x1b4/0x21c  f2fs_mount+0x20/0x30  legacy_get_tree+0x50/0xbc  vfs_get_tree+0x5c/0x1b0  do_new_mount+0x298/0x4cc  path_mount+0x33c/0x5fc  __arm64_sys_mount+0xcc/0x15c  invoke_syscall+0x60/0x150  el0_svc_common+0xb8/0xf8  do_el0_svc+0x28/0xa0  el0_svc+0x24/0x84  el0t_64_sync_handler+0x88/0xec It is because inode.i_crypt_info is not initialized during below path: - mount  - f2fs_fill_super   - f2fs_disable_checkpoint    - f2fs_gc     - f2fs_iget      - f2fs_truncate So, let&amp;#39;s relocate truncation of preallocated blocks to f2fs_file_open(), after fscrypt_file_open().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 89 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to truncate preallocated blocks in f2fs_file_open() chenyuwen reports a f2fs bug as below: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000011  fscrypt_set_bio_crypt_ctx+0x78/0x1e8  f2fs_grab_read_bio+0x78/0x208  f2fs_submit_page_read+0x44/0x154  f2fs_get_read_data_page+0x288/0x5f4  f2fs_get_lock_data_page+0x60/0x190  truncate_partial_data_page+0x108/0x4fc  f2fs_do_truncate_blocks+0x344/0x5f0  f2fs_truncate_blocks+0x6c/0x134  f2fs_truncate+0xd8/0x200  f2fs_iget+0x20c/0x5ac  do_garbage_collect+0x5d0/0xf6c  f2fs_gc+0x22c/0x6a4  f2fs_disable_checkpoint+0xc8/0x310  f2fs_fill_super+0x14bc/0x1764  mount_bdev+0x1b4/0x21c  f2fs_mount+0x20/0x30  legacy_get_tree+0x50/0xbc  vfs_get_tree+0x5c/0x1b0  do_new_mount+0x298/0x4cc  path_mount+0x33c/0x5fc  __arm64_sys_mount+0xcc/0x15c  invoke_syscall+0x60/0x150  el0_svc_common+0xb8/0xf8  do_el0_svc+0x28/0xa0  el0_svc+0x24/0x84  el0t_64_sync_handler+0x88/0xec It is because inode.i_crypt_info is not initialized during below path: - mount  - f2fs_fill_super   - f2fs_disable_checkpoint    - f2fs_gc     - f2fs_iget      - f2fs_truncate So, let&amp;#39;s relocate truncation of preallocated blocks to f2fs_file_open(), after fscrypt_file_open().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-43859</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1875 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1875</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder unbekannte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder unbekannte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1875</guid>
    </item>
  </channel>
</rss>
