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

medium Tenable Cloud Security Plugin ID 481620

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/kvm: Don't consume async #PF flags
on a kernel #PF in NMI context An async #PF "page not present" event arrives through the #PF vector, and
its reason sits in the per-CPU apf_reason.flags until __kvm_handle_async_pf() reads and clears it. If an
NMI arrives after the event is injected and before the #PF handler reads the flags, and the NMI handler
itself takes a #PF, that fault reads and clears the flags belonging to the #PF it interrupted. It then
finds interrupts disabled in the NMI context it interrupted, and panics: Kernel panic - not syncing: Host
injected async #PF in interrupt disabled region Call Trace: <NMI> panic+0x52/0x60
__kvm_handle_async_pf+0xb0/0xb0 exc_page_fault+0x71/0xb0 asm_exc_page_fault+0x27/0x30 RIP:
0010:__get_user_nocheck_8+0x6/0x20 perf_callchain_user+0x147/0x1a0 get_perf_callchain+0x12d/0x1c0 ...
perf_event_nmi_handler+0x26/0x50 exc_nmi+0xe8/0x110 RIP: 0010:asm_exc_page_fault+0x0/0x30 </NMI> The last
RIP line shows the NMI landing on the first instruction of the #PF entry. perf with user call chains takes
such a fault: the sampling NMI walks the user stack with __get_user(), which faults when a saved frame
pointer is not a valid user address or the walk runs off the top of the stack. The same window exists when
KVM, running as an L1 hypervisor with DELIVERY_AS_PF_VMEXIT, reads the flags itself after a #PF VM-exit.
The NMI entry code saves and restores CR2 for this nesting, but not the async #PF reason. Andy Lutomirski
described the race, with perf as the example, when async #PF delivery was reworked in 2020 [1]. Saving and
clearing the flags across the NMI, next to CR2, was discussed there but not merged. Since that rework,
Linux has stopped setting KVM_ASYNC_PF_SEND_ALWAYS, so the host delivers "page not present" only for user
mode faults and a kernel-mode fault in NMI context (including kernel-mode #MC and #DB) cannot be an async
page fault. In that case, return without touching the flags so that the interrupted handler finds them
intact. Tested on v7.3-rc5 in a 4-vCPU, 2 GiB guest restored from a snapshot whose memory is served on
demand through userfaultfd, so that reading it back takes async #PFs, while every thread samples hardware
cycles with user call chains and points its frame pointer at an unmapped page. Without this patch the
guest panicked as above in 3 of 3 runs. With it, the guest survived 3 of 3 runs of 60 seconds, and the
host counted 148,441 to 153,334 kvm_async_pf_not_present events in the first 20 seconds of each. On
6.18.50 the results were the same: the guest panicked without the patch and survived with it.
(CVE-2026-99178)

Solution

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

See Also

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

Plugin Details

Severity: Medium

ID: 481620

Version: Revision 1.1

Type: Local

Published: 11/20/2026

Updated: 11/20/2026

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.81

Vendor

Vendor Severity: LOW

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-99178

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/28/2026

Reference Information

CVE: CVE-2026-99178