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

high Tenable Cloud Security Plugin ID 475383

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: io_uring/rw: end write accounting from
->ki_complete Commit b000145e9907 moved both the fsnotify calls and the write accounting out of the kiocb
completion handler and into the io_req_rw_complete() task_work. However, only the fsnotify part actually
needed to move as it may sleep. Ending the write accounting is just a percpu_up_read() on the superblock
writers sem. Deferring it is a problem, because it makes dropping SB_FREEZE_WRITE protection depend on the
ring owner getting to running task_work. But the task may be blocked in freeze_super(), causing it to
never get to that: task io-wq worker --------------------------------------------------------------
io_write() io_kiocb_start_write() (takes sb_writers, hidden from lockdep by __sb_writers_release)
write_iter() -> -EIOCBQUEUED ioctl(FS_IOC_SHUTDOWN) bdev_freeze() freeze_super() percpu_down_write() <-
waits for the reader above io_write() kiocb_start_write() percpu_down_read() <- queued behind the writer
<bio completes> io_complete_rw() queues io_req_rw_complete() <- never runs, task is in D state End the
write from io_complete_rw() instead, and leave only the fsnotify calls in task_work. (CVE-2026-97619)

Solution

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

Plugin Details

Severity: High

ID: 475383

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/16/2026

Updated: 10/16/2026

Risk Information

VPR

Risk Factor: Medium

Score: 4.3

Percentile: 53.43

Vendor

Vendor Severity: LOW

CVSS v2

Risk Factor: Medium

Base Score: 6.6

Temporal Score: 4.9

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

CVSS Score Source: CVE-2026-97619

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: 9/25/2026

Reference Information

CVE: CVE-2026-97619

Detections

Analytics