<?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>Wed, 07 Oct 2026 12:35:12 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04158</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-04158</link>
      <description>bdu:2026-04158</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-04158</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-23267</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-23267</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-2026-23267</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0341 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoqu…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0341</link>
      <description>certfr-2026-avi-0341</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0341</guid>
    </item>
    <item>
      <title>EUVD-2026-315440</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-315440</link>
      <description>EUVD-2026-315440</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-315440</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23267</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23267</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix IS_CHECKPOINTED flag inconsistency issue caused by concurrent atomic commit and checkpoint writes&lt;/p&gt;
&lt;p&gt;During SPO tests, when mounting F2FS, an -EINVAL error was returned from
f2fs_recover_inode_page. The issue occurred under the following scenario&lt;/p&gt;
&lt;p&gt;Thread A                                     Thread B
f2fs_ioc_commit_atomic_write
 - f2fs_do_sync_file // atomic = true
  - f2fs_fsync_node_pages
    : last_folio = inode folio
    : schedule before folio_lock(last_folio) f2fs_write_checkpoint
                                              - block_operations// writeback last_folio
                                              - schedule before f2fs_flush_nat_entries
    : set_fsync_mark(last_folio, 1)
    : set_dentry_mark(last_folio, 1)
    : folio_mark_dirty(last_folio)
    - __write_node_folio(last_folio)
      : f2fs_down_read(&amp;amp;sbi-&amp;gt;node_write)//block
                                              - f2fs_flush_nat_entries
                                                : {struct nat_entry}-&amp;gt;flag |= BIT(IS_CHECKPOINTED)
                                              - unblock_operations
                                                : f2fs_up_write(&amp;amp;sbi-&amp;gt;node_write)
                                             f2fs_write_checkpoint//return
      : f2fs_do_write_node_page()
f2fs_ioc_commit_atomic_write//return
                                             SPO&lt;/p&gt;
&lt;p&gt;Thread A calls f2fs_need_dentry_mark(sbi, ino)…&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 IS_CHECKPOINTED flag inconsistency issue caused by concurrent atomic commit and checkpoint writes&lt;/p&gt;
&lt;p&gt;During SPO tests, when mounting F2FS, an -EINVAL error was returned from
f2fs_recover_inode_page. The issue occurred under the following scenario&lt;/p&gt;
&lt;p&gt;Thread A                                     Thread B
f2fs_ioc_commit_atomic_write
 - f2fs_do_sync_file // atomic = true
  - f2fs_fsync_node_pages
    : last_folio = inode folio
    : schedule before folio_lock(last_folio) f2fs_write_checkpoint
                                              - block_operations// writeback last_folio
                                              - schedule before f2fs_flush_nat_entries
    : set_fsync_mark(last_folio, 1)
    : set_dentry_mark(last_folio, 1)
    : folio_mark_dirty(last_folio)
    - __write_node_folio(last_folio)
      : f2fs_down_read(&amp;amp;sbi-&amp;gt;node_write)//block
                                              - f2fs_flush_nat_entries
                                                : {struct nat_entry}-&amp;gt;flag |= BIT(IS_CHECKPOINTED)
                                              - unblock_operations
                                                : f2fs_up_write(&amp;amp;sbi-&amp;gt;node_write)
                                             f2fs_write_checkpoint//return
      : f2fs_do_write_node_page()
f2fs_ioc_commit_atomic_write//return
                                             SPO&lt;/p&gt;
&lt;p&gt;Thread A calls f2fs_need_dentry_mark(sbi, ino)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-23267</guid>
    </item>
    <item>
      <title>GHSA-9m9w-6gjg-9m6r</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9m9w-6gjg-9m6r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;f2fs: fix IS_CHECKPOINTED flag inconsistency issue caused by concurrent atomic commit and checkpoint writes&lt;/p&gt;
&lt;p&gt;During SPO tests, when mounting F2FS, an -EINVAL error was returned from
f2fs_recover_inode_page. The issue occurred under the following scenario&lt;/p&gt;
&lt;p&gt;Thread A                                     Thread B
f2fs_ioc_commit_atomic_write
 - f2fs_do_sync_file // atomic = true
  - f2fs_fsync_node_pages
    : last_folio = inode folio
    : schedule before folio_lock(last_folio) f2fs_write_checkpoint
                                              - block_operations// writeback last_folio
                                              - schedule before f2fs_flush_nat_entries
    : set_fsync_mark(last_folio, 1)
    : set_dentry_mark(last_folio, 1)
    : folio_mark_dirty(last_folio)
    - __write_node_folio(last_folio)
      : f2fs_down_read(&amp;amp;sbi-&amp;gt;node_write)//block
                                              - f2fs_flush_nat_entries
                                                : {struct nat_entry}-&amp;gt;flag |= BIT(IS_CHECKPOINTED)
                                              - unblock_operations
                                                : f2fs_up_write(&amp;amp;sbi-&amp;gt;node_write)
                                             f2fs_write_checkpoint//return
      : f2fs_do_write_node_page()
f2fs_ioc_commit_atomic_write//return
                                             SPO&lt;/p&gt;
&lt;p&gt;Thread A calls f2fs_need_dentry_mark(sbi, ino)…&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 IS_CHECKPOINTED flag inconsistency issue caused by concurrent atomic commit and checkpoint writes&lt;/p&gt;
&lt;p&gt;During SPO tests, when mounting F2FS, an -EINVAL error was returned from
f2fs_recover_inode_page. The issue occurred under the following scenario&lt;/p&gt;
&lt;p&gt;Thread A                                     Thread B
f2fs_ioc_commit_atomic_write
 - f2fs_do_sync_file // atomic = true
  - f2fs_fsync_node_pages
    : last_folio = inode folio
    : schedule before folio_lock(last_folio) f2fs_write_checkpoint
                                              - block_operations// writeback last_folio
                                              - schedule before f2fs_flush_nat_entries
    : set_fsync_mark(last_folio, 1)
    : set_dentry_mark(last_folio, 1)
    : folio_mark_dirty(last_folio)
    - __write_node_folio(last_folio)
      : f2fs_down_read(&amp;amp;sbi-&amp;gt;node_write)//block
                                              - f2fs_flush_nat_entries
                                                : {struct nat_entry}-&amp;gt;flag |= BIT(IS_CHECKPOINTED)
                                              - unblock_operations
                                                : f2fs_up_write(&amp;amp;sbi-&amp;gt;node_write)
                                             f2fs_write_checkpoint//return
      : f2fs_do_write_node_page()
f2fs_ioc_commit_atomic_write//return
                                             SPO&lt;/p&gt;
&lt;p&gt;Thread A calls f2fs_need_dentry_mark(sbi, ino)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9m9w-6gjg-9m6r</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-23267 — f2fs: fix IS_CHECKPOINTED flag inconsistency issue caused by concurrent atomic commit and checkpoint writes</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-23267</link>
      <description>msrc_CVE-2026-23267</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-23267</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23267</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23267</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 225 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix IS_CHECKPOINTED flag inconsistency issue caused by concurrent atomic commit and checkpoint writes During SPO tests, when mounting F2FS, an -EINVAL error was returned from f2fs_recover_inode_page. The issue occurred under the following scenario Thread A                                     Thread B f2fs_ioc_commit_atomic_write  - f2fs_do_sync_file // atomic = true   - f2fs_fsync_node_pages     : last_folio = inode folio     : schedule before folio_lock(last_folio) f2fs_write_checkpoint                                               - block_operations// writeback last_folio                                               - schedule before f2fs_flush_nat_entries     : set_fsync_mark(last_folio, 1)     : set_dentry_mark(last_folio, 1)     : folio_mark_dirty(last_folio)     - __write_node_folio(last_folio)       : f2fs_down_read(&amp;amp;sbi-&amp;gt;node_write)//block                                               - f2fs_flush_nat_entries                                                 : {struct nat_entry}-&amp;gt;flag |= BIT(IS_CHECKPOINTED)                                               - unblock_operations                                                 : f2fs_up_write(&amp;amp;sbi-&amp;gt;node_write)                                              f2fs_write_checkpoint//return       : f2fs_do_write_node_page() f2fs_ioc_commit_atomic_write//return                                              SPO Thread A calls f2fs_need_dentry_mark(sbi, ino), an…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 225 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: f2fs: fix IS_CHECKPOINTED flag inconsistency issue caused by concurrent atomic commit and checkpoint writes During SPO tests, when mounting F2FS, an -EINVAL error was returned from f2fs_recover_inode_page. The issue occurred under the following scenario Thread A                                     Thread B f2fs_ioc_commit_atomic_write  - f2fs_do_sync_file // atomic = true   - f2fs_fsync_node_pages     : last_folio = inode folio     : schedule before folio_lock(last_folio) f2fs_write_checkpoint                                               - block_operations// writeback last_folio                                               - schedule before f2fs_flush_nat_entries     : set_fsync_mark(last_folio, 1)     : set_dentry_mark(last_folio, 1)     : folio_mark_dirty(last_folio)     - __write_node_folio(last_folio)       : f2fs_down_read(&amp;amp;sbi-&amp;gt;node_write)//block                                               - f2fs_flush_nat_entries                                                 : {struct nat_entry}-&amp;gt;flag |= BIT(IS_CHECKPOINTED)                                               - unblock_operations                                                 : f2fs_up_write(&amp;amp;sbi-&amp;gt;node_write)                                              f2fs_write_checkpoint//return       : f2fs_do_write_node_page() f2fs_ioc_commit_atomic_write//return                                              SPO Thread A calls f2fs_need_dentry_mark(sbi, ino), an…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23267</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0790 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0790</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einem Denial-of-Service-Zustand, einer Rechteausweitung oder einer Speicherbeschädigung führen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einem Denial-of-Service-Zustand, einer Rechteausweitung oder einer Speicherbeschädigung führen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0790</guid>
    </item>
  </channel>
</rss>
