<?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://vulnerability.circl.lu</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>Thu, 01 Oct 2026 07:46:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-46160 — btrfs: fix missing last_unlink_trans update when removing a directory</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-46160</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&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://vulnerability.circl.lu/vuln/cve-2026-46160</guid>
    </item>
  </channel>
</rss>
