遠端 Redhat Enterprise Linux 9 主機上安裝的多個套件受到 RHSA-2025:19268 公告中提及的多個弱點影響。

    kernel-rt 套件提供即時 Linux 核心，其可針對具有極高決定機制需求的系統啟用微調。

    安全性修復：

    * 核心：net：usb：smsc75xx：將封包長度限制為 skb->len (CVE-2023-53125)

    * 核心ASoCSOFIntelhda透過 snprintf() 修正潛在的緩衝區溢位 (CVE-2022-50050)

    * 核心mptcp不在已關閉的子流程上佇列資料 (CVE-2022-50070)

    * 核心RDMA/irdma修正釋放後使用視窗 (CVE-2022-50137)

    * 核心KVMSVM如果使用者空間插入 GIF=0 的中斷則不執行 BUG (CVE-2022-50228)

    * 核心：HID：核心：加強 s32ton() 以防止轉換成 0 位元 (CVE-2025-38556)

    * 核心：eventpoll：修正半無限制遞迴 (CVE-2025-38614)

    * 核心tls將 no-async 解密要求處理與 async 分開 (CVE-2024-58240)

    * 核心：ALSA：hda/ca0132：修正 add_tuning_control 中的緩衝區溢位 (CVE-2025-39751)

    * 核心：crypto：seqiv - 正確處理 EBUSY (CVE-2023-53373)

    如需安全性問題的詳細資料，包括影響、CVSS 分數、致謝及其他相關資訊，請參閱〈參照〉一節列出的 CVE 頁面。

Tenable 已直接從 Red Hat Enterprise Linux 安全公告擷取前置描述區塊。

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

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

  - 已解決 Linux 核心中的下列弱點：pid: take a reference when initializing `cad_pid` During boot, kernel_init_freeable() initializes `cad_pid` to the init task's struct pid. Later on, we may change `cad_pid` via a sysctl, and when this happens proc_do_cad_pid() will increment the refcount on the new pid via get_pid(), and will decrement the refcount on the old pid via put_pid(). As we never called get_pid() when we initialized `cad_pid`, we decrement a reference we never incremented, can therefore free the init task's struct pid early. As there can be dangling references to the struct pid, we can later encounter a use-after-free (e.g. when delivering signals). This was spotted when fuzzing v5.13-rc3 with Syzkaller, but seems to have been around since the conversion of `cad_pid` to struct pid in commit 9ec52099e4b8 ([PATCH] replace cad_pid by a struct pid) from the pre-KASAN stone age of v2.6.19. Fix this by getting a reference to the init task's struct pid when we assign it to `cad_pid`.
    Full KASAN splat below. ================================================================== BUG: KASAN:
    use-after-free in ns_of_pid include/linux/pid.h:153 [inline] BUG: KASAN: use-after-free in task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509 Read of size 4 at addr ffff23794dda0004 by task syz-executor.0/273 CPU: 1 PID: 273 Comm: syz-executor.0 Not tainted 5.12.0-00001-g9aef892b2d15 #1 Hardware name: linux,dummy-virt (DT) Call trace: ns_of_pid include/linux/pid.h:153 [inline] task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509 do_notify_parent+0x308/0xe60 kernel/signal.c:1950 exit_notify kernel/exit.c:682 [inline] do_exit+0x2334/0x2bd0 kernel/exit.c:845 do_group_exit+0x108/0x2c8 kernel/exit.c:922 get_signal+0x4e4/0x2a88 kernel/signal.c:2781 do_signal arch/arm64/kernel/signal.c:882 [inline] do_notify_resume+0x300/0x970 arch/arm64/kernel/signal.c:936 work_pending+0xc/0x2dc Allocated by task 0: slab_post_alloc_hook+0x50/0x5c0 mm/slab.h:516 slab_alloc_node mm/slub.c:2907 [inline] slab_alloc mm/slub.c:2915 [inline] kmem_cache_alloc+0x1f4/0x4c0 mm/slub.c:2920 alloc_pid+0xdc/0xc00 kernel/pid.c:180 copy_process+0x2794/0x5e18 kernel/fork.c:2129 kernel_clone+0x194/0x13c8 kernel/fork.c:2500 kernel_thread+0xd4/0x110 kernel/fork.c:2552 rest_init+0x44/0x4a0 init/main.c:687 arch_call_rest_init+0x1c/0x28 start_kernel+0x520/0x554 init/main.c:1064 0x0 Freed by task 270:
    slab_free_hook mm/slub.c:1562 [inline] slab_free_freelist_hook+0x98/0x260 mm/slub.c:1600 slab_free mm/slub.c:3161 [inline] kmem_cache_free+0x224/0x8e0 mm/slub.c:3177 put_pid.part.4+0xe0/0x1a8 kernel/pid.c:114 put_pid+0x30/0x48 kernel/pid.c:109 proc_do_cad_pid+0x190/0x1b0 kernel/sysctl.c:1401 proc_sys_call_handler+0x338/0x4b0 fs/proc/proc_sysctl.c:591 proc_sys_write+0x34/0x48 fs/proc/proc_sysctl.c:617 call_write_iter include/linux/fs.h:1977 [inline] new_sync_write+0x3ac/0x510 fs/read_write.c:518 vfs_write fs/read_write.c:605 [inline] vfs_write+0x9c4/0x1018 fs/read_write.c:585 ksys_write+0x124/0x240 fs/read_write.c:658 __do_sys_write fs/read_write.c:670 [inline] __se_sys_write fs/read_write.c:667 [inline] __arm64_sys_write+0x78/0xb0 fs/read_write.c:667 __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] invoke_syscall arch/arm64/kernel/syscall.c:49 [inline] el0_svc_common.constprop.1+0x16c/0x388 arch/arm64/kernel/syscall.c:129 do_el0_svc+0xf8/0x150 arch/arm64/kernel/syscall.c:168 el0_svc+0x28/0x38 arch/arm64/kernel/entry-common.c:416 el0_sync_handler+0x134/0x180 arch/arm64/kernel/entry-common.c:432 el0_sync+0x154/0x180 arch/arm64/kernel/entry.S:701 The buggy address belongs to the object at ffff23794dda0000 which belongs to the cache pid of size 224 The buggy address is located 4 bytes inside of 224-byte region [ff
    ---truncated--- (CVE-2021-47118)

  - 已解決 Linux 核心中的下列弱點：i2c: i801: Don't generate an interrupt on bus reset Now that the i2c-i801 driver supports interrupts, setting the KILL bit in a attempt to recover from a timed out transaction triggers an interrupt. Unfortunately, the interrupt handler (i801_isr) is not prepared for this situation and will try to process the interrupt as if it was signaling the end of a successful transaction. In the case of a block transaction, this can result in an out-of-range memory access. This condition was reproduced several times by syzbot:
    https://syzkaller.appspot.com/bug?extid=ed71512d469895b5b34e https://syzkaller.appspot.com/bug?extid=8c8dedc0ba9e03f6c79e https://syzkaller.appspot.com/bug?extid=c8ff0b6d6c73d81b610e https://syzkaller.appspot.com/bug?extid=33f6c360821c399d69eb https://syzkaller.appspot.com/bug?extid=be15dc0b1933f04b043a https://syzkaller.appspot.com/bug?extid=b4d3fd1dfd53e90afd79 So disable interrupts while trying to reset the bus. Interrupts will be enabled again for the following transaction. (CVE-2021-47153)

  - 已解決 Linux 核心中的下列弱點：scsi: target: Fix WRITE_SAME No Data Buffer crash In newer version of the SBC specs, we have a NDOB bit that indicates there is no data buffer that gets written out. If this bit is set using commands like sg_write_same --ndob we will crash in target_core_iblock/file's execute_write_same handlers when we go to access the se_cmd->t_data_sg because its NULL. This patch adds a check for the NDOB bit in the common WRITE SAME code because we don't support it. And, it adds a check for zero SG elements in each handler in case the initiator tries to send a normal WRITE SAME with no data buffer. (CVE-2022-21546)

  - 已解決 Linux 核心中的下列弱點：net/mlx5e: IPoIB, Block PKEY interfaces with less rx queues than parent A user is able to configure an arbitrary number of rx queues when creating an interface via netlink. This doesn't work for child PKEY interfaces because the child interface uses the parent receive channels. Although the child shares the parent's receive channels, the number of rx queues is important for the channel_stats array: the parent's rx channel index is used to access the child's channel_stats. So the array has to be at least as large as the parent's rx queue size for the counting to work correctly and to prevent out of bound accesses. This patch checks for the mentioned scenario and returns an error when trying to create the interface. The error is propagated to the user. (CVE-2022-48883)

  - 已解決 Linux 核心中的下列弱點：be2net: Fix buffer overflow in be_get_module_eeprom be_cmd_read_port_transceiver_data assumes that it is given a buffer that is at least PAGE_DATA_LEN long, or twice that if the module supports SFF 8472. However, this is not always the case.
    Fix this by passing the desired offset and length to be_cmd_read_port_transceiver_data so that we only copy the bytes once. (CVE-2022-49581)

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

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

  - 已解決 Linux 核心中的下列弱點：ASoC: SOF: Intel: hda: 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-50050)

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

遠端 Redhat Enterprise Linux 8 主機上安裝的套件受到 RHSA-2025:22752 公告中提及的多個弱點影響。

    核心套件中包含 Linux 核心，後者是任何 Linux 作業系統的核心。

    安全性修正：

    * 核心ALSAusb-audioALSA USB 音訊超出邊界錯誤 (CVE-2022-48701)

    * 核心：nfsd：不略過 svc_proc_register() 的傳回碼 (CVE-2025-22026)

    * 核心：udp：修正記憶體計量洩漏。(CVE-2025-22058)

    * 核心：net_sched：hfsc：修正類別處理中的 UAF 弱點 (CVE-2025-37797)

    * 核心：net：usb：smsc75xx：將封包長度限制為 skb->len (CVE-2023-53125)

    * kernel: net_sched: ets: 修復當 class 的子佇列為 netem 時，重複加入清單的問題 (CVE-2025-37914)

    * 核心ASoCSOFIntelhda透過 snprintf() 修正潛在的緩衝區溢位 (CVE-2022-50050)

    * 核心mptcp不在已關閉的子流程上佇列資料 (CVE-2022-50070)

    * 核心ALSAbcd2000修正探查錯誤路徑上的一個 UAF 錯誤 (CVE-2022-50229)

    * 核心KVMSVM如果使用者空間插入 GIF=0 的中斷則不執行 BUG (CVE-2022-50228)

    * 核心：韌體：arm_scpi：確保探查失敗時未指派 scpi_info (CVE-2022-50087)

    * 核心：bpf：在對 poke 描述符號進行陣列範圍檢查時，請勿使用 tnum_range (CVE-2022-49985)

    * 核心drm/amd/display關閉 odm 時鐘前清除 optc 反向溢位 (CVE-2022-49969)

    * 核心md-raid10修正 KASAN 警告 (CVE-2022-50211)

    * 核心：i40e：修正 MMIO 對 i40e_clear_hw 中無效頁面的寫入存取權 (CVE-2025-38200)

    * 核心：RDMA/iwcm：修復 cm_id 解構後工作物件的釋放後使用錯誤 (CVE-2025-38211)

    * 核心：scsi：lpfc：針對 BIOS 版本使用 memcpy() (CVE-2025-38332)

    * 核心：vsock：修復 transport_* TOCTOU (CVE-2025-38461)

    * 核心：drm/gem：取得框架緩衝區 GEM 控點上的參照 (CVE-2025-38449)

    * 核心：net/sched：sch_qfq：修復 qfq_aggregate 上的爭用情形 (CVE-2025-38477)

    * 核心：do_change_type()：拒絕在未掛載/非自身掛載上操作 (CVE-2025-38498)

    * 核心：smb：用戶端：修復 cifs_oplock_break 中的釋放後使用問題 (CVE-2025-38527)

    * 核心：HID：核心：加強 s32ton() 以防止轉換成 0 位元 (CVE-2025-38556)

    * 核心tls將 no-async 解密要求處理與 async 分開 (CVE-2024-58240)

    * 核心：NFS：修正更新現有寫入時的爭用情形 (CVE-2025-39697)

    * 核心：NFS：修正 nfs_fh_to_dentry() 中的 filehandle 邊界檢查 (CVE-2025-39730)

    * 核心：ALSA：hda/ca0132：修正 add_tuning_control 中的緩衝區溢位 (CVE-2025-39751)

    * 核心wifibrcmfmacbrcmf_get_assoc_ies() 中發生 slab 超出邊界讀取 (CVE-2023-53213)

    * 核心wifiath9k不允許覆寫 ENDPOINT0 屬性 (CVE-2023-53185)

    * 核心：mm：修復 zswap 回寫爭用情形 (CVE-2023-53178)

    * 核心藍牙L2CAP修正釋放後使用 (CVE-2023-53305)

    * 核心：fs：修復 nilfs_mdt_destroy 中的 UAF/GPF 錯誤 (CVE-2022-50367)

    * 核心netschedsfb修正 sfb_init() 失敗時的 NULL 指標存取問題 (CVE-2022-50356)

    * 核心skbuffskb_segment在使用 skbuff 片段之前呼叫零複製函式 (CVE-2023-53354)

    * 核心：crypto：seqiv - 正確處理 EBUSY (CVE-2023-53373)

    * 核心：Bluetooth：修正清除金鑰時的潛在釋放後使用 (CVE-2023-53386)

    * 核心：Bluetooth：L2CAP：修正釋放後使用 (CVE-2022-50386)

    * 核心ext4修正 ext4_check_flag_values 位元移位中的未定義行為 (CVE-2022-50403)

    * 核心wifibrcmfmac修正 brcmf_netdev_start_xmit() 中的釋放後使用錯誤 (CVE-2022-50408)

    * 核心NFSD防止 NFSv2 READ 中的傳送緩衝區溢位 (CVE-2022-50410)

    * 核心：wifi：cfg80211：修復 cmp_bss() 中的釋放後使用 (CVE-2025-39864)

    如需安全性問題的詳細資料，包括影響、CVSS 分數、致謝及其他相關資訊，請參閱〈參照〉一節列出的 CVE 頁面。

Tenable 已直接從 Red Hat Enterprise Linux 安全公告擷取前置描述區塊。

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

遠端 Redhat Enterprise Linux 8 主機上安裝的套件受到 RHSA-2025:21084 公告中提及的多個弱點影響。

    核心套件中包含 Linux 核心，後者是任何 Linux 作業系統的核心。

    安全性修正：

    * 核心ALSAusb-audioALSA USB 音訊超出邊界錯誤 (CVE-2022-48701)

    * 核心ASoCSOFIntelhda透過 snprintf() 修正潛在的緩衝區溢位 (CVE-2022-50050)

    * 核心wifibrcmfmacbrcmf_get_assoc_ies() 中發生 slab 超出邊界讀取 (CVE-2023-53213)

    * 核心wifiath9k不允許覆寫 ENDPOINT0 屬性 (CVE-2023-53185)

    * 核心mm修正 zswap 回寫爭用情形 (CVE-2023-53178)

    * 核心：fs：修復 nilfs_mdt_destroy 中的 UAF/GPF 錯誤 (CVE-2022-50367)

    * 核心：crypto：seqiv - 正確處理 EBUSY (CVE-2023-53373)

    * 核心：Bluetooth：修正清除金鑰時的潛在釋放後使用 (CVE-2023-53386)

    * 核心wifibrcmfmac修正 brcmf_netdev_start_xmit() 中的釋放後使用錯誤 (CVE-2022-50408)

    * 核心iomapiomap修正回寫期間記錄錯誤時的記憶體損毀 (CVE-2022-50406)

    * 核心：wifi：cfg80211：修復 cmp_bss() 中的釋放後使用 (CVE-2025-39864)

    * 核心：scsi：lpfc：修正延遲接收路徑中的緩衝區釋放/清除順序 (CVE-2025-39841)

    如需安全性問題的詳細資料，包括影響、CVSS 分數、致謝及其他相關資訊，請參閱〈參照〉一節列出的 CVE 頁面。

Tenable 已直接從 Red Hat Enterprise Linux 安全公告擷取前置描述區塊。

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

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

  - 已解決 Linux 核心中的下列弱點：pid: take a reference when initializing `cad_pid` During boot, kernel_init_freeable() initializes `cad_pid` to the init task's struct pid. Later on, we may change `cad_pid` via a sysctl, and when this happens proc_do_cad_pid() will increment the refcount on the new pid via get_pid(), and will decrement the refcount on the old pid via put_pid(). As we never called get_pid() when we initialized `cad_pid`, we decrement a reference we never incremented, can therefore free the init task's struct pid early. As there can be dangling references to the struct pid, we can later encounter a use-after-free (e.g. when delivering signals). This was spotted when fuzzing v5.13-rc3 with Syzkaller, but seems to have been around since the conversion of `cad_pid` to struct pid in commit 9ec52099e4b8 ([PATCH] replace cad_pid by a struct pid) from the pre-KASAN stone age of v2.6.19. Fix this by getting a reference to the init task's struct pid when we assign it to `cad_pid`.
    Full KASAN splat below. ================================================================== BUG: KASAN:
    use-after-free in ns_of_pid include/linux/pid.h:153 [inline] BUG: KASAN: use-after-free in task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509 Read of size 4 at addr ffff23794dda0004 by task syz-executor.0/273 CPU: 1 PID: 273 Comm: syz-executor.0 Not tainted 5.12.0-00001-g9aef892b2d15 #1 Hardware name: linux,dummy-virt (DT) Call trace: ns_of_pid include/linux/pid.h:153 [inline] task_active_pid_ns+0xc0/0xc8 kernel/pid.c:509 do_notify_parent+0x308/0xe60 kernel/signal.c:1950 exit_notify kernel/exit.c:682 [inline] do_exit+0x2334/0x2bd0 kernel/exit.c:845 do_group_exit+0x108/0x2c8 kernel/exit.c:922 get_signal+0x4e4/0x2a88 kernel/signal.c:2781 do_signal arch/arm64/kernel/signal.c:882 [inline] do_notify_resume+0x300/0x970 arch/arm64/kernel/signal.c:936 work_pending+0xc/0x2dc Allocated by task 0: slab_post_alloc_hook+0x50/0x5c0 mm/slab.h:516 slab_alloc_node mm/slub.c:2907 [inline] slab_alloc mm/slub.c:2915 [inline] kmem_cache_alloc+0x1f4/0x4c0 mm/slub.c:2920 alloc_pid+0xdc/0xc00 kernel/pid.c:180 copy_process+0x2794/0x5e18 kernel/fork.c:2129 kernel_clone+0x194/0x13c8 kernel/fork.c:2500 kernel_thread+0xd4/0x110 kernel/fork.c:2552 rest_init+0x44/0x4a0 init/main.c:687 arch_call_rest_init+0x1c/0x28 start_kernel+0x520/0x554 init/main.c:1064 0x0 Freed by task 270:
    slab_free_hook mm/slub.c:1562 [inline] slab_free_freelist_hook+0x98/0x260 mm/slub.c:1600 slab_free mm/slub.c:3161 [inline] kmem_cache_free+0x224/0x8e0 mm/slub.c:3177 put_pid.part.4+0xe0/0x1a8 kernel/pid.c:114 put_pid+0x30/0x48 kernel/pid.c:109 proc_do_cad_pid+0x190/0x1b0 kernel/sysctl.c:1401 proc_sys_call_handler+0x338/0x4b0 fs/proc/proc_sysctl.c:591 proc_sys_write+0x34/0x48 fs/proc/proc_sysctl.c:617 call_write_iter include/linux/fs.h:1977 [inline] new_sync_write+0x3ac/0x510 fs/read_write.c:518 vfs_write fs/read_write.c:605 [inline] vfs_write+0x9c4/0x1018 fs/read_write.c:585 ksys_write+0x124/0x240 fs/read_write.c:658 __do_sys_write fs/read_write.c:670 [inline] __se_sys_write fs/read_write.c:667 [inline] __arm64_sys_write+0x78/0xb0 fs/read_write.c:667 __invoke_syscall arch/arm64/kernel/syscall.c:37 [inline] invoke_syscall arch/arm64/kernel/syscall.c:49 [inline] el0_svc_common.constprop.1+0x16c/0x388 arch/arm64/kernel/syscall.c:129 do_el0_svc+0xf8/0x150 arch/arm64/kernel/syscall.c:168 el0_svc+0x28/0x38 arch/arm64/kernel/entry-common.c:416 el0_sync_handler+0x134/0x180 arch/arm64/kernel/entry-common.c:432 el0_sync+0x154/0x180 arch/arm64/kernel/entry.S:701 The buggy address belongs to the object at ffff23794dda0000 which belongs to the cache pid of size 224 The buggy address is located 4 bytes inside of 224-byte region [ff
    ---truncated--- (CVE-2021-47118)

  - 已解決 Linux 核心中的下列弱點：i2c: i801: Don't generate an interrupt on bus reset Now that the i2c-i801 driver supports interrupts, setting the KILL bit in a attempt to recover from a timed out transaction triggers an interrupt. Unfortunately, the interrupt handler (i801_isr) is not prepared for this situation and will try to process the interrupt as if it was signaling the end of a successful transaction. In the case of a block transaction, this can result in an out-of-range memory access. This condition was reproduced several times by syzbot:
    https://syzkaller.appspot.com/bug?extid=ed71512d469895b5b34e https://syzkaller.appspot.com/bug?extid=8c8dedc0ba9e03f6c79e https://syzkaller.appspot.com/bug?extid=c8ff0b6d6c73d81b610e https://syzkaller.appspot.com/bug?extid=33f6c360821c399d69eb https://syzkaller.appspot.com/bug?extid=be15dc0b1933f04b043a https://syzkaller.appspot.com/bug?extid=b4d3fd1dfd53e90afd79 So disable interrupts while trying to reset the bus. Interrupts will be enabled again for the following transaction. (CVE-2021-47153)

  - 已解決 Linux 核心中的下列弱點：scsi: target: Fix WRITE_SAME No Data Buffer crash In newer version of the SBC specs, we have a NDOB bit that indicates there is no data buffer that gets written out. If this bit is set using commands like sg_write_same --ndob we will crash in target_core_iblock/file's execute_write_same handlers when we go to access the se_cmd->t_data_sg because its NULL. This patch adds a check for the NDOB bit in the common WRITE SAME code because we don't support it. And, it adds a check for zero SG elements in each handler in case the initiator tries to send a normal WRITE SAME with no data buffer. (CVE-2022-21546)

  - 已解決 Linux 核心中的下列弱點：net/mlx5e: IPoIB, Block PKEY interfaces with less rx queues than parent A user is able to configure an arbitrary number of rx queues when creating an interface via netlink. This doesn't work for child PKEY interfaces because the child interface uses the parent receive channels. Although the child shares the parent's receive channels, the number of rx queues is important for the channel_stats array: the parent's rx channel index is used to access the child's channel_stats. So the array has to be at least as large as the parent's rx queue size for the counting to work correctly and to prevent out of bound accesses. This patch checks for the mentioned scenario and returns an error when trying to create the interface. The error is propagated to the user. (CVE-2022-48883)

  - 已解決 Linux 核心中的下列弱點：ath9k_htc: fix potential out of bounds access with invalid rxstatus->rs_keyix The rxstatus->rs_keyix eventually gets passed to test_bit() so we need to ensure that it is within the bitmap. drivers/net/wireless/ath/ath9k/common.c:46 ath9k_cmn_rx_accept() error: passing untrusted data 'rx_stats->rs_keyix' to 'test_bit()' (CVE-2022-49503)

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

Rocky Linux 8.6 主機已安裝的套件會受到 CIQ ciqsa-2026_0011 公告中提及的多個弱點影響。

    此公告彙總了 CIQ LTS 8.6中核心 SRPM 的安全修正。它解決了 19 個 CVE：
    CVE-2022-50386、CVE-2022-50050、 CVE-2025-38729CVE-2022-50403CVE-2023-52525和另外 14 個。

Tenable 已直接從 CIQ 安全性公告中擷取上述描述區塊。

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

遠端 Redhat Enterprise Linux 9 主機上安裝的多個套件受到 RHSA-2025:19492 公告中提及的多個弱點影響。

    核心套件中包含 Linux 核心，後者是任何 Linux 作業系統的核心。

    安全性修正：

    * 核心：net：usb：smsc75xx：將封包長度限制為 skb->len (CVE-2023-53125)

    * 核心ASoCSOFIntelhda透過 snprintf() 修正潛在的緩衝區溢位 (CVE-2022-50050)

    * 核心mptcp不在已關閉的子流程上佇列資料 (CVE-2022-50070)

    * 核心RDMA/irdma修正釋放後使用視窗 (CVE-2022-50137)

    * 核心KVMSVM如果使用者空間插入 GIF=0 的中斷則不執行 BUG (CVE-2022-50228)

    * 核心：HID：核心：加強 s32ton() 以防止轉換成 0 位元 (CVE-2025-38556)

    * 核心：eventpoll：修正半無限制遞迴 (CVE-2025-38614)

    * 核心tls將 no-async 解密要求處理與 async 分開 (CVE-2024-58240)

    * 核心：ALSA：hda/ca0132：修正 add_tuning_control 中的緩衝區溢位 (CVE-2025-39751)

    * 核心：crypto：seqiv - 正確處理 EBUSY (CVE-2023-53373)

    如需安全性問題的詳細資料，包括影響、CVSS 分數、致謝及其他相關資訊，請參閱〈參照〉一節列出的 CVE 頁面。

Tenable 已直接從 Red Hat Enterprise Linux 安全公告擷取前置描述區塊。

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

ID	名稱	產品	系列	已發布	已更新	嚴重性
272004	RHEL 9：kernel-rt (RHSA-2025:19268)	Nessus	Red Hat Local Security Checks	2025/10/29	2025/10/29	high
360928	CentOS Linux 8.5 [TuxCare] 安全性更新：bpftool / kernel / kernel-core / kernel-cross-headers / etc多個弱點（CENTOS8.5：CLSA-2026：1771077729）	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/1	high
243844	Linux Distros 未修補弱點：CVE-2022-50050	Nessus	Misc.	2025/8/5	2026/9/30	high
277472	RHEL 8：核心 (RHSA-2025:22752)	Nessus	Red Hat Local Security Checks	2025/12/4	2026/2/26	high
274973	RHEL 8：核心 (RHSA-2025:21084)	Nessus	Red Hat Local Security Checks	2025/11/12	2025/11/12	high
361173	CentOS Linux 8.4 [TuxCare] 安全性更新：bpftool / kernel / kernel-core / kernel-cross-headers / etc 多個弱點（CENTOS8.4：CLSA-2026：1771078945）	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/1	high
359273	Rocky Linux 8.6 [CIQ] 安全性更新：bpftool / bpftool-debuginfo / kernel / kernel-abi-stablelists / etc 多個弱點（ciqsa-2026_0011）	Nessus	Rocky Linux Local Security Checks	2026/10/1	2026/10/1	high
272215	RHEL 9：核心 (RHSA-2025:19492)	Nessus	Red Hat Local Security Checks	2025/11/3	2025/11/3	high

偵測

搜尋 Plugin

high

high

high

high

high

high

high

high