CentOS Linux 8 [TuxCare] Security Update: bpftool / kernel / kernel-core / kernel-cross-headers / etc Multiple Vulnerabilities (CENTOS-STREAM8:CLSA-2026:1794913125)

high Nessus Plugin ID 381966

Synopsis

The CentOS Linux host is missing one or more security updates.

Description

The CentOS Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS-STREAM8:CLSA-2026:1794913125 advisory.

- In the Linux kernel, the following vulnerability has been resolved: ceph: bound copied dentry name length in NFS export get_name ceph_get_name() copies the MDS-supplied name into the caller's NAME_MAX-sized buffer with memcpy(name, rinfo->dname, rinfo->dname_len) and then writes name[rinfo->dname_len] = 0, without checking dname_len against NAME_MAX. A malicious or buggy MDS that returns a LOOKUPNAME reply with dname_len > NAME_MAX overflows the buffer. __get_snap_name() copies rde->name / rde->name_len the same unchecked way. Impact: a malicious or compromised Ceph MDS overflows the NAME_MAX name buffer in a client's NFS-export get_name path, a slab out-of-bounds write reported by KASAN. Reachable when a CephFS mount is re-exported over NFS. Add ceph_export_copy_name(), which rejects lengths above NAME_MAX with
-ENAMETOOLONG before the copy, and use it in both ceph_get_name() and __get_snap_name(). (CVE-2026-89652)

- In the Linux kernel, the following vulnerability has been resolved: cgroup/cpuset: Don't access cpuset_cgrp_subsys.root in is_in_v2_mode() After seeing the patch [1] to guard is_in_v2_mode() with RCU, it makes me realize that is_in_v2_mode() may be called in a context where a new cgroup filesystem is being rebound with stale cpuset_cgrp_subsys.root pointer. Avoid this potential UaF situation by adding a new cpuset_v2_mode flag which is set when the cpuset_v2_mode mount option is used. This flag is written into only when cpuset_bind() is being called with a stable cpuset_cgrp_subsys.root value. The is_in_v2_mode() helper is modified to read the new cpuset_v2_mode flag instead of accessing cpuset_cgrp_subsys.root directly. [1] https://lore.kernel.org/lkml/[email protected] (CVE-2026-98972)

- In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: use check_add_overflow for shader size+offset bound vmw_shader_define() validates the user-supplied shader window against its backing buffer with (u64)buffer->tbo.base.size < (u64)size + (u64)offset drm_vmw_shader_create_arg::offset is
__u64 in the uapi; when it is near U64_MAX the unsigned addition wraps and the resulting tiny value passes the check. The unbounded offset is then stored in res->guest_memory_offset and forwarded to host SVGA shader-create commands. Use check_add_overflow() to detect the wrap and compare the resulting endpoint against the buffer size. (CVE-2026-80887)

- In the Linux kernel, the following vulnerability has been resolved: libceph: guard missing CRUSH type name lookup Localized read selection can walk a parent bucket whose name exists in the CRUSH map while its type has no matching entry in type_names. get_immediate_parent() then dereferences a NULL type_cn and passes an invalid pointer into strcmp(), causing a null-ptr-deref. Skip such malformed parent buckets unless both the bucket name and type name metadata are present. This keeps malformed hierarchy data from crashing locality lookup and safely falls back to not local. [ idryomov: add WARN_ON_ONCE ] (CVE-2026-68157)

- In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: defer link RX stats percpu free to RCU sta_remove_link() frees a removed MLO link's RX stats percpu buffer right away, but defers only the link container to RCU: sta_info_free_link(&alloc->info); kfree_rcu(alloc, rcu_head); The RX fast path reads link_sta under rcu_read_lock and writes the percpu stats. A reader that resolved link_sta before the removal keeps the pointer. The container stays alive from the kfree_rcu, so the read still works. But the percpu block it points to is already freed. This needs uses_rss. That is when pcpu_rx_stats exists. The full STA teardown frees the deflink stats only after synchronize_net(). The link removal path had no such barrier. The race is hard to win in practice, but the free should still wait for RCU. Free the link together with its data from a single RCU callback, so the percpu block is reclaimed only after readers drain. (CVE-2026-68409)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Solution

Update the affected packages based on the guidance in TuxCare advisory CENTOS-STREAM8:CLSA-2026:1794913125.

See Also

https://cve.tuxcare.com/els/releases/CLSA-2026:1794913125

http://www.nessus.org/u?610d2bb5

Plugin Details

Severity: High

ID: 381966

File Name: tuxcare_centos_8_CLSA-2026-1794913125.nasl

Version: 1.1

Type: Local

Agent: unix

Published: 11/17/2026

Updated: 11/17/2026

Supported Sensors: Nessus Agent, Continuous Assessment, Nessus

Risk Information

VPR

Risk Factor: High

Score: 7.8

Percentile: 99.33

Vendor

Vendor Severity: Important

CVSS v2

Risk Factor: Medium

Base Score: 6.8

Temporal Score: 5.3

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

CVSS Score Source: CVE-2026-63957

CVSS v3

Risk Factor: High

Base Score: 7.8

Temporal Score: 7

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:P/RL:O/RC:C

Vulnerability Information

Required KB Items: Host/local_checks_enabled, Host/CentOS/release, Host/CentOS/rpm-list, Host/OS/extended-third-party

Exploit Available: true

Exploit Ease: Exploits are available

Patch Publication Date: 11/17/2026

Vulnerability Publication Date: 5/13/2025

Reference Information

CVE: CVE-2025-37928, CVE-2025-39973, CVE-2025-40297, CVE-2025-68822, CVE-2026-23050, CVE-2026-31494, CVE-2026-31518, CVE-2026-31662, CVE-2026-43042, CVE-2026-43451, CVE-2026-43469, CVE-2026-45894, CVE-2026-45942, CVE-2026-46184, CVE-2026-46195, CVE-2026-63806, CVE-2026-63898, CVE-2026-63899, CVE-2026-63901, CVE-2026-63903, CVE-2026-63904, CVE-2026-63913, CVE-2026-63919, CVE-2026-63928, CVE-2026-63956, CVE-2026-63957, CVE-2026-63962, CVE-2026-63983, CVE-2026-64109, CVE-2026-64487, CVE-2026-64530, CVE-2026-64549, CVE-2026-64551, CVE-2026-64562, CVE-2026-68082, CVE-2026-68117, CVE-2026-68131, CVE-2026-68136, CVE-2026-68157, CVE-2026-68159, CVE-2026-68278, CVE-2026-68300, CVE-2026-68343, CVE-2026-68399, CVE-2026-68409, CVE-2026-68476, CVE-2026-72020, CVE-2026-72049, CVE-2026-72052, CVE-2026-72053, CVE-2026-72061, CVE-2026-72135, CVE-2026-72243, CVE-2026-72251, CVE-2026-72284, CVE-2026-72301, CVE-2026-72338, CVE-2026-72339, CVE-2026-72502, CVE-2026-74443, CVE-2026-74488, CVE-2026-74512, CVE-2026-74586, CVE-2026-74598, CVE-2026-74616, CVE-2026-74743, CVE-2026-80586, CVE-2026-80767, CVE-2026-80782, CVE-2026-80788, CVE-2026-80829, CVE-2026-80852, CVE-2026-80887, CVE-2026-80977, CVE-2026-80989, CVE-2026-89526, CVE-2026-89551, CVE-2026-89563, CVE-2026-89631, CVE-2026-89643, CVE-2026-89650, CVE-2026-89652, CVE-2026-89662, CVE-2026-89697, CVE-2026-89783, CVE-2026-89846, CVE-2026-90049, CVE-2026-90104, CVE-2026-90151, CVE-2026-90307, CVE-2026-93117, CVE-2026-93288, CVE-2026-93787, CVE-2026-97528, CVE-2026-97531, CVE-2026-97541, CVE-2026-98111, CVE-2026-98176, CVE-2026-98186, CVE-2026-98197, CVE-2026-98204, CVE-2026-98205, CVE-2026-98241, CVE-2026-98252, CVE-2026-98262, CVE-2026-98276, CVE-2026-98299, CVE-2026-98314, CVE-2026-98331, CVE-2026-98347, CVE-2026-98358, CVE-2026-98380, CVE-2026-98429, CVE-2026-98550, CVE-2026-98709, CVE-2026-98738, CVE-2026-98741, CVE-2026-98827, CVE-2026-98857, CVE-2026-98859, CVE-2026-98972, CVE-2026-99156, CVE-2026-99233, CVE-2026-99281, CVE-2026-99288

CLSA: 2026:1794913125