CentOS Linux 8.5 主机上存在安装的程序包，该程序包受到 TuxCare CENTOS8.5：CLSA-2026：U 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 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

远程 Redhat Enterprise Linux 9 主机上安装的程序包受到 RHSA-2025:19268 公告中提及的多个漏洞影响。

    kernel-rt 程序包提供 Real Time Linux Kernel，支持对具有极高确定性要求的系统进行微调。

    安全修复：

    * kernel：net：usb：smsc75xx：将数据包长度限制为 skb->len (CVE-2023-53125)

    * kernelASoCSOFIntelhda修复了 snprintf() 潜在的缓冲区溢出CVE-2022-50050]

    * kernel: mptcp不在已关闭的子流中排队数据 (CVE-2022-50070)

    * kernelRDMA/irdma修复释放后使用的窗口 (CVE-2022-50137)

    * kernelKVMSVM如果用户空间注入 GIF=0 的中断则不进行 BUGCVE-2022-50228]

    * kernel: HID: core：强化 s32ton() 以防止转换为 0 位 (CVE-2025-38556)

    * kernel：eventpoll：修复半无限递归 (CVE-2025-38614)

    * kernel: tls将非异步解密请求处理与异步分离 (CVE-2024-58240)

    - 内核：ALSA：hda/ca0132：修复 add_tuning_control 中的缓冲区溢出 (CVE-2025-39751)

    * kernel：crypto：seqiv - 正确处理 EBUSY (CVE-2023-53373)

    有关上述安全问题的更多详细信息，包括其影响、CVSS 得分、致谢，以及其他相关信息，请参阅列于“参考”部分的 CVE 页面。

Tenable 已直接从 Red Hat Enterprise Linux 安全公告中提取上述描述块。

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

如 TuxCare CENTOS8.4：CLSA-2026：1771078945公告所述，CentOS Linux 8.4 主机上存在安装的程序包，该漏洞会受到多个漏洞的影响。

  - 已修复 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 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

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 操作系统的核心。

    安全修复：

    * kernel: ALSAusb-audioALSA USB 音频越界缺陷CVE-2022-48701

    * 内核：nfsd：不会忽略 svc_proc_register() 的返回代码 (CVE-2025-22026)

    * 内核：udp：修复内存核算泄漏。(CVE-2025-22058)

    * kernel：net_sched: hfsc：修复类处理中的 UAF 漏洞 (CVE-2025-37797)

    * kernel：net：usb：smsc75xx：将数据包长度限制为 skb->len (CVE-2023-53125)

    * 内核：net_sched：ets：修复类中以 netem 作为子 qdisc 的双列表添加 (CVE-2025-37914)

    * kernelASoCSOFIntelhda修复了 snprintf() 潜在的缓冲区溢出CVE-2022-50050]

    * kernel: mptcp不在已关闭的子流中排队数据 (CVE-2022-50070)

    * kernelALSAbcd2000修复探测错误路径上的 UAF 缺陷CVE-2022-50229]

    * kernelKVMSVM如果用户空间注入 GIF=0 的中断则不进行 BUGCVE-2022-50228]

    * 内核：firmware：arm_scpi：确保探测失败时不分配 scpi_info (CVE-2022-50087)

    * 内核：bpf：不要对 poke 描述符的数组范围检查使用 tnum_range(CVE-2022-49985)

    * kernel: drm/amd/display关闭 odm 时钟前清除 optc 下溢 (CVE-2022-49969)

    * kernel: md-raid10修复 KASAN 警告 (CVE-2022-50211)

    * 内核：i40e：修复 i40e_clear_hw 中 MMIO 对无效页面的写入访问权 (CVE-2025-38200)

    * kernel：RDMA/iwcm：修复 cm_id 销毁之后工作对象的释放后使用 (CVE-2025-38211)

    * kernel：scsi：lpfc：使用 memcpy() 处理 BIOS 版本 (CVE-2025-38332)

    * 内核：vsock：修复 transport_* TOCTOU (CVE-2025-38461)

    * kernel: drm/gem：获取有关帧缓冲区的 GEM 句柄的引用 (CVE-2025-38449)

    * kernel：net/sched：sch_qfq：修复 qfq_aggregate 中的争用条件 (CVE-2025-38477)

    * kernel: do_change_type()：拒绝在未挂载/非我方挂载的情况下操作 (CVE-2025-38498)

    * 内核：smb：客户端：修复 cifs_oplock_break 中的释放后使用漏洞 (CVE-2025-38527)

    * kernel: HID: core：强化 s32ton() 以防止转换为 0 位 (CVE-2025-38556)

    * kernel: tls将非异步解密请求处理与异步分离 (CVE-2024-58240)

    * kernel: NFS：修复更新现有写入时的争用问题 (CVE-2025-39697)

    * 内核：NFS：修复 nfs_fh_to_dentry() 中的文件句柄边界检查 (CVE-2025-39730)

    - 内核：ALSA：hda/ca0132：修复 add_tuning_control 中的缓冲区溢出 (CVE-2025-39751)

    * kernel: wifi: brcmfmacbrcmf_get_assoc_ies() 中的 slab 越界读取 (CVE-2023-53213)

    * kernel: wifi: ath9k不允许覆盖 ENDPOINT0 属性 (CVE-2023-53185)

    * 内核：mm：修复 zswap 回写争用条件 (CVE-2023-53178)

    * kernelBluetoothL2CAP修复释放后使用 (CVE-2023-53305)

    * 内核：fs : 修复 nilfs_mdt_destroy 中的 UAF/GPF 缺陷 (CVE-2022-50367)

    * kernel: net: sched: sfb修复了 sfb_init() 失败时的空指针访问问题 (CVE-2022-50356)

    * kernel: skbuffskb_segment使用 skbuff frags 之前调用零复制函数 (CVE-2023-53354)

    * kernel：crypto：seqiv - 正确处理 EBUSY (CVE-2023-53373)

    - 内核：Bluetooth：修复清除密钥时可能出现的释放后使用问题 [CVE-2023-53386]

    * 内核：Bluetooth：L2CAP：修复释放后使用问题 (CVE-2022-50386)

    * kernelext4修复 ext4_check_flag_values 位移中的未定义行为 (CVE-2022-50403)

    * kernelwifibrcmfmac修复 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 操作系统的核心。

    安全修复：

    * kernel: ALSAusb-audioALSA USB 音频越界缺陷CVE-2022-48701

    * kernelASoCSOFIntelhda修复了 snprintf() 潜在的缓冲区溢出CVE-2022-50050]

    * kernel: wifi: brcmfmacbrcmf_get_assoc_ies() 中的 slab 越界读取 (CVE-2023-53213)

    * kernel: wifi: ath9k不允许覆盖 ENDPOINT0 属性 (CVE-2023-53185)

    * 内核mm修复 zswap 回写争用条件 (CVE-2023-53178)

    * kernel: fs : 修复 nilfs_mdt_destroy 中的 UAF/GPF 缺陷 (CVE-2022-50367)

    * kernel：crypto：seqiv - 正确处理 EBUSY (CVE-2023-53373)

    - 内核：Bluetooth：修复清除密钥时可能出现的释放后使用问题 [CVE-2023-53386]

    * kernelwifibrcmfmac修复 brcmf_netdev_start_xmit() 中的释放后使用缺陷 (CVE-2022-50408)

    * kerneliomapiomap修复回写期间记录错误时的内存损坏 (CVE-2022-50406)

    * kernel: wifi: cfg80211 : 修复 cmp_bss() 中的释放后使用  (CVE-2025-39864)

    * 内核：scsi：lpfc：修复延迟接收路径中的缓冲区释放/清除顺序 (CVE-2025-39841)

    有关上述安全问题的更多详细信息，包括其影响、CVSS 得分、致谢，以及其他相关信息，请参阅列于“参考”部分的 CVE 页面。

Tenable 已直接从 Red Hat Enterprise Linux 安全公告中提取上述描述块。

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

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

    此公告汇总了 CIQ LTS 8.6中内核 SRPM 的安全修复。它解决了 19 个 CVE：
    CVE-2022-50386、 CVE-2022-50050、 CVE-2025-38729、 CVE-2022-50403、 和 CVE-2023-5252514 个。

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

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

远程 Redhat Enterprise Linux 9 主机上安装的程序包受到 RHSA-2025:19492 公告中提及的多个漏洞影响。

    内核程序包中包含 Linux 内核，后者是任何 Linux 操作系统的核心。

    安全修复：

    * kernel：net：usb：smsc75xx：将数据包长度限制为 skb->len (CVE-2023-53125)

    * kernelASoCSOFIntelhda修复了 snprintf() 潜在的缓冲区溢出CVE-2022-50050]

    * kernel: mptcp不在已关闭的子流中排队数据 (CVE-2022-50070)

    * kernelRDMA/irdma修复释放后使用的窗口 (CVE-2022-50137)

    * kernelKVMSVM如果用户空间注入 GIF=0 的中断则不进行 BUGCVE-2022-50228]

    * kernel: HID: core：强化 s32ton() 以防止转换为 0 位 (CVE-2025-38556)

    * kernel：eventpoll：修复半无限递归 (CVE-2025-38614)

    * kernel: tls将非异步解密请求处理与异步分离 (CVE-2024-58240)

    - 内核：ALSA：hda/ca0132：修复 add_tuning_control 中的缓冲区溢出 (CVE-2025-39751)

    * kernel：crypto：seqiv - 正确处理 EBUSY (CVE-2023-53373)

    有关上述安全问题的更多详细信息，包括其影响、CVSS 得分、致谢，以及其他相关信息，请参阅列于“参考”部分的 CVE 页面。

Tenable 已直接从 Red Hat Enterprise Linux 安全公告中提取上述描述块。

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
360928	CentOS Linux 8.5 [TuxCare] 安全更新：bpftool / kernel / kernel-core / kernel-cross-headers / 等多个漏洞（CENTOS8.5：CLSA-2026：1771077729）	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/1	high
272004	RHEL 9：kernel-rt (RHSA-2025:19268)	Nessus	Red Hat Local Security Checks	2025/10/29	2025/10/29	high
361173	CentOS Linux 8.4 [TuxCare] 安全更新：bpftool / kernel / kernel-core / kernel-cross-headers / 等多个漏洞（CENTOS8.4：CLSA-2026：1771078945）	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
359273	Rocky Linux 8.6 [CIQ] 安全更新：bpftool / bpftool-debuginfo / kernel / kernel-abi-stablelists / 等多种漏洞（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

检测

插件搜索

high

high

high

high

high

high

high

high