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 19999.44.106

high Tenable Self-Hosted Container Security Plugin ID 475445

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: ipv6: sr: restore network header
before routing and forwarding ipv6_srh_rcv() runs with skb->data at the Segment Routing Header (SRH) while
skb_network_header() points at the IPv6 header. When segments_left > 0, ipv6_srh_rcv() previously restored
the skb->data position by pushing sizeof(struct ipv6hdr), assuming the SRH immediately followed the fixed
IPv6 header. If another extension header (such as a Hop-by-Hop options header) precedes the SRH,
skb_network_offset() remained negative. This led to two problems: 1. During ip6_route_input(),
fib6_rules_early_flow_dissect() invokes __skb_flow_dissect() which passes the negative
skb_network_offset() to flow dissection, breaking BPF and C flow dissector logic. 2. If forwarded via
ip6_forward() or redirected via act_mirred, downstream handlers (like sch_fragment() or neighbour output)
pass the negative offset as an unsigned length, triggering OOB memcpy or buffer overflows. Fix this by
pushing -skb_network_offset(skb) before routing, ensuring skb_network_offset(skb) is 0 for route lookup /
flow dissection as well as downstream forwarding. On the loopback path, pull skb_transport_offset(skb) to
restore skb->data to the SRH before looping back. (CVE-2026-98096)

Solution

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

Plugin Details

Severity: High

ID: 475445

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/16/2026

Updated: 10/16/2026

Risk Information

VPR

Risk Factor: Medium

Score: 4.3

Percentile: 53.43

Vendor

Vendor Severity: HIGH

CVSS v2

Risk Factor: High

Base Score: 7.1

Temporal Score: 5.3

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

CVSS Score Source: CVE-2026-98096

CVSS v3

Risk Factor: High

Base Score: 7.4

Temporal Score: 6.4

Vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/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/25/2026

Reference Information

CVE: CVE-2026-98096

Detections

Analytics