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

high Tenable Self-Hosted Container Security Plugin ID 480859

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: netfs: clear post-EOF pagecache when
extending a file via write Fix netfs to erase the contents of a hole created after the EOF by an ordinary
write if dirty data has been previously left there by writes through an mmapped region. Neither the
buffered nor the unbuffered/DIO write path clears that stale pagecache. Zero the tail of the folio
straddling the EOF before an extending write. That is the only folio that can hold data written past the
EOF through an mmap, as pages wholly beyond the EOF can't be faulted in. The folio is zeroed rather than
dropped so a concurrent extending write can't lose data. Both write paths downgrade the i_rwsem to shared,
so extending writes can run concurrently and the i_size read by the caller may be stale by the time the
folio is locked. Re-read i_size under the folio lock and clamp the zeroed range up to it, so a racing
write that already put data into the folio isn't clobbered. Wait for any writeback on the folio to finish
before zeroing it so that the pagecache isn't modified while it may still be read by the transport during
transmission. Honour IOCB_NOWAIT by returning -EAGAIN rather than blocking on the folio lock, on
writeback, or in folio_mkclean()'s rmap walk when the folio is mapped. truncate_pagecache() can't be used
here: it must be called with the i_rwsem held exclusively, but these write paths only hold it shared, and
it would block unconditionally, breaking IOCB_NOWAIT. Callers that hold i_rwsem exclusively for the whole
resize (truncate, setattr, fallocate, clone) exclude any genuine concurrent buffered writer, so staleness
can instead be decided from the folio's dirty state, as pagecache_isize_extended() already does for
filesystems that serialise writes against truncate/setattr via a single i_rwsem. Export
netfs_clear_stale_post_isize() helper to handle such case. The helper is required by the CIFS client to
fix generic/363. (CVE-2026-98844)

Solution

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

See Also

https://storage.googleapis.com/cos-oval-vulnerability-feed/cos-129.oval.xml.tar.gz

Plugin Details

Severity: High

ID: 480859

Version: Revision 1.1

Type: Local

Published: 11/19/2026

Updated: 11/19/2026

Risk Information

VPR

Risk Factor: Medium

Score: 4.3

Percentile: 53.7

Vendor

Vendor Severity: LOW

CVSS v2

Risk Factor: High

Base Score: 7.2

Temporal Score: 5.3

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

CVSS Score Source: CVE-2026-98844

CVSS v3

Risk Factor: High

Base Score: 7.1

Temporal Score: 6.2

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

Reference Information

CVE: CVE-2026-98844