Detections
Analytics

Google: sys-kernel/cchost-kernel-6_18, sys-kernel/csql-kernel-6_18, sys-kernel/lakitu-kernel-6_18, sys-kernel/lakitu-nc-kernel-6_18: security update to 20162.0.0

high Tenable Self-Hosted Container Security Plugin ID 475675

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: sunrpc: init gssp_lock before
 publishing proc entry create_use_gss_proxy_proc_entry() publishes /proc/net/rpc/use-gss-proxy via
 proc_create_data() before init_gssp_clnt() runs mutex_init() on sn->gssp_lock. Once the dentry is linked
 under proc_subdir_lock it is immediately reachable from userspace, so a write that lands in the window
 drives set_gssp_clnt() into mutex_lock() on a zero-initialized struct mutex.
 create_use_gss_proxy_proc_entry(net) proc_create_data("use-gss-proxy", ...) /* dentry live */
 init_gssp_clnt(sn) mutex_init(&sn->gssp_lock) /* too late */ write_gssp() set_gssp_clnt(net)
 mutex_lock(&sn->gssp_lock) /* uninitialized */ gssp_rpc_create(...) sn->gssp_clnt = clnt
 mutex_unlock(&sn->gssp_lock) The window spans only the two statements between proc_create_data() returning
 and init_gssp_clnt(), so a writer reaches it only if the registering thread is preempted there while
 another task is already opening the freshly published file. register_pernet_subsys() runs in preemptible
 context under pernet_ops_rwsem, so that preemption is possible, and the window widens on auth_rpcgss
 module load, when the proc entry is created for every live net namespace whose tasks are already running.
 A writer that wins the race locks a zero-filled struct mutex. On CONFIG_DEBUG_MUTEXES the missing magic
 value trips a "lock used without init" splat; on a production kernel the fast path acquires the lock via
 CMPXCHG(owner, 0, current). In the latter case a second writer that arrives before init_gssp_clnt() re-
 zeroes owner can enter set_gssp_clnt() concurrently, shut down the first writer's clnt while it is still
 in use, and leak the loser's clnt. Fix by initializing sn->gssp_lock in sunrpc_init_net() so its lifetime
 matches the sunrpc_net it lives in. sn->gssp_clnt is already NULL from the kzalloc that backs net_generic
 storage, so the lazy helper is no longer needed; drop init_gssp_clnt(), its prototype, and the call from
 create_use_gss_proxy_proc_entry(). sunrpc.ko is a build-time dependency of auth_rpcgss.ko, so
 sunrpc_init_net() has always run on every netns before any auth_gss pernet init can publish the proc
 entry. (CVE-2026-89540)

Solution

Update the sys-kernel/cchost-kernel-6_18 library and its related packages to version 20162.0.0 or later.

See Also

https://storage.googleapis.com/cos-oval-vulnerability-feed/cos-138.oval.xml.tar.gz

Plugin Details

Severity: High

ID: 475675

Version: Revision 1.1

Type: Local

Published: 10/16/2026

Updated: 10/16/2026

Risk Information

VPR

Risk Factor: Medium

Score: 6.9

Percentile: 96.43

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-2026-89540

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: 9/11/2026

Reference Information

CVE: CVE-2026-89540