<?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:06:18 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-68358</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-68358</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-68358</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-68358</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-68358</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: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document regarding memory barrier ordering guarantees:  (*) These guarantees do not apply to bitfields, because compilers often      generate code to modify these using non-atomic read-modify-write      sequences.  Do not attempt to use bitfields to synchronize parallel      algorithms.  (*) Even in cases where bitfields are protected by locks, all fields      in a given bitfield must be protected by one lock.  If two fields      in a given bitfield are protected by different locks, the compiler&amp;#39;s      non-atomic read-modify-write sequences can cause an update to one      field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info {         struct btrfs_fs_info *     fs_info;              /*     0     8 */         struct btrfs_space_info *  parent;               /*     8     8 */         ...         int                        clamp;                /*   172     4 */         unsigned int               full:1;               /*   176: 0  4 */         unsigned int               chunk_alloc:1;        /*   176: 1  4 */         unsigned int               flush:1;              /*   176: 2  4 */         ... Therefore, to be safe from parallel read-modify-writes losing a write to one of the bitfield mem…&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: fix racy bitfield write in btrfs_clear_space_info_full() From the memory-barriers.txt document regarding memory barrier ordering guarantees:  (*) These guarantees do not apply to bitfields, because compilers often      generate code to modify these using non-atomic read-modify-write      sequences.  Do not attempt to use bitfields to synchronize parallel      algorithms.  (*) Even in cases where bitfields are protected by locks, all fields      in a given bitfield must be protected by one lock.  If two fields      in a given bitfield are protected by different locks, the compiler&amp;#39;s      non-atomic read-modify-write sequences can cause an update to one      field to corrupt the value of an adjacent field. btrfs_space_info has a bitfield sharing an underlying word consisting of the fields full, chunk_alloc, and flush: struct btrfs_space_info {         struct btrfs_fs_info *     fs_info;              /*     0     8 */         struct btrfs_space_info *  parent;               /*     8     8 */         ...         int                        clamp;                /*   172     4 */         unsigned int               full:1;               /*   176: 0  4 */         unsigned int               chunk_alloc:1;        /*   176: 1  4 */         unsigned int               flush:1;              /*   176: 2  4 */         ... Therefore, to be safe from parallel read-modify-writes losing a write to one of the bitfield mem…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-68358</guid>
    </item>
  </channel>
</rss>
