Google: sys-kernel/lakitu-kernel-6_1, sys-kernel/lakitu-kernel-6_6: security update to 18613.75.4

medium Tenable Cloud Security Plugin ID 471439

Description

There are packages installed that are affected by a vulnerability referenced in the following CVE:

- In the Linux kernel, the following vulnerability has been resolved: vfs: fix race between evice_inodes()
and find_inode()&iput() Hi, all Recently I noticed a bug[1] in btrfs, after digged it into and I believe
it'a race in vfs. Let's assume there's a inode (ie ino 261) with i_count 1 is called by iput(), and
there's a concurrent thread calling generic_shutdown_super(). cpu0: cpu1: iput() // i_count is 1
->spin_lock(inode) ->dec i_count to 0 ->iput_final() generic_shutdown_super() ->__inode_add_lru()
->evict_inodes() // cause some reason[2] ->if (atomic_read(inode->i_count)) continue; // return before //
inode 261 passed the above check // list_lru_add_obj() // and then schedule out ->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
btrfs_iget() // after some function calls ->find_inode() // found the above inode 261 ->spin_lock(inode)
// check I_FREEING|I_WILL_FREE // and passed ->__iget() ->spin_unlock(inode) // schedule back
->spin_lock(inode) // check (I_NEW|I_FREEING|I_WILL_FREE) flags, // passed and set I_FREEING iput()
->spin_unlock(inode) ->spin_lock(inode) ->evict() // dec i_count to 0 ->iput_final() ->spin_unlock()
->evict() Now, we have two threads simultaneously evicting the same inode, which may trigger the
BUG(inode->i_state & I_CLEAR) statement both within clear_inode() and iput(). To fix the bug, recheck the
inode->i_count after holding i_lock. Because in the most scenarios, the first check is valid, and the
overhead of spin_lock() can be reduced. If there is any misunderstanding, please let me know, thanks. [1]:
https://lore.kernel.org/linux-btrfs/[email protected]/ [2]: The reason might be 1.
SB_ACTIVE was removed or 2. mapping_shrinkable() return false when I reproduced the bug. (CVE-2024-47679)

Solution

Update the sys-kernel/lakitu-kernel-6_1 library and its related packages to version 18613.75.4 or later.

Plugin Details

Severity: Medium

ID: 471439

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/3/2026

Updated: 10/3/2026

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.18

Vendor

Vendor Severity: MEDIUM

CVSS v2

Risk Factor: Low

Base Score: 3.8

Temporal Score: 2.8

Vector: CVSS2#AV:L/AC:H/Au:S/C:N/I:N/A:C

CVSS Score Source: CVE-2024-47679

CVSS v3

Risk Factor: Medium

Base Score: 4.7

Temporal Score: 4.1

Vector: CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C

Vulnerability Information

Exploit Ease: No known exploits are available

Vulnerability Publication Date: 10/21/2024

Reference Information

CVE: CVE-2024-47679

Detections

Analytics