Google: sys-kernel/csql-kernel-6_1, sys-kernel/tpusev-kernel-6_6: security update to 18613.534.62

medium Tenable Self-Hosted Container Security Plugin ID 472314

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: bpf: Forget ranges when refining tnum
after JSET Syzbot reported a kernel warning due to a range invariant violation on the following BPF
program. 0: call bpf_get_netns_cookie 1: if r0 == 0 goto <exit> 2: if r0 & Oxffffffff goto <exit> The
issue is on the path where we fall through both jumps. That path is unreachable at runtime: after insn 1,
we know r0 != 0, but with the sign extension on the jset, we would only fallthrough insn 2 if r0 == 0.
Unfortunately, is_branch_taken() isn't currently able to figure this out, so the verifier walks all
branches. The verifier then refines the register bounds using the second condition and we end up with
inconsistent bounds on this unreachable path: 1: if r0 == 0 goto <exit> r0: u64=[0x1, 0xffffffffffffffff]
var_off=(0, 0xffffffffffffffff) 2: if r0 & 0xffffffff goto <exit> r0 before reg_bounds_sync: u64=[0x1,
0xffffffffffffffff] var_off=(0, 0) r0 after reg_bounds_sync: u64=[0x1, 0] var_off=(0, 0) Improving the
range refinement for JSET to cover all cases is tricky. We also don't expect many users to rely on JSET
given LLVM doesn't generate those instructions. So instead of improving the range refinement for JSETs,
Eduard suggested we forget the ranges whenever we're narrowing tnums after a JSET. This patch implements
that approach. (CVE-2025-39748)

Solution

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

Plugin Details

Severity: Medium

ID: 472314

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/3/2026

Updated: 10/3/2026

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.52

Vendor

Vendor Severity: LOW

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-2025-39748

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: 9/11/2025

Reference Information

CVE: CVE-2025-39748

Detections

Analytics