CentOS Linux 8.5 主機已安裝的套件會受到 TuxCare CENTOS8.5：CLSA-2026：1782146775 公告中提及的多個弱點影響。

  - Linux 核心 CIFS 實作 4.9.0 容易受到目錄項目清單中的相對路徑插入影響。(CVE-2019-10220)

  - Linux 核心 4.20.5 及之前版本中的 KVM 實作存在釋放後使用弱點。(CVE-2019-7221)

  - BlueZ 中存在不當輸入驗證，未經驗證的使用者或可藉此透過相鄰存取造成特權提升。(CVE-2020-12351)

  - BlueZ 中的不當存取控制可能會允許未經驗證的使用者透過相鄰存取造成資訊洩漏。(CVE-2020-12352)

  - BlueZ 中存在不當緩存限制，未經驗證的使用者可藉此透過相鄰存取造成拒絕服務。這會影響所有支援 BlueZ 的 Linux 核心版本。(CVE-2020-24490)

請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

CentOS Linux 8 主機已安裝的套件會受到 TuxCare CENTOS-STREAM8：CLSA-2026：1782375682 公告中提及的多個弱點影響。

  - 已解決 Linux 核心中的下列弱點：bpf: Don't redirect packets with invalid pkt_len Syzbot found an issue [1]: fq_codel_drop() try to drop a flow whitout any skbs, that is, the flow->head is null. The root cause, as the [2] says, is because that bpf_prog_test_run_skb() run a bpf prog which redirects empty skbs. So we should determine whether the length of the packet modified by bpf prog or others like bpf_prog_test is valid before forwarding it directly. (CVE-2022-49975)

  - 已解決 Linux 核心中的下列弱點：ASoC: SOF: debug: Fix potential buffer overflow by snprintf() snprintf() returns the would-be-filled size when the string overflows the given buffer size, hence using this value may result in the buffer overflow (although it's unrealistic). This patch replaces with a safer version, scnprintf() for papering over such a potential issue.
    (CVE-2022-50051)

  - 已解決 Linux 核心中的下列弱點：x86/alternatives: Disable KASAN in apply_alternatives() Fei has reported that KASAN triggers during apply_alternatives() on a 5-level paging machine: BUG: KASAN: out-of-bounds in rcu_is_watching() Read of size 4 at addr ff110003ee6419a0 by task swapper/0/0 ... __asan_load4() rcu_is_watching() trace_hardirqs_on() text_poke_early() apply_alternatives() ... On machines with 5-level paging, cpu_feature_enabled(X86_FEATURE_LA57) gets patched. It includes KASAN code, where KASAN_SHADOW_START depends on __VIRTUAL_MASK_SHIFT, which is defined with cpu_feature_enabled(). KASAN gets confused when apply_alternatives() patches the KASAN_SHADOW_START users. A test patch that makes KASAN_SHADOW_START static, by replacing
    __VIRTUAL_MASK_SHIFT with 56, works around the issue. Fix it for real by disabling KASAN while the kernel is patching alternatives. [ mingo: updated the changelog ] (CVE-2023-52504)

  - 已解決 Linux 核心中的下列弱點：drm/amd: Fix UBSAN array-index-out-of-bounds for SMU7 For pptable structs that use flexible array sizes, use flexible arrays. (CVE-2023-52818)

  - 已解決 Linux 核心中的下列弱點：nbd: defer config unlock in nbd_genl_connect There is one use-after-free warning when running NBD_CMD_CONNECT and NBD_CLEAR_SOCK:
    nbd_genl_connect nbd_alloc_and_init_config // config_refs=1 nbd_start_device // config_refs=2 set NBD_RT_HAS_CONFIG_REF open nbd // config_refs=3 recv_work done // config_refs=2 NBD_CLEAR_SOCK // config_refs=1 close nbd // config_refs=0 refcount_inc -> uaf ------------[ cut here ]------------ refcount_t: addition on 0; use-after-free. WARNING: CPU: 24 PID: 1014 at lib/refcount.c:25 refcount_warn_saturate+0x12e/0x290 nbd_genl_connect+0x16d0/0x1ab0 genl_family_rcv_msg_doit+0x1f3/0x310 genl_rcv_msg+0x44a/0x790 The issue can be easily reproduced by adding a small delay before refcount_inc(&nbd->config_refs) in nbd_genl_connect(): mutex_unlock(&nbd->config_lock); if (!ret) {set_bit(NBD_RT_HAS_CONFIG_REF, &config->runtime_flags); + printk(before sleep\n); + mdelay(5 * 1000); + printk(after sleep\n); refcount_inc(&nbd->config_refs); nbd_connect_reply(info, nbd->index); } (CVE-2025-68366)

請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

Linux/Unix 主機上安裝了一個或多個受到弱點影響的套件，且供應商未提供可用的修補程式。

  - 已解決 Linux 核心中的下列弱點：ASoC: SOF: debug: Fix potential buffer overflow by snprintf() snprintf() returns the would-be-filled size when the string overflows the given buffer size, hence using this value may result in the buffer overflow (although it's unrealistic). This patch replaces with a safer version, scnprintf() for papering over such a potential issue.
    (CVE-2022-50051)

請注意，Nessus 依賴供應商報告的套件存在。

CentOS Linux 8.4 主機已安裝的套件會受到 TuxCare CENTOS8.4：CLSA-2026：1782145985 公告中提及的多個弱點影響。

  - Linux 核心 CIFS 實作 4.9.0 容易受到目錄項目清單中的相對路徑插入影響。(CVE-2019-10220)

  - 在 5.3.2 版及之前版本的 Linux 核心中，在 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 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

ID	名稱	產品	系列	已發布	已更新	嚴重性
360215	CentOS Linux 8.5 [TuxCare] 安全性更新：bpftool / kernel / kernel-core / kernel-cross-headers / etc多個弱點（CENTOS8.5：CLSA-2026：1782146775）	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/1	high
361917	CentOS Linux 8 [TuxCare] 安全性更新：bpftool / kernel / kernel-core / kernel-cross-headers / etc多個漏洞（CENTOS-STREAM8：CLSA-2026：1782375682）	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/1	high
244084	Linux Distros 未修補弱點：CVE-2022-50051	Nessus	Misc.	2025/8/6	2026/9/30	high
360976	CentOS Linux 8.4 [TuxCare] 安全性更新：bpftool / kernel / kernel-core / kernel-cross-headers / etc 多個弱點（CENTOS8.4：CLSA-2026：1782145985）	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/1	high

偵測

搜尋 Plugin

high

high

high

high