Google: sys-kernel/csql-kernel-6_6, sys-kernel/lakitu-kernel-6_6, sys-kernel/lakitu-nc-kernel-6_6, sys-kernel/lakitu-vgpu-kernel-6_6: security update to 18867.381.132

high Tenable Self-Hosted Container Security Plugin ID 467370

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: netfilter: nf_conntrack_h323: fix OOB
read in decode_choice() In decode_choice(), the boundary check before get_len() uses the variable `len`,
which is still 0 from its initialization at the top of the function: unsigned int type, ext, len = 0; ...
if (ext || (son->attr & OPEN)) { BYTE_ALIGN(bs); if (nf_h323_error_boundary(bs, len, 0)) /* len is 0 here
*/ return H323_ERROR_BOUND; len = get_len(bs); /* OOB read */ When the bitstream is exactly consumed
(bs->cur == bs->end), the check nf_h323_error_boundary(bs, 0, 0) evaluates to (bs->cur + 0 > bs->end),
which is false. The subsequent get_len() call then dereferences *bs->cur++, reading 1 byte past the end of
the buffer. If that byte has bit 7 set, get_len() reads a second byte as well. This can be triggered
remotely by sending a crafted Q.931 SETUP message with a User-User Information Element containing exactly
2 bytes of PER-encoded data ({0x08, 0x00}) to port 1720 through a firewall with the nf_conntrack_h323
helper active. The decoder fully consumes the PER buffer before reaching this code path, resulting in a
1-2 byte heap-buffer-overflow read confirmed by AddressSanitizer. Fix this by checking for 2 bytes (the
maximum that get_len() may read) instead of the uninitialized `len`. This matches the pattern used at
every other get_len() call site in the same file, where the caller checks for 2 bytes of available data
before calling get_len(). (CVE-2026-43233)

Solution

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

Plugin Details

Severity: High

ID: 467370

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/2/2026

Updated: 10/2/2026

Risk Information

VPR

Risk Factor: Low

Score: 3.5

Percentile: 52.01

Vendor

Vendor Severity: LOW

CVSS v2

Risk Factor: High

Base Score: 8.5

Temporal Score: 6.3

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

CVSS Score Source: CVE-2026-43233

CVSS v3

Risk Factor: High

Base Score: 8.2

Temporal Score: 7.1

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

Reference Information

CVE: CVE-2026-43233

Detections

Analytics