<?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>Sun, 04 Oct 2026 18:19:25 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-09458</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-09458</link>
      <description>bdu:2026-09458</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-09458</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-71067</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-71067</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-2025-71067</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0166 — 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-2026-avi-0166</link>
      <description>certfr-2026-avi-0166</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0166</guid>
    </item>
    <item>
      <title>EUVD-2026-315197</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-315197</link>
      <description>EUVD-2026-315197</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-315197</guid>
    </item>
    <item>
      <title>fkie_cve-2025-71067</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-71067</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ntfs: set dummy blocksize to read boot_block when mounting&lt;/p&gt;
&lt;p&gt;When mounting, sb-&amp;gt;s_blocksize is used to read the boot_block without
being defined or validated. Set a dummy blocksize before attempting to
read the boot_block.&lt;/p&gt;
&lt;p&gt;The issue can be triggered with the following syz reproducer:&lt;/p&gt;
&lt;p&gt;mkdirat(0xffffffffffffff9c, &amp;amp;(0x7f0000000080)=&amp;#39;./file1\x00&amp;#39;, 0x0)
  r4 = openat$nullb(0xffffffffffffff9c, &amp;amp;(0x7f0000000040), 0x121403, 0x0)
  ioctl$FS_IOC_SETFLAGS(r4, 0x40081271, &amp;amp;(0x7f0000000980)=0x4000)
  mount(&amp;amp;(0x7f0000000140)=@nullb, &amp;amp;(0x7f0000000040)=&amp;#39;./cgroup\x00&amp;#39;,
        &amp;amp;(0x7f0000000000)=&amp;#39;ntfs3\x00&amp;#39;, 0x2208004, 0x0)
  syz_clone(0x88200200, 0x0, 0x0, 0x0, 0x0, 0x0)&lt;/p&gt;
&lt;p&gt;Here, the ioctl sets the bdev block size to 16384. During mount,
get_tree_bdev_flags() calls sb_set_blocksize(sb, block_size(bdev)),
but since block_size(bdev) &amp;gt; PAGE_SIZE, sb_set_blocksize() leaves
sb-&amp;gt;s_blocksize at zero.&lt;/p&gt;
&lt;p&gt;Later, ntfs_init_from_boot() attempts to read the boot_block while
sb-&amp;gt;s_blocksize is still zero, which triggers the bug.&lt;/p&gt;
&lt;p&gt;[almaz.alexandrovich@paragon-software.com: changed comment style, added
return value handling]&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;ntfs: set dummy blocksize to read boot_block when mounting&lt;/p&gt;
&lt;p&gt;When mounting, sb-&amp;gt;s_blocksize is used to read the boot_block without
being defined or validated. Set a dummy blocksize before attempting to
read the boot_block.&lt;/p&gt;
&lt;p&gt;The issue can be triggered with the following syz reproducer:&lt;/p&gt;
&lt;p&gt;mkdirat(0xffffffffffffff9c, &amp;amp;(0x7f0000000080)=&amp;#39;./file1\x00&amp;#39;, 0x0)
  r4 = openat$nullb(0xffffffffffffff9c, &amp;amp;(0x7f0000000040), 0x121403, 0x0)
  ioctl$FS_IOC_SETFLAGS(r4, 0x40081271, &amp;amp;(0x7f0000000980)=0x4000)
  mount(&amp;amp;(0x7f0000000140)=@nullb, &amp;amp;(0x7f0000000040)=&amp;#39;./cgroup\x00&amp;#39;,
        &amp;amp;(0x7f0000000000)=&amp;#39;ntfs3\x00&amp;#39;, 0x2208004, 0x0)
  syz_clone(0x88200200, 0x0, 0x0, 0x0, 0x0, 0x0)&lt;/p&gt;
&lt;p&gt;Here, the ioctl sets the bdev block size to 16384. During mount,
get_tree_bdev_flags() calls sb_set_blocksize(sb, block_size(bdev)),
but since block_size(bdev) &amp;gt; PAGE_SIZE, sb_set_blocksize() leaves
sb-&amp;gt;s_blocksize at zero.&lt;/p&gt;
&lt;p&gt;Later, ntfs_init_from_boot() attempts to read the boot_block while
sb-&amp;gt;s_blocksize is still zero, which triggers the bug.&lt;/p&gt;
&lt;p&gt;[almaz.alexandrovich@paragon-software.com: changed comment style, added
return value handling]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-71067</guid>
    </item>
    <item>
      <title>GHSA-wq7w-gfpq-89g4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wq7w-gfpq-89g4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ntfs: set dummy blocksize to read boot_block when mounting&lt;/p&gt;
&lt;p&gt;When mounting, sb-&amp;gt;s_blocksize is used to read the boot_block without
being defined or validated. Set a dummy blocksize before attempting to
read the boot_block.&lt;/p&gt;
&lt;p&gt;The issue can be triggered with the following syz reproducer:&lt;/p&gt;
&lt;p&gt;mkdirat(0xffffffffffffff9c, &amp;amp;(0x7f0000000080)=&amp;#39;./file1\x00&amp;#39;, 0x0)
  r4 = openat$nullb(0xffffffffffffff9c, &amp;amp;(0x7f0000000040), 0x121403, 0x0)
  ioctl$FS_IOC_SETFLAGS(r4, 0x40081271, &amp;amp;(0x7f0000000980)=0x4000)
  mount(&amp;amp;(0x7f0000000140)=@nullb, &amp;amp;(0x7f0000000040)=&amp;#39;./cgroup\x00&amp;#39;,
        &amp;amp;(0x7f0000000000)=&amp;#39;ntfs3\x00&amp;#39;, 0x2208004, 0x0)
  syz_clone(0x88200200, 0x0, 0x0, 0x0, 0x0, 0x0)&lt;/p&gt;
&lt;p&gt;Here, the ioctl sets the bdev block size to 16384. During mount,
get_tree_bdev_flags() calls sb_set_blocksize(sb, block_size(bdev)),
but since block_size(bdev) &amp;gt; PAGE_SIZE, sb_set_blocksize() leaves
sb-&amp;gt;s_blocksize at zero.&lt;/p&gt;
&lt;p&gt;Later, ntfs_init_from_boot() attempts to read the boot_block while
sb-&amp;gt;s_blocksize is still zero, which triggers the bug.&lt;/p&gt;
&lt;p&gt;[almaz.alexandrovich@paragon-software.com: changed comment style, added
return value handling]&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;ntfs: set dummy blocksize to read boot_block when mounting&lt;/p&gt;
&lt;p&gt;When mounting, sb-&amp;gt;s_blocksize is used to read the boot_block without
being defined or validated. Set a dummy blocksize before attempting to
read the boot_block.&lt;/p&gt;
&lt;p&gt;The issue can be triggered with the following syz reproducer:&lt;/p&gt;
&lt;p&gt;mkdirat(0xffffffffffffff9c, &amp;amp;(0x7f0000000080)=&amp;#39;./file1\x00&amp;#39;, 0x0)
  r4 = openat$nullb(0xffffffffffffff9c, &amp;amp;(0x7f0000000040), 0x121403, 0x0)
  ioctl$FS_IOC_SETFLAGS(r4, 0x40081271, &amp;amp;(0x7f0000000980)=0x4000)
  mount(&amp;amp;(0x7f0000000140)=@nullb, &amp;amp;(0x7f0000000040)=&amp;#39;./cgroup\x00&amp;#39;,
        &amp;amp;(0x7f0000000000)=&amp;#39;ntfs3\x00&amp;#39;, 0x2208004, 0x0)
  syz_clone(0x88200200, 0x0, 0x0, 0x0, 0x0, 0x0)&lt;/p&gt;
&lt;p&gt;Here, the ioctl sets the bdev block size to 16384. During mount,
get_tree_bdev_flags() calls sb_set_blocksize(sb, block_size(bdev)),
but since block_size(bdev) &amp;gt; PAGE_SIZE, sb_set_blocksize() leaves
sb-&amp;gt;s_blocksize at zero.&lt;/p&gt;
&lt;p&gt;Later, ntfs_init_from_boot() attempts to read the boot_block while
sb-&amp;gt;s_blocksize is still zero, which triggers the bug.&lt;/p&gt;
&lt;p&gt;[almaz.alexandrovich@paragon-software.com: changed comment style, added
return value handling]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wq7w-gfpq-89g4</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-71067 — ntfs: set dummy blocksize to read boot_block when mounting</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-71067</link>
      <description>msrc_CVE-2025-71067</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-71067</guid>
    </item>
    <item>
      <title>OESA-2026-2580 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-2580</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iomap: Fix possible overflow condition in iomap_write_delalloc_scan&lt;/p&gt;
&lt;p&gt;folio_next_index() returns an unsigned long value which left shifted
by PAGE_SHIFT could possibly cause an overflow on 32-bit system. Instead
use folio_pos(folio) + folio_size(folio), which does this correctly.(CVE-2023-54285)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bcache: fix NULL pointer in cache_set_flush()&lt;/p&gt;
&lt;p&gt;1. LINE#1794 - LINE#1887 is some codes about function of
   bch_cache_set_alloc().
2. LINE#2078 - LINE#2142 is some codes about function of
   register_cache_set().
3. register_cache_set() will call bch_cache_set_alloc() in LINE#2098.&lt;/p&gt;
&lt;p&gt;1794 struct cache_set *bch_cache_set_alloc(struct cache_sb *sb)
 1795 {
 ...
 1860         if (!(c-&amp;amp;gt;devices = kcalloc(c-&amp;amp;gt;nr_uuids, sizeof(void *), GFP_KERNEL)) ||
 1861             mempool_init_slab_pool(&amp;amp;amp;c-&amp;amp;gt;search, 32, bch_search_cache) ||
 1862             mempool_init_kmalloc_pool(&amp;amp;amp;c-&amp;amp;gt;bio_meta, 2,
 1863                                 sizeof(struct bbio) + sizeof(struct bio_vec) *
 1864                                 bucket_pages(c)) ||
 1865             mempool_init_kmalloc_pool(&amp;amp;amp;c-&amp;amp;gt;fill_iter, 1, iter_size) ||
 1866             bioset_init(&amp;amp;amp;c-&amp;amp;gt;bio_split, 4, offsetof(struct bbio, bio),
 1867                         BIOSET_NEED_BVECS|BIOSET_NEED_RESCUER) ||
 18…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;iomap: Fix possible overflow condition in iomap_write_delalloc_scan&lt;/p&gt;
&lt;p&gt;folio_next_index() returns an unsigned long value which left shifted
by PAGE_SHIFT could possibly cause an overflow on 32-bit system. Instead
use folio_pos(folio) + folio_size(folio), which does this correctly.(CVE-2023-54285)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bcache: fix NULL pointer in cache_set_flush()&lt;/p&gt;
&lt;p&gt;1. LINE#1794 - LINE#1887 is some codes about function of
   bch_cache_set_alloc().
2. LINE#2078 - LINE#2142 is some codes about function of
   register_cache_set().
3. register_cache_set() will call bch_cache_set_alloc() in LINE#2098.&lt;/p&gt;
&lt;p&gt;1794 struct cache_set *bch_cache_set_alloc(struct cache_sb *sb)
 1795 {
 ...
 1860         if (!(c-&amp;amp;gt;devices = kcalloc(c-&amp;amp;gt;nr_uuids, sizeof(void *), GFP_KERNEL)) ||
 1861             mempool_init_slab_pool(&amp;amp;amp;c-&amp;amp;gt;search, 32, bch_search_cache) ||
 1862             mempool_init_kmalloc_pool(&amp;amp;amp;c-&amp;amp;gt;bio_meta, 2,
 1863                                 sizeof(struct bbio) + sizeof(struct bio_vec) *
 1864                                 bucket_pages(c)) ||
 1865             mempool_init_kmalloc_pool(&amp;amp;amp;c-&amp;amp;gt;fill_iter, 1, iter_size) ||
 1866             bioset_init(&amp;amp;amp;c-&amp;amp;gt;bio_split, 4, offsetof(struct bbio, bio),
 1867                         BIOSET_NEED_BVECS|BIOSET_NEED_RESCUER) ||
 18…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-2580</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-71067</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71067</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 232 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ntfs: set dummy blocksize to read boot_block when mounting When mounting, sb-&amp;gt;s_blocksize is used to read the boot_block without being defined or validated. Set a dummy blocksize before attempting to read the boot_block. The issue can be triggered with the following syz reproducer:   mkdirat(0xffffffffffffff9c, &amp;amp;(0x7f0000000080)=&amp;#39;./file1\x00&amp;#39;, 0x0)   r4 = openat$nullb(0xffffffffffffff9c, &amp;amp;(0x7f0000000040), 0x121403, 0x0)   ioctl$FS_IOC_SETFLAGS(r4, 0x40081271, &amp;amp;(0x7f0000000980)=0x4000)   mount(&amp;amp;(0x7f0000000140)=@nullb, &amp;amp;(0x7f0000000040)=&amp;#39;./cgroup\x00&amp;#39;,         &amp;amp;(0x7f0000000000)=&amp;#39;ntfs3\x00&amp;#39;, 0x2208004, 0x0)   syz_clone(0x88200200, 0x0, 0x0, 0x0, 0x0, 0x0) Here, the ioctl sets the bdev block size to 16384. During mount, get_tree_bdev_flags() calls sb_set_blocksize(sb, block_size(bdev)), but since block_size(bdev) &amp;gt; PAGE_SIZE, sb_set_blocksize() leaves sb-&amp;gt;s_blocksize at zero. Later, ntfs_init_from_boot() attempts to read the boot_block while sb-&amp;gt;s_blocksize is still zero, which triggers the bug. [almaz.alexandrovich@paragon-software.com: changed comment style, added return value handling]&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 232 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ntfs: set dummy blocksize to read boot_block when mounting When mounting, sb-&amp;gt;s_blocksize is used to read the boot_block without being defined or validated. Set a dummy blocksize before attempting to read the boot_block. The issue can be triggered with the following syz reproducer:   mkdirat(0xffffffffffffff9c, &amp;amp;(0x7f0000000080)=&amp;#39;./file1\x00&amp;#39;, 0x0)   r4 = openat$nullb(0xffffffffffffff9c, &amp;amp;(0x7f0000000040), 0x121403, 0x0)   ioctl$FS_IOC_SETFLAGS(r4, 0x40081271, &amp;amp;(0x7f0000000980)=0x4000)   mount(&amp;amp;(0x7f0000000140)=@nullb, &amp;amp;(0x7f0000000040)=&amp;#39;./cgroup\x00&amp;#39;,         &amp;amp;(0x7f0000000000)=&amp;#39;ntfs3\x00&amp;#39;, 0x2208004, 0x0)   syz_clone(0x88200200, 0x0, 0x0, 0x0, 0x0, 0x0) Here, the ioctl sets the bdev block size to 16384. During mount, get_tree_bdev_flags() calls sb_set_blocksize(sb, block_size(bdev)), but since block_size(bdev) &amp;gt; PAGE_SIZE, sb_set_blocksize() leaves sb-&amp;gt;s_blocksize at zero. Later, ntfs_init_from_boot() attempts to read the boot_block while sb-&amp;gt;s_blocksize is still zero, which triggers the bug. [almaz.alexandrovich@paragon-software.com: changed comment style, added return value handling]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-71067</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0086 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0086</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0086</guid>
    </item>
  </channel>
</rss>
