Google: sys-kernel/csql-kernel-6_12, sys-kernel/csql-kernel-6_6: security update to 19216.0.62

medium Tenable Cloud Security Plugin ID 467894

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: btrfs: fix subvolume deletion lockup
caused by inodes xarray race There is a race condition between inode eviction and inode caching that can
cause a live struct btrfs_inode to be missing from the root->inodes xarray. Specifically, there is a
window during evict() between the inode being unhashed and deleted from the xarray. If btrfs_iget() is
called for the same inode in that window, it will be recreated and inserted into the xarray, but then
eviction will delete the new entry, leaving nothing in the xarray: Thread 1 Thread 2
--------------------------------------------------------------- evict() remove_inode_hash()
btrfs_iget_path() btrfs_iget_locked() btrfs_read_locked_inode() btrfs_add_inode_to_root() destroy_inode()
btrfs_destroy_inode() btrfs_del_inode_from_root() __xa_erase In turn, this can cause issues for subvolume
deletion. Specifically, if an inode is in this lost state, and all other inodes are evicted, then
btrfs_del_inode_from_root() will call btrfs_add_dead_root() prematurely. If the lost inode has a
delayed_node attached to it, then when btrfs_clean_one_deleted_snapshot() calls
btrfs_kill_all_delayed_nodes(), it will loop forever because the delayed_nodes xarray will never become
empty (unless memory pressure forces the inode out). We saw this manifest as soft lockups in production.
Fix it by only deleting the xarray entry if it matches the given inode (using __xa_cmpxchg()).
(CVE-2025-39884)

Solution

Update the sys-kernel/csql-kernel-6_12 library and its related packages to version 19216.0.62 or later.

Plugin Details

Severity: Medium

ID: 467894

Version: Revision 1.4

Type: Local

Family: Google COS Security Checks

Published: 10/3/2026

Updated: 10/6/2026

Supported Sensors: Tenable Cloud Security, Tenable Self-Hosted Container Security

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.34

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-2025-39884

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: 9/23/2025

Reference Information

CVE: CVE-2025-39884

Detections

Analytics