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

high Tenable Self-Hosted Container Security Plugin ID 466434

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/hugetlb: fix swap entry corruption
when clearing uffd-wp at fork() copy_hugetlb_page_range() clears the uffd-wp bit of migration and hwpoison
entries with huge_pte_clear_uffd_wp(), which operates on the present-PTE bit position. Swap entries keep
the uffd-wp state elsewhere -- the migration branch reads and sets it with pte_swp_uffd_wp() and
pte_swp_mkuffd_wp() -- and the present-PTE position falls into the swap payload. On x86-64 it lands in the
inverted swap offset, where a naturally-aligned hugetlb PFN always has the affected bit set, so the clear
advances the encoded PFN by two pages. No userfaultfd needs to be involved: the clear is guarded only by
the child VMA not being uffd-wp registered, so a plain fork() with an in-flight hugetlb migration entry
(or a poisoned hugetlb page) corrupts the entry copied into the child. Instrumenting the clear and forking
after MADV_HWPOISON on a 2MB anon hugetlb page shows: offset before=120e00 offset after =120e02 The
fallout is mostly latent: rmap walks match migration entries by folio range and remove_migration_pte()
rebuilds the PTE from the folio, so a within-folio PFN skew heals once migration completes. But any path
that re-encodes the corrupted offset -- e.g. hugetlb_change_protection() rewriting a writable migration
entry via make_readable_migration_entry(swp_offset(entry)) -- propagates it. Migration entries
legitimately carry uffd-wp, so clear it with pte_swp_clear_uffd_wp(), matching copy_nonpresent_pte() and
move_huge_pte(). A hwpoison entry, on the other hand, never carries the uffd-wp bit: it is installed fresh
by make_hwpoison_entry() (try_to_unmap_one() does not preserve uffd-wp on the hwpoison path) and
hugetlb_change_protection() leaves hwpoison entries untouched. There was nothing to clear there, only the
corruption, so drop the clear entirely. (CVE-2026-80893)

Solution

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

Plugin Details

Severity: High

ID: 466434

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/2/2026

Updated: 10/2/2026

Risk Information

VPR

Risk Factor: Medium

Score: 4.9

Percentile: 58.22

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

CVSS v3

Risk Factor: High

Base Score: 7.8

Temporal Score: 6.8

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

Reference Information

CVE: CVE-2026-80893

Detections

Analytics