<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T19:13:02.629456+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bdu:2026-04158</id>
    <title>bdu:2026-04158</title>
    <updated>2026-10-07T19:13:02.642784+00:00</updated>
    <content>bdu:2026-04158</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-04158"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-23267</id>
    <title>BELL-CVE-2026-23267</title>
    <updated>2026-10-07T19:13:02.642824+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-23267"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0341</id>
    <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>
    <updated>2026-10-07T19:13:02.642855+00:00</updated>
    <content>certfr-2026-avi-0341</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-0341"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-315440</id>
    <title>EUVD-2026-315440</title>
    <updated>2026-10-07T19:13:02.642872+00:00</updated>
    <content>EUVD-2026-315440</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-315440"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23267</id>
    <title>fkie_cve-2026-23267</title>
    <updated>2026-10-07T19:13:02.642882+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>f2fs: fix IS_CHECKPOINTED flag inconsistency issue caused by concurrent atomic commit and checkpoint writes</p>
<p>During SPO tests, when mounting F2FS, an -EINVAL error was returned from
f2fs_recover_inode_page. The issue occurred under the following scenario</p>
<p>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;sbi-&gt;node_write)//block
                                              - f2fs_flush_nat_entries
                                                : {struct nat_entry}-&gt;flag |= BIT(IS_CHECKPOINTED)
                                              - unblock_operations
                                                : f2fs_up_write(&amp;sbi-&gt;node_write)
                                             f2fs_write_checkpoint//return
      : f2fs_do_write_node_page()
f2fs_ioc_commit_atomic_write//return
                                             SPO</p>
<p>Thread A calls f2fs_need_dentry_mark(sbi, ino)…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-23267"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-9m9w-6gjg-9m6r</id>
    <title>GHSA-9m9w-6gjg-9m6r</title>
    <updated>2026-10-07T19:13:02.642927+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>f2fs: fix IS_CHECKPOINTED flag inconsistency issue caused by concurrent atomic commit and checkpoint writes</p>
<p>During SPO tests, when mounting F2FS, an -EINVAL error was returned from
f2fs_recover_inode_page. The issue occurred under the following scenario</p>
<p>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;sbi-&gt;node_write)//block
                                              - f2fs_flush_nat_entries
                                                : {struct nat_entry}-&gt;flag |= BIT(IS_CHECKPOINTED)
                                              - unblock_operations
                                                : f2fs_up_write(&amp;sbi-&gt;node_write)
                                             f2fs_write_checkpoint//return
      : f2fs_do_write_node_page()
f2fs_ioc_commit_atomic_write//return
                                             SPO</p>
<p>Thread A calls f2fs_need_dentry_mark(sbi, ino)…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-9m9w-6gjg-9m6r"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-23267</id>
    <title>msrc_CVE-2026-23267 — f2fs: fix IS_CHECKPOINTED flag inconsistency issue caused by concurrent atomic commit and checkpoint writes</title>
    <updated>2026-10-07T19:13:02.642966+00:00</updated>
    <content>msrc_CVE-2026-23267</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-23267"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23267</id>
    <title>UBUNTU-CVE-2026-23267</title>
    <updated>2026-10-07T19:13:02.642983+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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;sbi-&gt;node_write)//block                                               - f2fs_flush_nat_entries                                                 : {struct nat_entry}-&gt;flag |= BIT(IS_CHECKPOINTED)                                               - unblock_operations                                                 : f2fs_up_write(&amp;sbi-&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…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23267"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0790</id>
    <title>WID-SEC-W-2026-0790 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-07T19:13:02.643247+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0790"/>
  </entry>
</feed>
