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

high Tenable Cloud Security Plugin ID 471196

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: tcp: call sk_data_ready() after
listener migration When inet_csk_listen_stop() migrates an established child socket from a closing
listener to another socket in the same SO_REUSEPORT group, the target listener gets a new accept-queue
entry via inet_csk_reqsk_queue_add(), but that path never notifies the target listener's waiters. A
nonblocking accept() still works because it checks the queue directly, but poll()/epoll_wait() waiters and
blocking accept() callers can also remain asleep indefinitely. Call READ_ONCE(nsk->sk_data_ready)(nsk)
after a successful migration in inet_csk_listen_stop(). However, after inet_csk_reqsk_queue_add()
succeeds, the ref acquired in reuseport_migrate_sock() is effectively transferred to nreq->rsk_listener.
Another CPU can then dequeue nreq via accept() or listener shutdown, hit reqsk_put(), and drop that
listener ref. Since listeners are SOCK_RCU_FREE, wrap the post-queue_add() dereferences of nsk in
rcu_read_lock()/rcu_read_unlock(), which also covers the existing sock_net(nsk) access in that path. The
reqsk_timer_handler() path does not need the same changes for two reasons: half-open requests become
readable only after the final ACK, where tcp_child_process() already wakes the listener; and once nreq is
visible via inet_ehash_insert(), the success path no longer touches nsk directly. (CVE-2026-46015)

Solution

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

Plugin Details

Severity: High

ID: 471196

Version: Revision 1.3

Type: Local

Family: Google COS Security Checks

Published: 10/3/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.17

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-46015

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: 5/26/2026

Reference Information

CVE: CVE-2026-46015

Detections

Analytics