<?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 00:34:56 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-68778</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-68778</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-2025-68778</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://127.0.0.1:10001/vuln/certfr-2026-avi-0166</link>
      <description>certfr-2026-avi-0166</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0166</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-68778</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-68778</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: btrfs: don&amp;#39;t log conflicting inode if it&amp;#39;s a dir moved in the current transaction We can&amp;#39;t log a conflicting inode if it&amp;#39;s a directory and it was moved from one parent directory to another parent directory in the current transaction, as this can result an attempt to have a directory with two hard links during log replay, one for the old parent directory and another for the new parent directory. The following scenario triggers that issue: 1) We have directories &amp;#34;dir1&amp;#34; and &amp;#34;dir2&amp;#34; created in a past transaction.    Directory &amp;#34;dir1&amp;#34; has inode A as its parent directory; 2) We move &amp;#34;dir1&amp;#34; to some other directory; 3) We create a file with the name &amp;#34;dir1&amp;#34; in directory inode A; 4) We fsync the new file. This results in logging the inode of the new file    and the inode for the directory &amp;#34;dir1&amp;#34; that was previously moved in the    current transaction. So the log tree has the INODE_REF item for the    new location of &amp;#34;dir1&amp;#34;; 5) We move the new file to some other directory. This results in updating    the log tree to included the new INODE_REF for the new location of the    file and removes the INODE_REF for the old location. This happens    during the rename when we call btrfs_log_new_name(); 6) We fsync the file, and that persists the log tree changes done in the    previous step (btrfs_log_new_name() only updates the log tree in    memory); 7) We have a power failure; 8) Next time the fs is mounted, log replay happens…&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: btrfs: don&amp;#39;t log conflicting inode if it&amp;#39;s a dir moved in the current transaction We can&amp;#39;t log a conflicting inode if it&amp;#39;s a directory and it was moved from one parent directory to another parent directory in the current transaction, as this can result an attempt to have a directory with two hard links during log replay, one for the old parent directory and another for the new parent directory. The following scenario triggers that issue: 1) We have directories &amp;#34;dir1&amp;#34; and &amp;#34;dir2&amp;#34; created in a past transaction.    Directory &amp;#34;dir1&amp;#34; has inode A as its parent directory; 2) We move &amp;#34;dir1&amp;#34; to some other directory; 3) We create a file with the name &amp;#34;dir1&amp;#34; in directory inode A; 4) We fsync the new file. This results in logging the inode of the new file    and the inode for the directory &amp;#34;dir1&amp;#34; that was previously moved in the    current transaction. So the log tree has the INODE_REF item for the    new location of &amp;#34;dir1&amp;#34;; 5) We move the new file to some other directory. This results in updating    the log tree to included the new INODE_REF for the new location of the    file and removes the INODE_REF for the old location. This happens    during the rename when we call btrfs_log_new_name(); 6) We fsync the file, and that persists the log tree changes done in the    previous step (btrfs_log_new_name() only updates the log tree in    memory); 7) We have a power failure; 8) Next time the fs is mounted, log replay happens…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-68778</guid>
    </item>
  </channel>
</rss>
