Google: sys-kernel/csql-kernel-6_6, sys-kernel/lakitu-kernel-6_6, sys-kernel/lakitu-nc-kernel-6_6, sys-kernel/lakitu-vgpu-kernel-6_6, sys-kernel/tpusev-kernel-6_6: security update to 18613.731.2

critical Tenable Self-Hosted Container Security Plugin ID 466098

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: pin svc_xprt across the
asynchronous TLS handshake callback svc_tcp_handshake() stores the raw svc_xprt pointer in
tls_handshake_args.ta_data and submits the request through tls_server_hello_x509(). The handshake core
takes only sock_hold(req->hr_sk); nothing references the embedding struct svc_sock that
svc_tcp_handshake_done() reaches via container_of(). Two close races leave the in-flight callback writing
through a freed svc_sock. svc_sock_free() calls tls_handshake_cancel() and discards its return value: a
false return means handshake_complete() has already set HANDSHAKE_F_REQ_COMPLETED but hp_done() may not
have finished, yet svc_sock_free() proceeds to kfree(svsk). The cancel-loser fall-through inside
svc_tcp_handshake() itself produces the same window: when wait_for_completion_interruptible_timeout()
returns <= 0 (timeout or signal) and tls_handshake_cancel() returns false, the function does not drain,
returns, and svc_handle_xprt() calls svc_xprt_received(), which clears XPT_BUSY and can drop the last
reference. A concurrent close then runs svc_sock_free() while svc_tcp_handshake_done() is still updating
xpt_flags and walking svsk->sk_handshake_done. The corruption surfaces as set_bit/clear_bit RMW into the
freed xpt_flags slab slot and as complete_all() walking and writing the freed wait_queue_head_t list
embedded in sk_handshake_done -- a slab-corruption primitive, not a benign read. The path is reachable on
any TLS-enabled NFS server whenever a connection close overlaps the tlshd downcall delivery window; the
interruptible wait means signal delivery suffices, not just SVC_HANDSHAKE_TO expiry. Take
svc_xprt_get(xprt) immediately before tls_server_hello_x509() so the in-flight callback owns its own
reference. Release it on the two edges where the callback is guaranteed not to fire -- submission failure
from tls_server_hello_x509() and a successful tls_handshake_cancel() -- and at the tail of
svc_tcp_handshake_done() after complete_all(). [cel: rewrote commit message to describe the actual change]
(CVE-2026-72222)

Solution

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

Plugin Details

Severity: Critical

ID: 466098

Version: Revision 1.2

Type: Local

Family: Google COS Security Checks

Published: 10/2/2026

Updated: 10/3/2026

Risk Information

VPR

Risk Factor: Medium

Score: 6.9

Percentile: 96.56

Vendor

Vendor Severity: LOW

CVSS v2

Risk Factor: Critical

Base Score: 10

Temporal Score: 7.4

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

CVSS Score Source: CVE-2026-72222

CVSS v3

Risk Factor: Critical

Base Score: 9.8

Temporal Score: 8.5

Vector: CVSS:3.0/AV:N/AC:L/PR:N/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: 8/11/2026

Reference Information

CVE: CVE-2026-72222

Detections

Analytics