Detections
Analytics

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

high Tenable Self-Hosted Container Security Plugin ID 472519

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: dm thin metadata: fix metadata
 snapshot consistency on commit failure __reserve_metadata_snap() and __release_metadata_snap() modify the
 superblock's held_root directly in the block_manager's buffer. If the subsequent metadata commit fails,
 the held_root gets flushed to disk through the abort_transaction path, resulting in inconsistent metadata.
 Reproducer 1: __reserve_metadata_snap() 1. Create a 2 MiB metadata device and make the region after the
 14th block inaccessible, to trigger metadata commit failure in the subsequent reserve_metadata_snap
 operation. The 14th block will be the shadow destination for the index block. dmsetup create tmeta --table
 "0 112 linear /dev/sdc 0 112 3984 error" 2. Create a 16 MiB thin-pool dmsetup create tdata --table "0
 32768 zero" dd if=/dev/zero of=/dev/mapper/tmeta bs=4k count=1 dmsetup create tpool --table "0 32768 thin-
 pool /dev/mapper/tmeta \ /dev/mapper/tdata 128 0 1 skip_block_zeroing" 3. Take a metadata snapshot to
 trigger metadata commit failure and transaction abort. However, the held_root is written to disk, breaking
 metadata consistency. dmsetup message tpool 0 "reserve_metadata_snap" thin_check v1.2.2 result: Bad
 reference count for metadata block 6. Expected 2, but space map contains 1. Bad reference count for
 metadata block 7. Expected 2, but space map contains 1. Bad reference count for metadata block 13.
 Expected 1, but space map contains 0. Reproducer 2: __release_metadata_snap() 1. Create a 2 MiB metadata
 device and make the region after the 16th block inaccessible, to trigger metadata commit failure in the
 subsequent release_metadata_snap operation. The 16th block will be the shadow destination for the index
 block. dmsetup create tmeta --table "0 128 linear /dev/sdc 0 128 3968 error" 2. Create a 16 MiB thin-pool
 dmsetup create tdata --table "0 32768 zero" dd if=/dev/zero of=/dev/mapper/tmeta bs=4k count=1 dmsetup
 create tpool --table "0 32768 thin-pool /dev/mapper/tmeta \ /dev/mapper/tdata 128 0 1 skip_block_zeroing"
 3. Reserve then release the metadata snapshot, to trigger metadata commit failure and transaction abort.
 The held_root gets removed from the on-disk superblock, causing inconsistent metadata. dmsetup message
 tpool 0 "reserve_metadata_snap" dmsetup message tpool 0 "release_metadata_snap" thin_check v1.2.2 result:
 Bad reference count for metadata block 6. Expected 1, but space map contains 2. Bad reference count for
 metadata block 7. Expected 1, but space map contains 2. 1 metadata blocks have leaked. Fix by deferring
 the held_root update to commit time. Additionally, move the existing-snapshot check in
 __reserve_metadata_snap before the shadow operation to avoid unnecessary work. In __release_metadata_snap,
 clear pmd->held_root before btree deletion so partial failure leaks blocks rather than leaving a stale
 reference, and unlock the snapshot block before decrementing its refcount. (CVE-2026-72108)

Solution

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

See Also

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

Plugin Details

Severity: High

ID: 472519

Version: Revision 1.1

Type: Local

Published: 10/3/2026

Updated: 10/3/2026

Risk Information

VPR

Risk Factor: Medium

Score: 4.9

Percentile: 58.29

Vendor

Vendor Severity: LOW

CVSS v2

Risk Factor: Medium

Base Score: 6.8

Temporal Score: 5

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

CVSS Score Source: CVE-2026-72108

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

Reference Information

CVE: CVE-2026-72108