Google: sys-kernel/csql-kernel-6_12, sys-kernel/csql-kernel-6_6: security update to 19216.104.72

high Tenable Self-Hosted Container Security Plugin ID 472510

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: btrfs: ensure no dirty metadata is
written back for an fs with errors [BUG] During development of a minor feature (make sure all
btrfs_bio::end_io() is called in task context), I noticed a crash in generic/388, where metadata writes
triggered new works after btrfs_stop_all_workers(). It turns out that it can even happen without any code
modification, just using RAID5 for metadata and the same workload from generic/388 is going to trigger the
use-after-free. [CAUSE] If btrfs hits an error, the fs is marked as error, no new transaction is allowed
thus metadata is in a frozen state. But there are some metadata modifications before that error, and they
are still in the btree inode page cache. Since there will be no real transaction commit, all those dirty
folios are just kept as is in the page cache, and they can not be invalidated by invalidate_inode_pages2()
call inside close_ctree(), because they are dirty. And finally after btrfs_stop_all_workers(), we call
iput() on btree inode, which triggers writeback of those dirty metadata. And if the fs is using RAID56
metadata, this will trigger RMW and queue new works into rmw_workers, which is already stopped, causing
warning from queue_work() and use-after-free. [FIX] Add a special handling for write_one_eb(), that if the
fs is already in an error state, immediately mark the bbio as failure, instead of really submitting them.
Then during close_ctree(), iput() will just discard all those dirty tree blocks without really writing
them back, thus no more new jobs for already stopped-and-freed workqueues. The extra discard in
write_one_eb() also acts as an extra safenet. E.g. the transaction abort is triggered by some extent/free
space tree corruptions, and since extent/free space tree is already corrupted some tree blocks may be
allocated where they shouldn't be (overwriting existing tree blocks). In that case writing them back will
further corrupting the fs. (CVE-2025-40303)

Solution

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

Plugin Details

Severity: High

ID: 472510

Version: Revision 1.1

Type: Local

Family: Google COS Security Checks

Published: 10/3/2026

Updated: 10/3/2026

Risk Information

VPR

Risk Factor: Medium

Score: 4.9

Percentile: 58.12

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-2025-40303

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: 12/8/2025

Reference Information

CVE: CVE-2025-40303

Detections

Analytics