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.126

medium Tenable Self-Hosted Container Security Plugin ID 475267

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: x86/kprobes: Fix crash when probing CS
CALL instructions When using eBPF to probe CS CALL instructions within a function, a crash can be
triggered. The eBPF tool probes offset 257 of the __hrtimer_run_queues() function:
<__hrtimer_run_queues+249>: nopl 0x0(%rax,%rax,1) <__hrtimer_run_queues+254>: mov %r14,%rdi
<__hrtimer_run_queues+257>: cs call <__x86_indirect_thunk_r12> <__hrtimer_run_queues+263>: mov %eax,%r12d
<__hrtimer_run_queues+266>: xchg %ax,%ax <__hrtimer_run_queues+268>: mov %r13,%rdi Which triggers this
crash: BUG: unable to handle page fault for address: 00000000000f41c9 #PF: supervisor write access in
kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: 0002 [#1] SMP NOPTI CPU: 1 PID: 0
Comm: swapper/1 Kdump: loaded Tainted: P RIP: 0010:__hrtimer_run_queues+0x106/0x230 Note that
__hrtimer_run_queues+0x106 is __hrtimer_run_queues+262, which is at the 6th byte of the above CS CALL
instruction. Since the CS CALL instruction occupies 6 bytes, the exception occurred in the middle of that
call instruction. The root cause is that when using eBPF tools to probe in the middle of a function, a
kprobe with INT3 is used as the underlying implementation. During single-step emulation of the original
CALL instruction, int3_emulate_call() assumes that the probed CALL instruction is 5 bytes long. However,
the actual CS-prefixed CALL instruction occupies 6 bytes, so it constructs an incorrect exception return
address. When the CPU returns from the kprobe handler, the next instruction to be executed is at the
address of the last byte of that CS CALL instruction. Coincidentally, starting from that address, the CPU
fetches and decodes a completely different instruction, which ultimately triggers a kernel crash. Fix the
issue by using the actual instruction length obtained from the instruction decoder when constructing the
exception return address, rather than relying on the hardcoded CALL_INSN_SIZE macro. [ mingo: Refined the
changelog ] (CVE-2026-98273)

Solution

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

Plugin Details

Severity: Medium

ID: 475267

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/16/2026

Updated: 10/16/2026

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.73

Vendor

Vendor Severity: LOW

CVSS v2

Risk Factor: Medium

Base Score: 4.9

Temporal Score: 3.6

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

CVSS Score Source: CVE-2026-98273

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: 10/6/2026

Reference Information

CVE: CVE-2026-98273

Detections

Analytics