Rocky Linux 8 主机上存在安装的程序包，该程序包受到 CIQ crlsa-2024_5101 公告中提及的多个漏洞的影响。

    * 内核：powerpc：修复超出 drmem 数组末尾的访问 (CVE-2023-52451)

    * 内核：如果 SetVariable 不受支持，则在重新挂载时强制执行 RO (CVE-2023-52463)

    * 内核：tracing：重构 trace_clock_global() 以永不阻断 (CVE-2021-46939)

    - 内核：ext4：避免因 flex bg 过大而导致的在线调整大小失败 (CVE-2023-52622)

    * 内核：net/sched：flower：修复链模板卸载 (CVE-2024-26669)

    * 内核：stmmac：销毁工作队列时清除变量 (CVE-2024-26802)

    * 内核：efi：runtime：修复软保留区域大小的潜在溢出 (CVE-2024-26843)

    * 内核：quota：修复潜在的空指针取消引用 (CVE-2024-26878)

    * 内核：TIPC 消息重组释放后使用远程代码执行漏洞 (CVE-2024-36886)

    * 内核：SUNRPC：修复 gss_import_v2_context 中的内存泄漏 (CVE-2023-52653)

    * kernel: dmaengine/idxd：硬件勘误表允许通过不受信任的应用程序直接访问造成潜在的安全问题 (CVE-2024-21823)

    - 内核：恢复 net/mlx5：阻止进入存在 ns 不一致的 switchdev 模式 (CVE-2023-52658)

    * 内核：ext4：修复在线调整大小期间的损坏问题 (CVE-2024-35807)

    * 内核：x86/fpu：保持 xfd_state 与 MSR_IA32_XFD 之间的同步 (CVE-2024-35801)

    * 内核：dyndbg：修复 >control 解析器中的旧 BUG_ON (CVE-2024-35947)

    * 内核：net/sched：act_skbmod：防止内核发生信息泄露 (CVE-2024-35893)

    * 内核：x86/mce：确保在 set_bank() 中获取 mce_sysfs_mutex (CVE-2024-35876)

    * 内核：platform/x86：wmi：修复字符设备打开问题 (CVE-2023-52864)

    * 内核：tipc：将与持有者相关的名称的 nla_policy 更改为 NLA_NUL_STRING (CVE-2023-52845)

    * (CVE-2023-28746)
    * (CVE-2023-52847)
    * (CVE-2021-47548)
    * (CVE-2024-36921)
    * (CVE-2024-26921)
    * (CVE-2021-47579)
    * (CVE-2024-36927)
    * (CVE-2024-39276)
    * (CVE-2024-33621)
    * (CVE-2024-27010)
    * (CVE-2024-26960)
    * (CVE-2024-38596)
    * (CVE-2022-48743)
    * (CVE-2024-26733)
    * (CVE-2024-26586)
    * (CVE-2024-26698)
    * (CVE-2023-52619)

    错误修复：

    * Rocky Linux8.6 - Spinlock 统计数据可能显示负的经过时间和格式不正确的输出 (JIRA:Rocky Linux-17678)

    * [AWS][8.9] 为 Amazon EC2 r8g.metal-24xl 实例启动调试内核时发现调用跟踪 (JIRA:Rocky Linux-23841)

    * [rhel8] gfs2：修复 glock shrinker (JIRA:Rocky Linux-32941)

    * lan78xx：Microchip LAN7800 在拔出和重新插入后从未启动 (JIRA:Rocky Linux-33437)

    * [Hyper-V][Rocky Linux-8.10.z] 将 hv_netvsc 驱动程序更新至 TOT (JIRA:Rocky Linux-39074)

    * proc inode-i_sb 上 fsnotify 触发的释放后使用 (JIRA:Rocky Linux-40167)

    * blk-cgroup：正确地将 iostat 更新向上传播到层次结构 [rhel-8.10.z] (JIRA:Rocky Linux-40939)

    * (JIRA:Rocky Linux-31798)
    * (JIRA:Rocky Linux-10263)
    * (JIRA:Rocky Linux-40901)
    * (JIRA:Rocky Linux-43547)
    * (JIRA:Rocky Linux-34876)

    增强功能：

    * [RFE] 为自定义 softdog 配置添加模块参数“soft_reboot_cmd”和“soft_active_on_boot”(JIRA:Rocky Linux-19723)

Tenable 已直接从 CIQ 安全公告中提取上述描述块。

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

Rocky Linux 8 主机上存在安装的程序包，该程序包受到 CIQ crlsa-2024_5102 公告中提及的多个漏洞的影响。

    * 内核：如果 SetVariable 不受支持，则在重新挂载时强制执行 RO (CVE-2023-52463)

    * 内核：tracing：重构 trace_clock_global() 以永不阻断 (CVE-2021-46939)

    - 内核：ext4：避免因 flex bg 过大而导致的在线调整大小失败 (CVE-2023-52622)

    * 内核：net/sched：flower：修复链模板卸载 (CVE-2024-26669)

    * 内核：stmmac：销毁工作队列时清除变量 (CVE-2024-26802)

    * 内核：efi：runtime：修复软保留区域大小的潜在溢出 (CVE-2024-26843)

    * 内核：quota：修复潜在的空指针取消引用 (CVE-2024-26878)

    * 内核：TIPC 消息重组释放后使用远程代码执行漏洞 (CVE-2024-36886)

    * 内核：SUNRPC：修复 gss_import_v2_context 中的内存泄漏 (CVE-2023-52653)

    * kernel: dmaengine/idxd：硬件勘误表允许通过不受信任的应用程序直接访问造成潜在的安全问题 (CVE-2024-21823)

    * 内核：ext4：修复在线调整大小期间的损坏问题 (CVE-2024-35807)

    * 内核：x86/fpu：保持 xfd_state 与 MSR_IA32_XFD 之间的同步 (CVE-2024-35801)

    * 内核：dyndbg：修复 >control 解析器中的旧 BUG_ON (CVE-2024-35947)

    * 内核：net/sched：act_skbmod：防止内核发生信息泄露 (CVE-2024-35893)

    * 内核：x86/mce：确保在 set_bank() 中获取 mce_sysfs_mutex (CVE-2024-35876)

    * 内核：platform/x86：wmi：修复字符设备打开问题 (CVE-2023-52864)

    * 内核：tipc：将与持有者相关的名称的 nla_policy 更改为 NLA_NUL_STRING (CVE-2023-52845)

    - 内核：恢复 net/mlx5：阻止进入存在 ns 不一致的 switchdev 模式 (CVE-2023-52658)

    * 内核：由于缺少 leb_size 检查而崩溃 (CVE-2024-25739)

    * 内核：tcp：确保初始化一次 accept_queue 的自旋锁 (CVE-2024-26614)

    * 内核：将健全性检查添加至 rx zerocopy (CVE-2024-26640)

    * 内核：NFSv4.2：修复了 mm/usercopy.c:102 的 nfs4_listxattr 内核缺陷 (CVE-2024-26870)

    * 内核：nfs：修复直接写入中的 UAF 问题 (CVE-2024-26958)

    * 内核：SUNRPC：修复 gssx_dec_option_array 中的某些内存泄漏 (CVE-2024-27388)

    * 内核：wifi：iwlwifi：mvm：不要为 GTK 设置 MFP 标记 (CVE-2024-27434)

    * 内核：of：修复 of_parse_phandle_with_args_map 中的双重释放 (CVE-2023-52679)

    * 内核：scsi：lpfc：修复 lpfc_rcv_padisc() 中可能的内存泄漏 (CVE-2024-35930)

    * 内核：wifi：iwlwifi：mvm：rfi：修复潜在的响应泄漏 (CVE-2024-35912)

    * 内核：block：防止 blk_rq_stat_sum() 中发生除以零错误 (CVE-2024-35925)

    * 内核：wifi：ath11k：将 MHI 通道缓冲区长度减少到 8KB (CVE-2024-35938)

    * kernel: wifi: cfg80211：更仔细地检查 A-MSDU 格式 (CVE-2024-35937)

    * 内核：wifi：rtw89：修复中止扫描时的空指针访问 (CVE-2024-35946)

    * 内核：netfilter：nf_tables：遵守来自 netdev 释放事件路径的表休眠标记 (CVE-2024-36005)

    * 内核：mm/hugetlb：修复了 resv uncharge 缺少 hugetlb_lock 的问题 (CVE-2024-36000)

    * 内核：mlxsw：spectrum_acl_tcam：修复错误的列表 API 使用 (CVE-2024-36006)

    * 内核：net：ieee802154：修复解析 dev 地址中的空取消引用 (CVE-2021-47257)

    * 内核：mmc：sdio：修复某些错误路径中可能的资源泄漏 (CVE-2023-52730)

    * 内核：wifi：ath11k：修复 gtk 卸载状态事件锁定 (CVE-2023-52777)

    * (CVE-2023-52832)
    * (CVE-2023-52803)
    * (CVE-2023-52756)
    * (CVE-2023-52834)
    * (CVE-2023-52791)
    * (CVE-2023-52764)
    * (CVE-2021-47468)
    * (CVE-2021-47284)
    * (CVE-2024-36025)
    * (CVE-2024-36941)
    * (CVE-2024-36940)
    * (CVE-2024-36904)
    * (CVE-2024-36896)
    * (CVE-2024-36954)
    * (CVE-2024-36950)
    * (CVE-2024-38575)
    * (CVE-2024-36917)
    * (CVE-2024-36016)
    * (CVE-2023-52762)
    * (CVE-2024-27025)
    * (CVE-2021-47548)
    * (CVE-2023-52619)

Tenable 已直接从 CIQ 安全公告中提取上述描述块。

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

Rocky Linux 9.4 主机上存在安装的程序包，该程序包受到 CIQ ciqsa-2026_1241 公告中提及的多个漏洞的影响。

    此公告汇总了 CIQ LTS 9.4中 kernel-rt SRPM 的安全修复。它解决了 16 个 CVE：
    CVE-2023-52606、 CVE-2024-42301、 CVE-2024-36960、 CVE-2024-38581和 CVE-2023-5293311 个。

Tenable 已直接从 CIQ 安全公告中提取上述描述块。

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

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

  - 已修复 Linux 内核中的下列漏洞：tracing: Restructure trace_clock_global() to never block It was reported that a fix to the ring buffer recursion detection would cause a hung machine when performing suspend / resume testing. The following backtrace was extracted from debugging that case: Call Trace: trace_clock_global+0x91/0xa0 __rb_reserve_next+0x237/0x460 ring_buffer_lock_reserve+0x12a/0x3f0 trace_buffer_lock_reserve+0x10/0x50 __trace_graph_return+0x1f/0x80 trace_graph_return+0xb7/0xf0 ? trace_clock_global+0x91/0xa0 ftrace_return_to_handler+0x8b/0xf0 ? pv_hash+0xa0/0xa0 return_to_handler+0x15/0x30 ? ftrace_graph_caller+0xa0/0xa0 ? trace_clock_global+0x91/0xa0 ? __rb_reserve_next+0x237/0x460 ? ring_buffer_lock_reserve+0x12a/0x3f0 ? trace_event_buffer_lock_reserve+0x3c/0x120 ? trace_event_buffer_reserve+0x6b/0xc0 ? trace_event_raw_event_device_pm_callback_start+0x125/0x2d0 ? dpm_run_callback+0x3b/0xc0 ? pm_ops_is_empty+0x50/0x50 ? platform_get_irq_byname_optional+0x90/0x90 ? trace_device_pm_callback_start+0x82/0xd0 ? dpm_run_callback+0x49/0xc0 With the following RIP: RIP:
    0010:native_queued_spin_lock_slowpath+0x69/0x200 Since the fix to the recursion detection would allow a single recursion to happen while tracing, this lead to the trace_clock_global() taking a spin lock and then trying to take it again: ring_buffer_lock_reserve() { trace_clock_global() { arch_spin_lock() {queued_spin_lock_slowpath() { /* lock taken */ (something else gets traced by function graph tracer) ring_buffer_lock_reserve() { trace_clock_global() { arch_spin_lock() { queued_spin_lock_slowpath() { /* DEAD LOCK! */ Tracing should *never* block, as it can lead to strange lockups like the above. Restructure the trace_clock_global() code to instead of simply taking a lock to update the recorded prev_time simply use it, as two events happening on two different CPUs that calls this at the same time, really doesn't matter which one goes first. Use a trylock to grab the lock for updating the prev_time, and if it fails, simply try again the next time. If it failed to be taken, that means something else is already updating it. Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=212761 (CVE-2021-46939)

  - 已修复 Linux 内核中的下列漏洞：net: amd-xgbe: Fix skb data length underflow There will be BUG_ON() triggered in include/linux/skbuff.h leading to intermittent kernel panic, when the skb length underflow is detected. Fix this by dropping the packet if such length underflows are seen because of inconsistencies in the hardware descriptors. (CVE-2022-48743)

  - 已修复 Linux 内核中的下列漏洞：nvme-rdma: fix possible use-after-free in transport error_recovery work While nvme_rdma_submit_async_event_work is checking the ctrl and queue state before preparing the AER command and scheduling io_work, in order to fully prevent a race where this check is not reliable the error recovery work must flush async_event_work before continuing to destroy the admin queue after setting the ctrl state to RESETTING such that there is no race .submit_async_event and the error recovery handler itself changing the ctrl state. (CVE-2022-48788)

  - 已修复 Linux 内核中的下列漏洞：nvme-tcp: fix possible use-after-free in transport error_recovery work While nvme_tcp_submit_async_event_work is checking the ctrl and queue state before preparing the AER command and scheduling io_work, in order to fully prevent a race where this check is not reliable the error recovery work must flush async_event_work before continuing to destroy the admin queue after setting the ctrl state to RESETTING such that there is no race .submit_async_event and the error recovery handler itself changing the ctrl state. (CVE-2022-48789)

  - 已修复 Linux 内核中的下列漏洞：nvme: fix a possible use-after-free in controller reset during load Unlike .queue_rq, in .submit_async_event drivers may not check the ctrl readiness for AER submission. This may lead to a use-after-free condition that was observed with nvme-tcp.
    The race condition may happen in the following scenario: 1. driver executes its reset_ctrl_work 2. -> nvme_stop_ctrl - flushes ctrl async_event_work 3. ctrl sends AEN which is received by the host, which in turn schedules AEN handling 4. teardown admin queue (which releases the queue socket) 5. AEN processed, submits another AER, calling the driver to submit 6. driver attempts to send the cmd ==> use-after-free In order to fix that, add ctrl state check to validate the ctrl is actually able to accept the AER submission. This addresses the above race in controller resets because the driver during teardown should:
    1. change ctrl state to RESETTING 2. flush async_event_work (as well as other async work elements) So after 1,2, any other AER command will find the ctrl state to be RESETTING and bail out without submitting the AER. (CVE-2022-48790)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
354377	Rocky Linux 8 [CIQ] 安全更新：bpftool / bpftool-debuginfo / kernel / kernel-abi-stablelists / 等多种漏洞（crlsa-2024_5101）	Nessus	Rocky Linux Local Security Checks	2026/10/1	2026/10/1	high
355882	Rocky Linux 8 [CIQ] 安全更新：kernel-rt / kernel-rt-core / kernel-rt-debug / kernel-rt-debug-core / etc 多种漏洞（crlsa-2024_5102）	Nessus	Rocky Linux Local Security Checks	2026/10/1	2026/10/1	high
357201	Rocky Linux 9.4 [CIQ] 安全更新：kernel-rt-debug-debuginfo / kernel-rt-debuginfo 多种漏洞（ciqsa-2026_1241）	Nessus	Rocky Linux Local Security Checks	2026/10/1	2026/10/2	high
366937	CentOS Linux 8.4 [TuxCare] 安全更新：bpftool / kernel / kernel-core / kernel-cross-headers / 等多个漏洞（CENTOS8.4：CLSA-2024：1725872696）	Nessus	CentOS Local Security Checks	2026/10/18	2026/10/18	high

检测

插件搜索

high

high

high

high