Google: sys-kernel/lakitu-kernel-6_1, sys-kernel/lakitu-kernel-6_6: security update to 18613.75.91

medium Tenable Cloud Security Plugin ID 465691

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: support non-r10 register
spill/fill to/from stack in precision tracking Use instruction (jump) history to record instructions that
performed register spill/fill to/from stack, regardless if this was done through read-only r10 register,
or any other register after copying r10 into it *and* potentially adjusting offset. To make this work
reliably, we push extra per-instruction flags into instruction history, encoding stack slot index (spi)
and stack frame number in extra 10 bit flags we take away from prev_idx in instruction history. We don't
touch idx field for maximum performance, as it's checked most frequently during backtracking. This change
removes basically the last remaining practical limitation of precision backtracking logic in BPF verifier.
It fixes known deficiencies, but also opens up new opportunities to reduce number of verified states,
explored in the subsequent patches. There are only three differences in selftests' BPF object files
according to veristat, all in the positive direction (less states). File Program Insns (A) Insns (B) Insns
(DIFF) States (A) States (B) States (DIFF) -------------------------------------- ------------- ---------
--------- ------------- ---------- ---------- ------------- test_cls_redirect_dynptr.bpf.linked3.o
cls_redirect 2987 2864 -123 (-4.12%) 240 231 -9 (-3.75%) xdp_synproxy_kern.bpf.linked3.o syncookie_tc
82848 82661 -187 (-0.23%) 5107 5073 -34 (-0.67%) xdp_synproxy_kern.bpf.linked3.o syncookie_xdp 85116 84964
-152 (-0.18%) 5162 5130 -32 (-0.62%) Note, I avoided renaming jmp_history to more generic insn_hist to
minimize number of lines changed and potential merge conflicts between bpf and bpf-next trees. Notice also
cur_hist_entry pointer reset to NULL at the beginning of instruction verification loop. This pointer
avoids the problem of relying on last jump history entry's insn_idx to determine whether we already have
entry for current instruction or not. It can happen that we added jump history entry because current
instruction is_jmp_point(), but also we need to add instruction flags for stack access. In this case, we
don't want to entries, so we need to reuse last added entry, if it is present. Relying on insn_idx
comparison has the same ambiguity problem as the one that was fixed recently in [0], so we avoid that. [0]
https://patchwork.kernel.org/project/netdevbpf/patch/[email protected]/
(CVE-2023-52920)

Solution

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

Plugin Details

Severity: Medium

ID: 465691

Version: Revision 1.3

Type: Local

Family: Google COS Security Checks

Published: 10/2/2026

Updated: 10/3/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-2023-52920

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: 11/5/2024

Reference Information

CVE: CVE-2023-52920

Detections

Analytics