<?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://db.gcve.eu</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, 19 Nov 2026 17:05:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-47679 — vfs: fix race between evice_inodes() and find_inode()&amp;iput()</title>
      <link>https://db.gcve.eu/vuln/cve-2024-47679</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;vfs: fix race between evice_inodes() and find_inode()&amp;amp;iput()&lt;/p&gt;
&lt;p&gt;Hi, all&lt;/p&gt;
&lt;p&gt;Recently I noticed a bug[1] in btrfs, after digged it into
and I believe it&amp;#39;a race in vfs.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s assume there&amp;#39;s a inode (ie ino 261) with i_count 1 is
called by iput(), and there&amp;#39;s a concurrent thread calling
generic_shutdown_super().&lt;/p&gt;
&lt;p&gt;cpu0:                              cpu1:
iput() // i_count is 1
  -&amp;gt;spin_lock(inode)
  -&amp;gt;dec i_count to 0
  -&amp;gt;iput_final()                    generic_shutdown_super()
    -&amp;gt;__inode_add_lru()               -&amp;gt;evict_inodes()
      // cause some reason[2]           -&amp;gt;if (atomic_read(inode-&amp;gt;i_count)) continue;
      // return before                  // inode 261 passed the above check
      // list_lru_add_obj()             // and then schedule out
   -&amp;gt;spin_unlock()
// note here: the inode 261
// was still at sb list and hash list,
// and I_FREEING|I_WILL_FREE was not been set&lt;/p&gt;
&lt;p&gt;btrfs_iget()
  // after some function calls
  -&amp;gt;find_inode()
    // found the above inode 261
    -&amp;gt;spin_lock(inode)
   // check I_FREEING|I_WILL_FREE
   // and passed
      -&amp;gt;__iget()
    -&amp;gt;spin_unlock(inode)                // schedule back
                                        -&amp;gt;spin_lock(inode)
                                        // check (I_NEW|I_FREEING|I_WILL_FREE) flags,
                                        // passed and set I_FREEING
iput()                                  -&amp;gt;spin_unlock(inode)
  -&amp;gt;spin_lock(inode)…&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;vfs: fix race between evice_inodes() and find_inode()&amp;amp;iput()&lt;/p&gt;
&lt;p&gt;Hi, all&lt;/p&gt;
&lt;p&gt;Recently I noticed a bug[1] in btrfs, after digged it into
and I believe it&amp;#39;a race in vfs.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s assume there&amp;#39;s a inode (ie ino 261) with i_count 1 is
called by iput(), and there&amp;#39;s a concurrent thread calling
generic_shutdown_super().&lt;/p&gt;
&lt;p&gt;cpu0:                              cpu1:
iput() // i_count is 1
  -&amp;gt;spin_lock(inode)
  -&amp;gt;dec i_count to 0
  -&amp;gt;iput_final()                    generic_shutdown_super()
    -&amp;gt;__inode_add_lru()               -&amp;gt;evict_inodes()
      // cause some reason[2]           -&amp;gt;if (atomic_read(inode-&amp;gt;i_count)) continue;
      // return before                  // inode 261 passed the above check
      // list_lru_add_obj()             // and then schedule out
   -&amp;gt;spin_unlock()
// note here: the inode 261
// was still at sb list and hash list,
// and I_FREEING|I_WILL_FREE was not been set&lt;/p&gt;
&lt;p&gt;btrfs_iget()
  // after some function calls
  -&amp;gt;find_inode()
    // found the above inode 261
    -&amp;gt;spin_lock(inode)
   // check I_FREEING|I_WILL_FREE
   // and passed
      -&amp;gt;__iget()
    -&amp;gt;spin_unlock(inode)                // schedule back
                                        -&amp;gt;spin_lock(inode)
                                        // check (I_NEW|I_FREEING|I_WILL_FREE) flags,
                                        // passed and set I_FREEING
iput()                                  -&amp;gt;spin_unlock(inode)
  -&amp;gt;spin_lock(inode)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2024-47679</guid>
    </item>
    <item>
      <title>USN-7166-1 — linux, linux-gcp, linux-gcp-5.15, linux-gke, linux-gkeop, linux-ibm, linux-ibm-5.15, linux-kvm, linux-lowlatency, linux…</title>
      <link>https://db.gcve.eu/vuln/usn-7166-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: linux-gcp-5.15, Ubuntu:20.04:LTS: linux-ibm-5.15, Ubuntu:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:20.04:LTS: linux-oracle-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-gcp, Ubuntu:22.04:LTS: linux-gke, Ubuntu:22.04:LTS: linux-gkeop, Ubuntu:22.04:LTS: linux-ibm, Ubuntu:22.04:LTS: linux-kvm and 4 more&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - ACPI drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Buffer Sharing and Synchronization framework;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - I2C subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Mailbox framework;
  - Media drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - STMicroelectronics network drivers;
  - NTB driver;
  - Virtio pmem driver;
  - PCI subsystem;
  - x86 platform drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - SPI subsystem;
  - Thermal drivers;
  - USB Device Class drivers;
  - USB Type-C Port Controller Manager driver;
  - VFIO drivers;
  - Virtio Host (VHOST) subsystem;
  - Framebuffer layer;
  - 9P distributed file system;
  - BTRFS file system;
  - Ceph distributed file system;
  - File systems infrastructure;
  - Ext4 file system;
  - F2FS file system;
  - GFS2 file system;
  - JFS file system;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - NILFS2 file system;
  - Network file system (NFS)…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: linux-gcp-5.15, Ubuntu:20.04:LTS: linux-ibm-5.15, Ubuntu:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:20.04:LTS: linux-oracle-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-gcp, Ubuntu:22.04:LTS: linux-gke, Ubuntu:22.04:LTS: linux-gkeop, Ubuntu:22.04:LTS: linux-ibm, Ubuntu:22.04:LTS: linux-kvm and 4 more&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - ACPI drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Buffer Sharing and Synchronization framework;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - I2C subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Mailbox framework;
  - Media drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - STMicroelectronics network drivers;
  - NTB driver;
  - Virtio pmem driver;
  - PCI subsystem;
  - x86 platform drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - SPI subsystem;
  - Thermal drivers;
  - USB Device Class drivers;
  - USB Type-C Port Controller Manager driver;
  - VFIO drivers;
  - Virtio Host (VHOST) subsystem;
  - Framebuffer layer;
  - 9P distributed file system;
  - BTRFS file system;
  - Ceph distributed file system;
  - File systems infrastructure;
  - Ext4 file system;
  - F2FS file system;
  - GFS2 file system;
  - JFS file system;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - NILFS2 file system;
  - Network file system (NFS)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7166-1</guid>
    </item>
  </channel>
</rss>
