<?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://cve.radiocsirt.org</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>Fri, 02 Oct 2026 16:33:14 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-46160</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-46160</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://cve.radiocsirt.org/vuln/bell-cve-2026-46160</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0731 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Certaines d'entre elles permettent à un at…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0731</link>
      <description>certfr-2026-avi-0731</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0731</guid>
    </item>
    <item>
      <title>EUVD-2026-328699</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-328699</link>
      <description>EUVD-2026-328699</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-328699</guid>
    </item>
    <item>
      <title>fkie_cve-2026-46160</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-46160</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;btrfs: fix missing last_unlink_trans update when removing a directory&lt;/p&gt;
&lt;p&gt;When removing a directory we are not updating its last_unlink_trans field,
which can result in incorrect fsync behaviour in case some one fsyncs the
directory after it was removed because it&amp;#39;s holding a file descriptor on
it.&lt;/p&gt;
&lt;p&gt;Example scenario:&lt;/p&gt;
&lt;p&gt;mkdir /mnt/dir1
   mkdir /mnt/dir1/dir2
   mkdir /mnt/dir3&lt;/p&gt;
&lt;p&gt;sync -f /mnt&lt;/p&gt;
&lt;p&gt;# Do some change to the directory and fsync it.
   chmod 700 /mnt/dir1
   xfs_io -c fsync /mnt/dir1&lt;/p&gt;
&lt;p&gt;# Move dir2 out of dir1 so that dir1 becomes empty.
   mv /mnt/dir1/dir2 /mnt/dir3/&lt;/p&gt;
&lt;p&gt;open fd on /mnt/dir1
   call rmdir(2) on path &amp;#34;/mnt/dir1&amp;#34;
   fsync fd&lt;/p&gt;
&lt;p&gt;&amp;lt;trigger power failure&amp;gt;&lt;/p&gt;
&lt;p&gt;When attempting to mount the filesystem, the log replay will fail with
an -EIO error and dmesg/syslog has the following:&lt;/p&gt;
&lt;p&gt;[445771.626482] BTRFS info (device dm-0): first mount of filesystem 0368bbea-6c5e-44b5-b409-09abe496e650
   [445771.626486] BTRFS info (device dm-0): using crc32c checksum algorithm
   [445771.627912] BTRFS info (device dm-0): start tree-log replay
   [445771.628335] page: refcount:2 mapcount:0 mapping:0000000061443ddc index:0x1d00 pfn:0x7072a5
   [445771.629453] memcg:ffff89f400351b00
   [445771.629892] aops:btree_aops [btrfs] ino:1
   [445771.630737] flags: 0x17fffc00000402a(uptodate|lru|private|writeback|node=0|zone=2|lastcpupid=0x1ffff)
   [445771.632359] raw: 017fffc00000402a fffff47284d950c8 fffff4729…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;btrfs: fix missing last_unlink_trans update when removing a directory&lt;/p&gt;
&lt;p&gt;When removing a directory we are not updating its last_unlink_trans field,
which can result in incorrect fsync behaviour in case some one fsyncs the
directory after it was removed because it&amp;#39;s holding a file descriptor on
it.&lt;/p&gt;
&lt;p&gt;Example scenario:&lt;/p&gt;
&lt;p&gt;mkdir /mnt/dir1
   mkdir /mnt/dir1/dir2
   mkdir /mnt/dir3&lt;/p&gt;
&lt;p&gt;sync -f /mnt&lt;/p&gt;
&lt;p&gt;# Do some change to the directory and fsync it.
   chmod 700 /mnt/dir1
   xfs_io -c fsync /mnt/dir1&lt;/p&gt;
&lt;p&gt;# Move dir2 out of dir1 so that dir1 becomes empty.
   mv /mnt/dir1/dir2 /mnt/dir3/&lt;/p&gt;
&lt;p&gt;open fd on /mnt/dir1
   call rmdir(2) on path &amp;#34;/mnt/dir1&amp;#34;
   fsync fd&lt;/p&gt;
&lt;p&gt;&amp;lt;trigger power failure&amp;gt;&lt;/p&gt;
&lt;p&gt;When attempting to mount the filesystem, the log replay will fail with
an -EIO error and dmesg/syslog has the following:&lt;/p&gt;
&lt;p&gt;[445771.626482] BTRFS info (device dm-0): first mount of filesystem 0368bbea-6c5e-44b5-b409-09abe496e650
   [445771.626486] BTRFS info (device dm-0): using crc32c checksum algorithm
   [445771.627912] BTRFS info (device dm-0): start tree-log replay
   [445771.628335] page: refcount:2 mapcount:0 mapping:0000000061443ddc index:0x1d00 pfn:0x7072a5
   [445771.629453] memcg:ffff89f400351b00
   [445771.629892] aops:btree_aops [btrfs] ino:1
   [445771.630737] flags: 0x17fffc00000402a(uptodate|lru|private|writeback|node=0|zone=2|lastcpupid=0x1ffff)
   [445771.632359] raw: 017fffc00000402a fffff47284d950c8 fffff4729…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-46160</guid>
    </item>
    <item>
      <title>GHSA-xvrh-2655-9jjv</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xvrh-2655-9jjv</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;btrfs: fix missing last_unlink_trans update when removing a directory&lt;/p&gt;
&lt;p&gt;When removing a directory we are not updating its last_unlink_trans field,
which can result in incorrect fsync behaviour in case some one fsyncs the
directory after it was removed because it&amp;#39;s holding a file descriptor on
it.&lt;/p&gt;
&lt;p&gt;Example scenario:&lt;/p&gt;
&lt;p&gt;mkdir /mnt/dir1
   mkdir /mnt/dir1/dir2
   mkdir /mnt/dir3&lt;/p&gt;
&lt;p&gt;sync -f /mnt&lt;/p&gt;
&lt;p&gt;# Do some change to the directory and fsync it.
   chmod 700 /mnt/dir1
   xfs_io -c fsync /mnt/dir1&lt;/p&gt;
&lt;p&gt;# Move dir2 out of dir1 so that dir1 becomes empty.
   mv /mnt/dir1/dir2 /mnt/dir3/&lt;/p&gt;
&lt;p&gt;open fd on /mnt/dir1
   call rmdir(2) on path &amp;#34;/mnt/dir1&amp;#34;
   fsync fd&lt;/p&gt;
&lt;p&gt;&amp;lt;trigger power failure&amp;gt;&lt;/p&gt;
&lt;p&gt;When attempting to mount the filesystem, the log replay will fail with
an -EIO error and dmesg/syslog has the following:&lt;/p&gt;
&lt;p&gt;[445771.626482] BTRFS info (device dm-0): first mount of filesystem 0368bbea-6c5e-44b5-b409-09abe496e650
   [445771.626486] BTRFS info (device dm-0): using crc32c checksum algorithm
   [445771.627912] BTRFS info (device dm-0): start tree-log replay
   [445771.628335] page: refcount:2 mapcount:0 mapping:0000000061443ddc index:0x1d00 pfn:0x7072a5
   [445771.629453] memcg:ffff89f400351b00
   [445771.629892] aops:btree_aops [btrfs] ino:1
   [445771.630737] flags: 0x17fffc00000402a(uptodate|lru|private|writeback|node=0|zone=2|lastcpupid=0x1ffff)
   [445771.632359] raw: 017fffc00000402a fffff47284d950c8 fffff4729…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;btrfs: fix missing last_unlink_trans update when removing a directory&lt;/p&gt;
&lt;p&gt;When removing a directory we are not updating its last_unlink_trans field,
which can result in incorrect fsync behaviour in case some one fsyncs the
directory after it was removed because it&amp;#39;s holding a file descriptor on
it.&lt;/p&gt;
&lt;p&gt;Example scenario:&lt;/p&gt;
&lt;p&gt;mkdir /mnt/dir1
   mkdir /mnt/dir1/dir2
   mkdir /mnt/dir3&lt;/p&gt;
&lt;p&gt;sync -f /mnt&lt;/p&gt;
&lt;p&gt;# Do some change to the directory and fsync it.
   chmod 700 /mnt/dir1
   xfs_io -c fsync /mnt/dir1&lt;/p&gt;
&lt;p&gt;# Move dir2 out of dir1 so that dir1 becomes empty.
   mv /mnt/dir1/dir2 /mnt/dir3/&lt;/p&gt;
&lt;p&gt;open fd on /mnt/dir1
   call rmdir(2) on path &amp;#34;/mnt/dir1&amp;#34;
   fsync fd&lt;/p&gt;
&lt;p&gt;&amp;lt;trigger power failure&amp;gt;&lt;/p&gt;
&lt;p&gt;When attempting to mount the filesystem, the log replay will fail with
an -EIO error and dmesg/syslog has the following:&lt;/p&gt;
&lt;p&gt;[445771.626482] BTRFS info (device dm-0): first mount of filesystem 0368bbea-6c5e-44b5-b409-09abe496e650
   [445771.626486] BTRFS info (device dm-0): using crc32c checksum algorithm
   [445771.627912] BTRFS info (device dm-0): start tree-log replay
   [445771.628335] page: refcount:2 mapcount:0 mapping:0000000061443ddc index:0x1d00 pfn:0x7072a5
   [445771.629453] memcg:ffff89f400351b00
   [445771.629892] aops:btree_aops [btrfs] ino:1
   [445771.630737] flags: 0x17fffc00000402a(uptodate|lru|private|writeback|node=0|zone=2|lastcpupid=0x1ffff)
   [445771.632359] raw: 017fffc00000402a fffff47284d950c8 fffff4729…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xvrh-2655-9jjv</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-46160 — btrfs: fix missing last_unlink_trans update when removing a directory</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-46160</link>
      <description>msrc_CVE-2026-46160</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-46160</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10954-1 — kernel-devel-7.0.11-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1</link>
      <description>&lt;p&gt;kernel-devel-7.0.11-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.0.11-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10954-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:22433-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:22433-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:22433-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-46160</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46160</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 253 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: fix missing last_unlink_trans update when removing a directory When removing a directory we are not updating its last_unlink_trans field, which can result in incorrect fsync behaviour in case some one fsyncs the directory after it was removed because it&amp;#39;s holding a file descriptor on it. Example scenario:    mkdir /mnt/dir1    mkdir /mnt/dir1/dir2    mkdir /mnt/dir3    sync -f /mnt    # Do some change to the directory and fsync it.    chmod 700 /mnt/dir1    xfs_io -c fsync /mnt/dir1    # Move dir2 out of dir1 so that dir1 becomes empty.    mv /mnt/dir1/dir2 /mnt/dir3/    open fd on /mnt/dir1    call rmdir(2) on path &amp;#34;/mnt/dir1&amp;#34;    fsync fd    &amp;lt;trigger power failure&amp;gt; When attempting to mount the filesystem, the log replay will fail with an -EIO error and dmesg/syslog has the following:    [445771.626482] BTRFS info (device dm-0): first mount of filesystem 0368bbea-6c5e-44b5-b409-09abe496e650    [445771.626486] BTRFS info (device dm-0): using crc32c checksum algorithm    [445771.627912] BTRFS info (device dm-0): start tree-log replay    [445771.628335] page: refcount:2 mapcount:0 mapping:0000000061443ddc index:0x1d00 pfn:0x7072a5    [445771.629453] memcg:ffff89f400351b00    [445771.629892] aops:btree_aops [btrfs] ino:1    [445771.630737] flags: 0x17fffc00000402a(uptodate|lru|private|writeback|node=0|zone=2|lastcpupid=0x1ffff)    [445771.632359] raw: 017fffc00000402a fffff47284d950c8 fffff472907b7c08 fff…&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 253 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: fix missing last_unlink_trans update when removing a directory When removing a directory we are not updating its last_unlink_trans field, which can result in incorrect fsync behaviour in case some one fsyncs the directory after it was removed because it&amp;#39;s holding a file descriptor on it. Example scenario:    mkdir /mnt/dir1    mkdir /mnt/dir1/dir2    mkdir /mnt/dir3    sync -f /mnt    # Do some change to the directory and fsync it.    chmod 700 /mnt/dir1    xfs_io -c fsync /mnt/dir1    # Move dir2 out of dir1 so that dir1 becomes empty.    mv /mnt/dir1/dir2 /mnt/dir3/    open fd on /mnt/dir1    call rmdir(2) on path &amp;#34;/mnt/dir1&amp;#34;    fsync fd    &amp;lt;trigger power failure&amp;gt; When attempting to mount the filesystem, the log replay will fail with an -EIO error and dmesg/syslog has the following:    [445771.626482] BTRFS info (device dm-0): first mount of filesystem 0368bbea-6c5e-44b5-b409-09abe496e650    [445771.626486] BTRFS info (device dm-0): using crc32c checksum algorithm    [445771.627912] BTRFS info (device dm-0): start tree-log replay    [445771.628335] page: refcount:2 mapcount:0 mapping:0000000061443ddc index:0x1d00 pfn:0x7072a5    [445771.629453] memcg:ffff89f400351b00    [445771.629892] aops:btree_aops [btrfs] ino:1    [445771.630737] flags: 0x17fffc00000402a(uptodate|lru|private|writeback|node=0|zone=2|lastcpupid=0x1ffff)    [445771.632359] raw: 017fffc00000402a fffff47284d950c8 fffff472907b7c08 fff…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-46160</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1700 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht näher spezifizierte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1700</guid>
    </item>
  </channel>
</rss>
