Google: sys-kernel/csql-kernel-6_1, sys-kernel/csql-kernel-6_6: security update to 18613.439.16

high Tenable Self-Hosted Container Security Plugin ID 466144

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: Don't leak disconnected dentries
on umount When user calls open_by_handle_at() on some inode that is not cached, we will create
disconnected dentry for it. If such dentry is a directory, exportfs_decode_fh_raw() will then try to
connect this dentry to the dentry tree through reconnect_path(). It may happen for various reasons (such
as corrupted fs or race with rename) that the call to lookup_one_unlocked() in reconnect_one() will fail
to find the dentry we are trying to reconnect and instead create a new dentry under the parent. Now this
dentry will not be marked as disconnected although the parent still may well be disconnected (at least in
case this inconsistency happened because the fs is corrupted and .. doesn't point to the real parent
directory). This creates inconsistency in disconnected flags but AFAICS it was mostly harmless. At least
until commit f1ee616214cb ("VFS: don't keep disconnected dentries on d_anon") which removed adding of most
disconnected dentries to sb->s_anon list. Thus after this commit cleanup of disconnected dentries
implicitely relies on the fact that dput() will immediately reclaim such dentries. However when some leaf
dentry isn't marked as disconnected, as in the scenario described above, the reclaim doesn't happen and
the dentries are "leaked". Memory reclaim can eventually reclaim them but otherwise they stay in memory
and if umount comes first, we hit infamous "Busy inodes after unmount" bug. Make sure all dentries created
under a disconnected parent are marked as disconnected as well. (CVE-2025-40105)

Solution

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

Plugin Details

Severity: High

ID: 466144

Version: Revision 1.2

Type: Local

Family: Google COS Security Checks

Published: 10/2/2026

Updated: 10/3/2026

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

Risk Information

VPR

Risk Factor: Medium

Score: 4.9

Percentile: 58.12

Vendor

Vendor Severity: LOW

CVSS v2

Risk Factor: Medium

Base Score: 6.8

Temporal Score: 5

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

CVSS Score Source: CVE-2025-40105

CVSS v3

Risk Factor: High

Base Score: 7.8

Temporal Score: 6.8

Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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/30/2025

Reference Information

CVE: CVE-2025-40105

Detections

Analytics