CentOS Linux 8.4 [TuxCare] 安全更新:bpftool / kernel / kernel-core / kernel-cross-headers / 等多个漏洞 (CENTOS8.4:CLSA-2026:1782145985)

high Nessus 插件 ID 360976

简介

CentOS Linux 主机缺少一个或多个安全更新。

描述

CentOS Linux 8.4 主机上存在安装的程序包,该程序包受到 TuxCare CENTOS8.4:CLSA-2026:2026:1782145985公告中提及的多个漏洞的影响。

- Linux 内核 CIFS 实现版本 4.9.0 容易受到目录条目列表中相对路径注入的影响。(CVE-2019-10220)

- 在 Linux 内核 5.3.2 及其之前版本的 drivers/infiniband/hw/cxgb4/mem.c 的 write_tpt_entry 中发现问题。cxgb4 驱动程序直接从堆栈变量中调用 dma_map_single(DMA 函数)。
攻击者可利用此问题触发拒绝服务,如果在此堆栈/DMA 交互具有安全相关性的架构上使用此驱动程序,该漏洞可遭恶意利用。(CVE-2019-17075)

- Linux 内核 4.20.5 及其之前版本的 KVM 实现中存在释放后使用。(CVE-2019-7221)

- 此漏洞允许本地攻击者提升对 Linux 内核 5.14-rc3 的受影响装置的特权。要利用此漏洞,攻击者必须首先具备在目标系统上执行低权限代码的能力。处理 eBPF 程序时存在特定缺陷。造成此问题的原因是缺少对用户提供的 eBPF 程序的正确验证,这可导致类型混淆情形。攻击者可利用此漏洞,在内核的上下文中提升特权和执行任意代码。此漏洞之前为 ZDI-CAN-14689。(CVE-2021-34866)

- 已修复 Linux 内核中的下列漏洞:kyber: fix out of bounds access when preempted __blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and passes the hctx to
->bio_merge(). kyber_bio_merge() then gets the ctx for the current CPU again and uses that to get the corresponding Kyber context in the passed hctx. However, the thread may be preempted between the two calls to blk_mq_get_ctx(), and the ctx returned the second time may no longer correspond to the passed hctx.
This works accidentally most of the time, but it can cause us to read garbage if the second ctx came from an hctx with more ctx's than the first one (i.e., if ctx->index_hw[hctx->type] > hctx->nr_ctx). This manifested as this UBSAN array index out of bounds error reported by Jakub: UBSAN: array-index-out-of-bounds in ../kernel/locking/qspinlock.c:130:9 index 13106 is out of range for type 'long unsigned int [128]' Call Trace: dump_stack+0xa4/0xe5 ubsan_epilogue+0x5/0x40
__ubsan_handle_out_of_bounds.cold.13+0x2a/0x34 queued_spin_lock_slowpath+0x476/0x480 do_raw_spin_lock+0x1c2/0x1d0 kyber_bio_merge+0x112/0x180 blk_mq_submit_bio+0x1f5/0x1100 submit_bio_noacct+0x7b0/0x870 submit_bio+0xc2/0x3a0 btrfs_map_bio+0x4f0/0x9d0 btrfs_submit_data_bio+0x24e/0x310 submit_one_bio+0x7f/0xb0 submit_extent_page+0xc4/0x440
__extent_writepage_io+0x2b8/0x5e0 __extent_writepage+0x28d/0x6e0 extent_write_cache_pages+0x4d7/0x7a0 extent_writepages+0xa2/0x110 do_writepages+0x8f/0x180 __writeback_single_inode+0x99/0x7f0 writeback_sb_inodes+0x34e/0x790 __writeback_inodes_wb+0x9e/0x120 wb_writeback+0x4d2/0x660 wb_workfn+0x64d/0xa10 process_one_work+0x53a/0xa80 worker_thread+0x69/0x5b0 kthread+0x20b/0x240 ret_from_fork+0x1f/0x30 Only Kyber uses the hctx, so fix it by passing the request_queue to ->bio_merge() instead. BFQ and mq-deadline just use that, and Kyber can map the queues itself to avoid the mismatch.
(CVE-2021-46984)

请注意,Nessus 尚未测试这些问题,而是只依据应用程序自我报告的版本号进行判断。

解决方案

根据 TuxCare 公告 CENTOS8.4:CLSA-2026:1782145985 中的指南更新受影响的程序包。

另见

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

http://www.nessus.org/u?899db72c

插件详情

严重性: High

ID: 360976

文件名: tuxcare_centos_8.4_CLSA-2026-1782145985.nasl

版本: 1.1

类型: Local

代理: unix

发布时间: 2026/10/1

最近更新时间: 2026/10/1

支持的传感器: Continuous Assessment, Nessus Agent, Tenable Cloud Security, Tenable Self-Hosted Container Security, Nessus

风险信息

VPR

风险因素: High

分数: 7.6

百分位: 98.25

Vendor

Vendor Severity: Important

CVSS v2

风险因素: High

基本分数: 9.3

时间分数: 7.3

矢量: CVSS2#AV:N/AC:M/Au:N/C:C/I:C/A:C

CVSS 分数来源: CVE-2019-10220

CVSS v3

风险因素: High

基本分数: 8.8

时间分数: 7.9

矢量: CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

时间矢量: CVSS:3.0/E:P/RL:O/RC:C

CVSS 分数来源: CVE-2022-3640

漏洞信息

必需的 KB 项: Host/OS/extended-third-party, Host/local_checks_enabled, Host/CentOS/release, Host/CentOS/rpm-list

可利用: true

易利用性: Exploits are available

补丁发布日期: 2026/6/22

漏洞发布日期: 2019/2/7

参考资料信息

CVE: CVE-2019-10220, CVE-2019-17075, CVE-2019-7221, CVE-2021-34866, CVE-2021-46984, CVE-2021-47063, CVE-2021-47101, CVE-2021-47138, CVE-2021-47226, CVE-2021-47255, CVE-2021-47277, CVE-2021-47506, CVE-2021-47517, CVE-2021-47566, CVE-2022-3640, CVE-2022-49022, CVE-2022-49696, CVE-2022-50051, CVE-2022-50258, CVE-2023-28410, CVE-2023-39189, CVE-2023-53600, CVE-2023-53827, CVE-2023-53833, CVE-2024-58240, CVE-2025-38004, CVE-2025-39689, CVE-2025-40170, CVE-2025-40259, CVE-2025-68366, CVE-2025-68724, CVE-2025-71082, CVE-2025-71091, CVE-2025-71238, CVE-2026-22984, CVE-2026-23099, CVE-2026-23191, CVE-2026-23209, CVE-2026-23243, CVE-2026-23392, CVE-2026-23397, CVE-2026-23448, CVE-2026-23455, CVE-2026-31402, CVE-2026-31405, CVE-2026-31408, CVE-2026-31452, CVE-2026-31500, CVE-2026-31532, CVE-2026-31581, CVE-2026-31586, CVE-2026-31663, CVE-2026-31669, CVE-2026-31685, CVE-2026-43020, CVE-2026-43027, CVE-2026-43051, CVE-2026-43052, CVE-2026-43110, CVE-2026-43190, CVE-2026-43370, CVE-2026-43427

CLSA: 2026:1782145985