<?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 13:12:12 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-43361</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-43361</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-43361</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0745 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0745</link>
      <description>certfr-2026-avi-0745</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0745</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-43361</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43361</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 234 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: fix transaction abort when snapshotting received subvolumes Currently a user can trigger a transaction abort by snapshotting a previously received snapshot a bunch of times until we reach a BTRFS_UUID_KEY_RECEIVED_SUBVOL item overflow (the maximum item size we can store in a leaf). This is very likely not common in practice, but if it happens, it turns the filesystem into RO mode. The snapshot, send and set_received_subvol and subvol_setflags (used by receive) don&amp;#39;t require CAP_SYS_ADMIN, just inode_owner_or_capable(). A malicious user could use this to turn a filesystem into RO mode and disrupt a system. Reproducer script:   $ cat test.sh   #!/bin/bash   DEV=/dev/sdi   MNT=/mnt/sdi   # Use smallest node size to make the test faster.   mkfs.btrfs -f --nodesize 4K $DEV   mount $DEV $MNT   # Create a subvolume and set it to RO so that it can be used for send.   btrfs subvolume create $MNT/sv   touch $MNT/sv/foo   btrfs property set $MNT/sv ro true   # Send and receive the subvolume into snaps/sv.   mkdir $MNT/snaps   btrfs send $MNT/sv | btrfs receive $MNT/snaps   # Now snapshot the received subvolume, which has a received_uuid, a   # lot of times to trigger the leaf overflow.   total=500   for ((i = 1; i &amp;lt;= $total; i++)); do       echo -ne &amp;#34;\rCreating snapshot $i/$total&amp;#34;       btrfs subvolume snapshot -r $MNT/snaps/sv $MNT/snaps/sv_$i &amp;gt; /dev/null   done   echo   umount $MNT When running the test:   $ .…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 234 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: fix transaction abort when snapshotting received subvolumes Currently a user can trigger a transaction abort by snapshotting a previously received snapshot a bunch of times until we reach a BTRFS_UUID_KEY_RECEIVED_SUBVOL item overflow (the maximum item size we can store in a leaf). This is very likely not common in practice, but if it happens, it turns the filesystem into RO mode. The snapshot, send and set_received_subvol and subvol_setflags (used by receive) don&amp;#39;t require CAP_SYS_ADMIN, just inode_owner_or_capable(). A malicious user could use this to turn a filesystem into RO mode and disrupt a system. Reproducer script:   $ cat test.sh   #!/bin/bash   DEV=/dev/sdi   MNT=/mnt/sdi   # Use smallest node size to make the test faster.   mkfs.btrfs -f --nodesize 4K $DEV   mount $DEV $MNT   # Create a subvolume and set it to RO so that it can be used for send.   btrfs subvolume create $MNT/sv   touch $MNT/sv/foo   btrfs property set $MNT/sv ro true   # Send and receive the subvolume into snaps/sv.   mkdir $MNT/snaps   btrfs send $MNT/sv | btrfs receive $MNT/snaps   # Now snapshot the received subvolume, which has a received_uuid, a   # lot of times to trigger the leaf overflow.   total=500   for ((i = 1; i &amp;lt;= $total; i++)); do       echo -ne &amp;#34;\rCreating snapshot $i/$total&amp;#34;       btrfs subvolume snapshot -r $MNT/snaps/sv $MNT/snaps/sv_$i &amp;gt; /dev/null   done   echo   umount $MNT When running the test:   $ .…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43361</guid>
    </item>
  </channel>
</rss>
