<?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://127.0.0.1:10001</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, 21 Nov 2026 08:57:06 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-23465</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-23465</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://127.0.0.1:10001/vuln/bell-cve-2026-23465</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0548 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0548</link>
      <description>certfr-2026-avi-0548</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0548</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23465</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23465</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 206 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: log new dentries when logging parent dir of a conflicting inode If we log the parent directory of a conflicting inode, we are not logging the new dentries of the directory, so when we finish we have the parent directory&amp;#39;s inode marked as logged but we did not log its new dentries. As a consequence if the parent directory is explicitly fsynced later and it does not have any new changes since we logged it, the fsync is a no-op and after a power failure the new dentries are missing. Example scenario:   $ mkdir foo   $ sync   $rmdir foo   $ mkdir dir1   $ mkdir dir2   # A file with the same name and parent as the directory we just deleted   # and was persisted in a past transaction. So the deleted directory&amp;#39;s   # inode is a conflicting inode of this new file&amp;#39;s inode.   $ touch foo   $ ln foo dir2/link   # The fsync on dir2 will log the parent directory (&amp;#34;.&amp;#34;) because the   # conflicting inode (deleted directory) does not exists anymore, but it   # it does not log its new dentries (dir1).   $ xfs_io -c &amp;#34;fsync&amp;#34; dir2   # This fsync on the parent directory is no-op, since the previous fsync   # logged it (but without logging its new dentries).   $ xfs_io -c &amp;#34;fsync&amp;#34; .   &amp;lt;power failure&amp;gt;   # After log replay dir1 is missing. Fix this by ensuring we log new dir dentries whenever we log the parent directory of a no longer existing conflicting inode. A test case for fstests will follow soon.&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 206 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: log new dentries when logging parent dir of a conflicting inode If we log the parent directory of a conflicting inode, we are not logging the new dentries of the directory, so when we finish we have the parent directory&amp;#39;s inode marked as logged but we did not log its new dentries. As a consequence if the parent directory is explicitly fsynced later and it does not have any new changes since we logged it, the fsync is a no-op and after a power failure the new dentries are missing. Example scenario:   $ mkdir foo   $ sync   $rmdir foo   $ mkdir dir1   $ mkdir dir2   # A file with the same name and parent as the directory we just deleted   # and was persisted in a past transaction. So the deleted directory&amp;#39;s   # inode is a conflicting inode of this new file&amp;#39;s inode.   $ touch foo   $ ln foo dir2/link   # The fsync on dir2 will log the parent directory (&amp;#34;.&amp;#34;) because the   # conflicting inode (deleted directory) does not exists anymore, but it   # it does not log its new dentries (dir1).   $ xfs_io -c &amp;#34;fsync&amp;#34; dir2   # This fsync on the parent directory is no-op, since the previous fsync   # logged it (but without logging its new dentries).   $ xfs_io -c &amp;#34;fsync&amp;#34; .   &amp;lt;power failure&amp;gt;   # After log replay dir1 is missing. Fix this by ensuring we log new dir dentries whenever we log the parent directory of a no longer existing conflicting inode. A test case for fstests will follow soon.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23465</guid>
    </item>
  </channel>
</rss>
