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

medium Tenable Cloud Security Plugin ID 470823

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: netfilter: nf_tables: do not defer
rule destruction via call_rcu nf_tables_chain_destroy can sleep, it can't be used from call_rcu callbacks.
Moreover, nf_tables_rule_release() is only safe for error unwinding, while transaction mutex is held and
the to-be-desroyed rule was not exposed to either dataplane or dumps, as it deactives+frees without the
required synchronize_rcu() in-between. nft_rule_expr_deactivate() callbacks will change ->use counters of
other chains/sets, see e.g. nft_lookup .deactivate callback, these must be serialized via transaction
mutex. Also add a few lockdep asserts to make this more explicit. Calling synchronize_rcu() isn't ideal,
but fixing this without is hard and way more intrusive. As-is, we can get: WARNING: ..
net/netfilter/nf_tables_api.c:5515 nft_set_destroy+0x.. Workqueue: events nf_tables_trans_destroy_work
RIP: 0010:nft_set_destroy+0x3fe/0x5c0 Call Trace: <TASK> nf_tables_trans_destroy_work+0x6b7/0xad0
process_one_work+0x64a/0xce0 worker_thread+0x613/0x10d0 In case the synchronize_rcu becomes an issue, we
can explore alternatives. One way would be to allocate nft_trans_rule objects + one nft_trans_chain
object, deactivate the rules + the chain and then defer the freeing to the nft destroy workqueue. We'd
still need to keep the synchronize_rcu path as a fallback to handle -ENOMEM corner cases though.
(CVE-2024-56655)

Solution

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

Plugin Details

Severity: Medium

ID: 470823

Version: Revision 1.6

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.18

Vendor

Vendor Severity: MEDIUM

CVSS v2

Risk Factor: Medium

Base Score: 4.6

Temporal Score: 3.4

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

CVSS Score Source: CVE-2024-56655

CVSS v3

Risk Factor: Medium

Base Score: 5.5

Temporal Score: 4.8

Vector: CVSS:3.0/AV:L/AC:L/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: 12/27/2024

Reference Information

CVE: CVE-2024-56655

Detections

Analytics