Google: sys-kernel/cchost-kernel-6_12, sys-kernel/csql-kernel-6_12, sys-kernel/lakitu-kernel-6_12, sys-kernel/lakitu-nc-kernel-6_12: security update to 19506.299.82

medium Tenable Cloud Security Plugin ID 469463

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: mm: do file ownership checks with the
proper mount idmap Ever since idmapped mounts were introduced, inode ownership checks (for side-channel
protection) in mincore() and madvise(MADV_PAGEOUT) were done against the nop_mnt_idmap, which completely
ignores the file's mount's idmap. This results in odd edgecases like: 1) mount/bind-mount with an idmap
userA:userB:1 2) userB runs an owner_or_capable() check on file that is owned by userA on-disk/in-memory,
but owned by userB after idmap translation 3) owner_or_capable() mysteriously fails as the correct idmap
wasn't supplied In the case of mincore/madvise MADV_PAGEOUT, this is usually benign, because
file_permission(file, MAY_WRITE) will probably succeed, as it uses the proper idmap internally, but it
does not need to be the case on e.g a 0444 file where even the owner itself doesn't have permissions to
write to it. Since this is clearly not trivial to get right, introduce a file_owner_or_capable() that can
carry the correct semantics, and switch the various users in mm to it. The issue was found by manual code
inspection & an off-list discussion with Jan Kara. (CVE-2026-64294)

Solution

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

Plugin Details

Severity: Medium

ID: 469463

Version: Revision 1.3

Type: Local

Family: Google COS Security Checks

Published: 10/3/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.58

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-2026-64294

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: 7/23/2026

Reference Information

CVE: CVE-2026-64294

Detections

Analytics