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

high Tenable Self-Hosted Container Security Plugin ID 468870

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_queue: pin bridge device
while NFQUEUE holds fake dst The br_netfilter fake rtable is embedded in struct net_bridge and is attached
to bridged packets with skb_dst_set_noref(). If such a packet is queued to NFQUEUE, __nf_queue() upgrades
that fake dst with skb_dst_force(). At that point the queued skb can hold a real dst reference after
bridge teardown has started. The problem is not that every bridged packet needs its own dst reference. The
problem is that NFQUEUE can keep the bridge private fake dst alive after unregister begins. Fix this by
keeping the bridge fake dst model unchanged and pinning the bridge master device only while the packet
sits in NFQUEUE. Record the bridge device in nf_queue_entry when the queued skb carries a bridge fake dst,
take a device reference for the queue lifetime, and drop it when the queue entry is freed. Also make sure
queued entries are reaped when that bridge device goes down, and drop the redundant
nf_bridge_info_exists() test from the fake dst detection. This keeps netdev_priv(br->dev) alive until
verdict completion, so the embedded fake rtable and its metrics backing storage cannot be freed out from
under dst_release(). It also avoids the constant refcount bump and avoids using ipv4-specific dst helpers
for IPv6 bridge traffic. (CVE-2026-72255)

Solution

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

Plugin Details

Severity: High

ID: 468870

Version: Revision 1.5

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: Medium

Score: 6.9

Percentile: 96.5

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

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

Reference Information

CVE: CVE-2026-72255

Detections

Analytics