Google: sys-kernel/lakitu-kernel-6_1: security update to 17872.0.0

medium Tenable Self-Hosted Container Security Plugin ID 451660

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, cpumap: Handle skb as well when
clean up ptr_ring The following warning was reported when running xdp_redirect_cpu with both skb-mode and
stress-mode enabled: ------------[ cut here ]------------ Incorrect XDP memory type (-2128176192) usage
WARNING: CPU: 7 PID: 1442 at net/core/xdp.c:405 Modules linked in: CPU: 7 PID: 1442 Comm: kworker/7:0
Tainted: G 6.5.0-rc2+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Workqueue: events
__cpu_map_entry_free RIP: 0010:__xdp_return+0x1e4/0x4a0 ...... Call Trace: <TASK> ? show_regs+0x65/0x70 ?
__warn+0xa5/0x240 ? __xdp_return+0x1e4/0x4a0 ...... xdp_return_frame+0x4d/0x150
__cpu_map_entry_free+0xf9/0x230 process_one_work+0x6b0/0xb80 worker_thread+0x96/0x720 kthread+0x1a5/0x1f0
ret_from_fork+0x3a/0x70 ret_from_fork_asm+0x1b/0x30 </TASK> The reason for the warning is twofold. One is
due to the kthread cpu_map_kthread_run() is stopped prematurely. Another one is __cpu_map_ring_cleanup()
doesn't handle skb mode and treats skbs in ptr_ring as XDP frames. Prematurely-stopped kthread will be
fixed by the preceding patch and ptr_ring will be empty when __cpu_map_ring_cleanup() is called. But as
the comments in __cpu_map_ring_cleanup() said, handling and freeing skbs in ptr_ring as well to "catch any
broken behaviour gracefully". (CVE-2023-53660)

Solution

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

Plugin Details

Severity: Medium

ID: 451660

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/1/2026

Updated: 10/1/2026

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.25

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-2023-53660

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/6/2023

Reference Information

CVE: CVE-2023-53660

Detections

Analytics