CentOS Linux 8.4 [TuxCare] 安全更新：bpftool / kernel / kernel-core / kernel-cross-headers / 等多个漏洞 （CENTOS8.4：CLSA-2024：1707478061）
high Nessus 插件 ID 366965
语言：
简介
CentOS Linux 主机缺少一个或多个安全更新。描述
CentOS Linux 8.4 主机上存在安装的程序包，该程序包受到 TuxCare CENTOS8.4：CLSA-2024：2024：1707478061公告中提及的多个漏洞的影响。- 已修复 Linux 内核中的下列漏洞：RDMA/cma: Ensure rdma_addr_cancel() happens before issuing more requests The FSM can run in a circle allowing rdma_resolve_ip() to be called twice on the same id_priv. While this cannot happen without going through the work, it violates the invariant that the same address resolution background request cannot be active twice. CPU 1 CPU 2 rdma_resolve_addr(): RDMA_CM_IDLE -> RDMA_CM_ADDR_QUERY rdma_resolve_ip(addr_handler) #1 process_one_req(): for #1 addr_handler(): RDMA_CM_ADDR_QUERY -> RDMA_CM_ADDR_BOUND mutex_unlock(&id_priv->handler_mutex); [.. handler still running ..] rdma_resolve_addr():
RDMA_CM_ADDR_BOUND -> RDMA_CM_ADDR_QUERY rdma_resolve_ip(addr_handler) !! two requests are now on the req_list rdma_destroy_id(): destroy_id_handler_unlock(): _destroy_id(): cma_cancel_operation():
rdma_addr_cancel() // process_one_req() self removes it spin_lock_bh(&lock);
cancel_delayed_work(&req->work); if (!list_empty(&req->list)) == true ! rdma_addr_cancel() returns after process_on_req #1 is done kfree(id_priv) process_one_req(): for #2 addr_handler():
mutex_lock(&id_priv->handler_mutex); !! Use after free on id_priv rdma_addr_cancel() expects there to be one req on the list and only cancels the first one. The self-removal behavior of the work only happens after the handler has returned. This yields a situations where the req_list can have two reqs for the same handle but rdma_addr_cancel() only cancels the first one. The second req remains active beyond rdma_destroy_id() and will use-after-free id_priv once it inevitably triggers. Fix this by remembering if the id_priv has called rdma_resolve_ip() and always cancel before calling it again. This ensures the req_list never gets more than one item in it and doesn't cost anything in the normal flow that never uses this strange error path. (CVE-2021-47391)
- 已修复 Linux 内核中的下列漏洞：writeback: avoid use-after-free after removing device When a disk is removed, bdi_unregister gets called to stop further writeback and wait for associated delayed work to complete. However, wb_inode_writeback_end() may schedule bandwidth estimation dwork after this has completed, which can result in the timer attempting to access the just freed bdi_writeback. Fix this by checking if the bdi_writeback is alive, similar to when scheduling writeback work. Since this requires wb->work_lock, and wb_inode_writeback_end() may get called from interrupt, switch wb->work_lock to an irqsafe lock. (CVE-2022-49995)
- 在 Linux 内核 6.4.12 之前的版本中，drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c 中的 amdgpu_cs_wait_all_fences 存在释放后使用屏蔽。(CVE-2023-51042)
- 在 6.4.5 之前的 Linux 内核中，drivers/gpu/drm/drm_atomic.c 在无阻塞原子提交和驱动程序卸载之间有争用条件期间存在释放后使用。(CVE-2023-51043)
- 在 6.6.8 之前的 Linux 内核中发现了一个问题。因 vcc_recvmsg 争用条件，net/atm/ioctl.c 中的 do_vcc_ioctl 存在释放后使用漏洞。(CVE-2023-51780)
请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。
解决方案
根据 TuxCare 公告 CENTOS8.4：CLSA-2024：1707478061 中的指南更新受影响的程序包。另见
插件详情
严重性: High
ID: 366965
文件名: tuxcare_centos_8.4_CLSA-2024-1707478061.nasl
版本: 1.2
类型: Local
代理: unix
发布时间: 2026/10/18
最近更新时间: 2026/10/19
支持的传感器: Nessus Agent, Continuous Assessment, Tenable Cloud Security, Tenable Self-Hosted Container Security, Nessus
风险信息
VPR
风险因素: Critical
分数: 9.6
百分位: 99.95
Vendor
Vendor Severity: Important
CVSS v2
风险因素: High
基本分数: 7.7
时间分数: 6.7
矢量: CVSS2#AV:A/AC:L/Au:S/C:C/I:C/A:C
CVSS 分数来源: CVE-2024-0565
CVSS v3
风险因素: High
基本分数: 7.8
时间分数: 7.5
矢量: CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
时间矢量: CVSS:3.0/E:H/RL:O/RC:C
CVSS 分数来源: CVE-2024-1086
漏洞信息
必需的 KB 项: Host/local_checks_enabled, Host/CentOS/release, Host/CentOS/rpm-list, Host/OS/extended-third-party
可利用: true
易利用性: Exploits are available
补丁发布日期: 2024/2/9
漏洞发布日期: 2021/7/21
CISA 已知可遭利用的漏洞到期日期: 2024/6/20
参考资料信息
CVE: CVE-2021-47391, CVE-2022-49995, CVE-2023-51042, CVE-2023-51043, CVE-2023-51780, CVE-2023-6040, CVE-2023-6915, CVE-2024-0562, CVE-2024-0565, CVE-2024-0646, CVE-2024-0775, CVE-2024-1086
CLSA: 2024:1707478061