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:21136 公告中提及的多个漏洞影响。

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

    安全修复：

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

    * kernel: ipv6：mcast：延迟将 pmc->idev 放在 mld_del_delrec() 中 (CVE-2025-38550)

    * 内核： sctp：线性化 sctp_rcv 中的克隆 gso 数据包（CVE-2025-38718）

    * 内核NFS修复更新现有写入时的争用 (CVE-2025-39697)

    * kernel: ipv6: sr : 将 MAC 比较修复为恒定时间 (CVE-2025-39702)

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

    * kernel: wifi: mac80211 : 检查 S1G 操作框架大小 (CVE-2023-53257)

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

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

    * kernel: mt76mt7921访问未分配的 eeprom.data 修复内核错误CVE-2023-53232

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

    * kernel: wifi: mwifiex : 修复 rx 打包时发生的 OOB 和整数下溢 (CVE-2023-53226)

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

    * kernel: pstore/ram：检查初始化期间空 przs 的起始位置 (CVE-2023-53331)

    * kernel: 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)

    * kernelmmkmem修复 obj_Stock_flush_required() 中的空指针取消引用 (CVE-2023-53401)

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

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

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

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

    * kernel: crypto: xts - 正确处理 EBUSY (CVE-2023-53494)

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

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

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

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

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

    安全修复：

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

    * kernel: wifi: mwifiex : 修复 rx 打包时发生的 OOB 和整数下溢 (CVE-2023-53226)

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

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

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

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

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

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

    安全修复：

    * kernel: ALSAusb-audio也验证 UAC3 电源域描述符 (CVE-2025-38729)

    * kernel：ALSA：usb-audio：验证 UAC3 群集段描述符 (CVE-2025-39757)

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

    - 内核：Bluetooth：L2CAP：修复 l2cap_disconnect_rsp 中的“解锁平衡错误”问题 [CVE-2023-53297]

    * kernelscsiqla2xxx等待 io 返回终止 rport (CVE-2023-53322)

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

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

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

    * 内核NFSD防范 NFSv2 READ 中的发送缓冲区溢出 (CVE-2022-50410)

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

    * 内核：tcp：清除 tcp_disconnect() 中的 tcp_sk(sk)->fastopen_rsk (CVE-2025-39955)

    有关上述安全问题的更多详细信息，包括其影响、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 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

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

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

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

    安全修复：

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

    * 内核NFS修复更新现有写入时的争用 (CVE-2025-39697)

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

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

    * kernel: mt76mt7921访问未分配的 eeprom.data 修复内核错误CVE-2023-53232

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

    * kernel: wifi: mwifiex : 修复 rx 打包时发生的 OOB 和整数下溢 (CVE-2023-53226)

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

    * kernel: pstore/ram：检查初始化期间空 przs 的起始位置 (CVE-2023-53331)

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

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

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

    * kernelmmkmem修复 obj_Stock_flush_required() 中的空指针取消引用 (CVE-2023-53401)

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

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

    * kernel: crypto: xts - 正确处理 EBUSY (CVE-2023-53494)

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

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

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

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

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

    安全修复：

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

    * kernel: ipv6：mcast：延迟将 pmc->idev 放在 mld_del_delrec() 中 (CVE-2025-38550)

    * 内核： sctp：线性化 sctp_rcv 中的克隆 gso 数据包（CVE-2025-38718）

    * 内核NFS修复更新现有写入时的争用 (CVE-2025-39697)

    * kernel: ipv6: sr : 将 MAC 比较修复为恒定时间 (CVE-2025-39702)

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

    * kernel: wifi: mac80211 : 检查 S1G 操作框架大小 (CVE-2023-53257)

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

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

    * kernel: mt76mt7921访问未分配的 eeprom.data 修复内核错误CVE-2023-53232

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

    * kernel: wifi: mwifiex : 修复 rx 打包时发生的 OOB 和整数下溢 (CVE-2023-53226)

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

    * kernel: pstore/ram：检查初始化期间空 przs 的起始位置 (CVE-2023-53331)

    * kernel: 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)

    * kernelmmkmem修复 obj_Stock_flush_required() 中的空指针取消引用 (CVE-2023-53401)

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

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

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

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

    * kernel: crypto: xts - 正确处理 EBUSY (CVE-2023-53494)

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

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

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

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

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

    安全修复：

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

    * 内核NFS修复更新现有写入时的争用 (CVE-2025-39697)

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

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

    * kernel: mt76mt7921访问未分配的 eeprom.data 修复内核错误CVE-2023-53232

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

    * kernel: wifi: mwifiex : 修复 rx 打包时发生的 OOB 和整数下溢 (CVE-2023-53226)

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

    * kernel: pstore/ram：检查初始化期间空 przs 的起始位置 (CVE-2023-53331)

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

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

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

    * kernelmmkmem修复 obj_Stock_flush_required() 中的空指针取消引用 (CVE-2023-53401)

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

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

    * kernel: crypto: xts - 正确处理 EBUSY (CVE-2023-53494)

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

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

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

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

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

    安全修复：

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

    * kernel: ethtool获取链接设置时检查设备是否存在 (CVE-2024-46679)

    * kernel: ALSAusb-audio也验证 UAC3 电源域描述符 (CVE-2025-38729)

    * 内核： sctp：线性化 sctp_rcv 中的克隆 gso 数据包（CVE-2025-38718）

    - nfsd：处理 nfsd4_setclientid_confirm() 中的 get_client_locked() 失败 (CVE-2025-38724)

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

    * kernel：ALSA：usb-audio：验证 UAC3 群集段描述符 (CVE-2025-39757)

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

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

    * kernel: wifi: mwifiex : 修复 rx 打包时发生的 OOB 和整数下溢 (CVE-2023-53226)

    - 内核：Bluetooth：L2CAP：修复 l2cap_disconnect_rsp 中的“解锁平衡错误”问题 [CVE-2023-53297]

    * kernel：smb：client：修复 rename(2) 操作中与并发打开争用的问题 (CVE-2025-39825)

    * 内核：efivarfs：修复 efivarfs_d_compare 中的 slab 越界问题 (CVE-2025-39817)

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

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

    * kernel: ip6mr修复 ip6mr_cache_report() 中的 skb_under_panic (CVE-2023-53365)

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

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

    * kernelRDMA/mlx5修复 mlx5_ib_get_hw_stats用于 设备时 (CVE-2023-53393)

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

    * 内核：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)

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

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

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

    * kernel：mm/memory-failure：修复在解除内存中毒时出现的 VM_BUG_ON_PAGE(PagePoisoned(page)) 问题 (CVE-2025-39883)

    * 内核NFSD避免在 ops->opnum == OP_ILLEGAL 的情况下调用 OPDESC() (CVE-2023-53680)

    * 内核：tcp：清除 tcp_disconnect() 中的 tcp_sk(sk)->fastopen_rsk (CVE-2025-39955)

    * 内核tcp不在 tcp_conn_request() 中调用 reqsk_fastopen_remove() (CVE-2025-40186)

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

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

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

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

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

    安全修复：

    * kernel: ethtool获取链接设置时检查设备是否存在 (CVE-2024-46679)

    * kernel: ALSAusb-audio也验证 UAC3 电源域描述符 (CVE-2025-38729)

    * 内核： sctp：线性化 sctp_rcv 中的克隆 gso 数据包（CVE-2025-38718）

    - nfsd：处理 nfsd4_setclientid_confirm() 中的 get_client_locked() 失败 (CVE-2025-38724)

    * kernel：ALSA：usb-audio：验证 UAC3 群集段描述符 (CVE-2025-39757)

    * kernel: wifi: mwifiex : 修复 rx 打包时发生的 OOB 和整数下溢 (CVE-2023-53226)

    - 内核：Bluetooth：L2CAP：修复 l2cap_disconnect_rsp 中的“解锁平衡错误”问题 [CVE-2023-53297]

    * kernelscsiqla2xxx等待 io 返回终止 rport (CVE-2023-53322)

    * kernel: ip6mr修复 ip6mr_cache_report() 中的 skb_under_panic (CVE-2023-53365)

    * kernelRDMA/mlx5修复 mlx5_ib_get_hw_stats用于 设备时 (CVE-2023-53393)

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

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

    * 内核：tcp：清除 tcp_disconnect() 中的 tcp_sk(sk)->fastopen_rsk (CVE-2025-39955)

    * 内核tcp不在 tcp_conn_request() 中调用 reqsk_fastopen_remove() (CVE-2025-40186)

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

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

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

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

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

    安全修复：

    * kernel: ALSAusb-audio也验证 UAC3 电源域描述符 (CVE-2025-38729)

    * kernel：ALSA：usb-audio：验证 UAC3 群集段描述符 (CVE-2025-39757)

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

    - 内核：Bluetooth：L2CAP：修复 l2cap_disconnect_rsp 中的“解锁平衡错误”问题 [CVE-2023-53297]

    * kernelscsiqla2xxx等待 io 返回终止 rport (CVE-2023-53322)

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

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

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

    * 内核NFSD防范 NFSv2 READ 中的发送缓冲区溢出 (CVE-2022-50410)

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

    * 内核：tcp：清除 tcp_disconnect() 中的 tcp_sk(sk)->fastopen_rsk (CVE-2025-39955)

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

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

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

Linux/Unix 主机中安装的一个或多个程序包受到一个漏洞影响，而供应商没有提供补丁程序。

  - iomapiomap修复回写期间记录错误时造成的内存损坏 我时常在 arm64 上看到此崩溃无法处理虚拟地址 00000000000000f8 处的内核空指针取消引用 dev dm-0逻辑块 8733687 上的 I/O 错误异步页读取内存中止信息ESR = 0x0000000096000006 EC = 0x25DABT当前 ELIL = 32 位 SET = 0FnV = 0 EA = 0S1PTW = 0FSC = 0x06级别 2 转换错误数据中止信息ISV = 0ISS = 0x00000006 CM = 0WnR = 0 用户 pgtable
    64k pages, 42-bit VAs, pgdp=0000000139750000 [00000000000000f8] pgd=0000000000000000、p4d=0000000000000000、 pud=0000000000000000、 pmd=0000000000000000 内部错误Oops: 96000006 [#1] PREEMPT SMP dev dm-0逻辑区块上的缓冲区 I/O 错误8733688异步页读取转储 ftrace 缓冲区
    设备 dm-0 上的缓冲区 I/O 错误逻辑区块 8733689异步页面读取ftrace 缓冲区为空XFS (dm-0)记录 I/O 错误 -5 中链接的模块dm_thin_pool dm_persistent_data XFS (dm-0)在 xfs_trans_read_buf_map+0x1ec/0x590 [xfs] (fs/xfs/xfs_trans_buf.c:296) 中检测到元数据 I/O 错误 (0x1)。 dm_bio_prison XFS (dm-0)请卸载文件系统并修正问题 XFS (dm-0)xfs_imap_lookup
    xfs_ialloc_read_agi() 返回错误 -5 agno 0 dm_bufio dm_log_writes xfs nft_chain_nat xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6t_REJECT 可能的意外致命信号 6。
    nf_reject_ipv6 潜在的意外致命信号 6. ipt_REJECT nf_reject_ipv4 CPU: 1 PID: 122166 Comm
    fsstress Tainted: GW 6.0.0-rc5-djwa #rc5 3004c9f1de887ebae86015f2677638ce51ee7 rpcsec_gss_krb5 auth_rpcgss xt_tcpudp ip_set_hash_ip ip_set_hash_net xt_set nft_compat ip_set_hash_mac ip_set nf_tables Hardware name: QEMU KVM Virtual Machine, BIOS 1.5.1 06/16/2021 pstate: 60001000 (nZCv daif -PAN -UAO -TCO
    -DIT +SSBS BTYPE=--) ip_tables pc : 000003fd6d7df200 x_tables lr : 000003fd6d7df1ec overlay nfsv4 CPU: 0 PID: 54031 Comm: u4:3 Tainted: GW 6.0.0-rc5-djwa #rc5 3004c9f1de887ebae86015f2677638ce51ee7405 Hardware name: QEMU KVM Virtual Machine 、BIOS 1.5.1 06/16/2021 Workqueue回写 wb_workfn sp : 000003ffd9522fd0 (flush-253:0) pstate: 60401005 (nZCv daif +PAN -UAO -TCO -DIT +SSBS BTYPE=--) pc : errseq_set+0x1c/ 0x100 x29000003ffd9522fd0 x280000000000000023 x27000002acefeb6780 x260000000000000005 x25
    0000000000000001 x24: 0000000000000000 x23: 00000000ffffffff x22: 0000000000000005 lr:
    __filemap_set_wb_err+0x24/0xe0 x21: 0000000000000006 sp : fffffe000f80f760 x29: fffffe000f80f760 x28
    0000000000000003 x27: fffffe000f80f9f8 x26: 0000000002523000 x25: 00000000fffffffb x24: fffffe000f80f868 x23: fffffe000f80fbb0 x22: fffffc0180c26a78 x21: 0000000002530000 x20: 0000000000000000 x19:
    0000000000000000 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 x14: 0000000000000001 x13: 0000000000470af3 x12: fffffc0058f70000 x11: 0000000000000040 x10:
    0000000000001b20 x9 : fffffe000836b288 x8 : fffffc00eb9fd480 x7 : 0000000000f83659 x6 : 0000000000000000 x5 : 0000000000000869 x4 : 0000000000000005 x3 : 00000000000000f8 x20: 000003fd6d740020 x19:
    000000000001dd36 x18: 0000000000000001 x17: 000003fd6d78704c x16: 0000000000000001 x15: 000002acfac87668 x2 : 0000000000000ffa x1 : 00000000fffffffb x0 : 00000000000000f8 Call trace: errseq_set+0x1c/0x100
    __filemap_set_wb_err+0x24/0xe0 iomap_do_writepage+0x5e4/0xd5c write_cache_pages+0x208/0x674 iomap_writepages+0x34/0x60 xfs_vm_writepages+0x8c/0xcc [xfs 7a861f39c43631f475d6ba15d3a5884248ca5803b]
    0000000000000000 x13: 2064656e72757465 x12: 0000000000002180 x11: 000003fd6d8a82d0 x10: 0000000000000000 x9 : 000003fd6d8ae288 x8 : 0000000000000083 x7 : 00000000ffffffff x6 : 00000000ffffffee x5 :
    00000000fbad2887 x4 : 000003fd6d9abb58 x3 : 000003fd6d740020 x2 : 0000000000000006 x1 : 000000000001dd36 x0 : 0000000000000000 CPU---truncated--- (CVE-2022-50406)

请注意，Nessus 依赖供应商报告的程序包是否存在进行判断。

AlmaLinux 9.2 主机上存在安装的程序包，该程序包受到 TuxCare ALMALINUX9.2：CLSA-2026：1786350974公告中提及的多个漏洞的影响。

  - 已修复 Linux 内核中的下列漏洞：isofs: Fix out of bound access for corrupted isofs image When isofs image is suitably corrupted isofs_read_inode() can read data beyond the end of buffer. Sanity-check the directory entry length before using it. (CVE-2021-47478)

  - 已修复 Linux 内核中的下列漏洞：ubi: Fix race condition between ctrl_cdev_ioctl and ubi_cdev_ioctl Hulk Robot reported a KASAN report about use-after-free:
    ================================================================== BUG: KASAN: use-after-free in
    __list_del_entry_valid+0x13d/0x160 Read of size 8 at addr ffff888035e37d98 by task ubiattach/1385 [...] Call Trace: klist_dec_and_del+0xa7/0x4a0 klist_put+0xc7/0x1a0 device_del+0x4d4/0xed0 cdev_device_del+0x1a/0x80 ubi_attach_mtd_dev+0x2951/0x34b0 [ubi] ctrl_cdev_ioctl+0x286/0x2f0 [ubi] Allocated by task 1414: device_add+0x60a/0x18b0 cdev_device_add+0x103/0x170 ubi_create_volume+0x1118/0x1a10 [ubi] ubi_cdev_ioctl+0xb7f/0x1ba0 [ubi] Freed by task 1385:
    cdev_device_del+0x1a/0x80 ubi_remove_volume+0x438/0x6c0 [ubi] ubi_cdev_ioctl+0xbf4/0x1ba0 [ubi] [...] ================================================================== The lock held by ctrl_cdev_ioctl is ubi_devices_mutex, but the lock held by ubi_cdev_ioctl is ubi->device_mutex. Therefore, the two locks can be concurrent. ctrl_cdev_ioctl contains two operations: ubi_attach and ubi_detach. ubi_detach is bug-free because it uses reference counting to prevent concurrency. However, uif_init and uif_close in ubi_attach may race with ubi_cdev_ioctl. uif_init will race with ubi_cdev_ioctl as in the following stack. cpu1 cpu2 cpu3 _______________________|________________________|______________________ ctrl_cdev_ioctl ubi_attach_mtd_dev uif_init ubi_cdev_ioctl ubi_create_volume cdev_device_add ubi_add_volume // sysfs exist kill_volumes ubi_cdev_ioctl ubi_remove_volume cdev_device_del // first free ubi_free_volume cdev_del // double free cdev_device_del And uif_close will race with ubi_cdev_ioctl as in the following stack. cpu1 cpu2 cpu3 _______________________|________________________|______________________ ctrl_cdev_ioctl ubi_attach_mtd_dev uif_init ubi_cdev_ioctl ubi_create_volume cdev_device_add ubi_debugfs_init_dev //error goto out_uif; uif_close kill_volumes ubi_cdev_ioctl ubi_remove_volume cdev_device_del // first free ubi_free_volume // double free The cause of this problem is that commit 714fb87e8bc0 make device available before it becomes accessible via sysfs. Therefore, we roll back the modification. We will fix the race condition between ubi device creation and udev by removing ubi_get_device in vol_attribute_show and dev_attribute_show.This avoids accessing uninitialized ubi_devices[ubi_num]. ubi_get_device is used to prevent devices from being deleted during sysfs execution. However, now kernfs ensures that devices will not be deleted before all reference counting are released. The key process is shown in the following stack. device_del device_remove_attrs device_remove_groups sysfs_remove_groups sysfs_remove_group remove_files kernfs_remove_by_name kernfs_remove_by_name_ns __kernfs_remove kernfs_drain (CVE-2021-47634)

  - 已修复 Linux 内核中的下列漏洞：scsi: qla2xxx: Fix memory leak in
    __qlt_24xx_handle_abts() Commit 8f394da36a36 (scsi: qla2xxx: Drop TARGET_SCF_LOOKUP_LUN_FROM_TAG) made the __qlt_24xx_handle_abts() function return early if tcm_qla2xxx_find_cmd_by_tag() didn't find a command, but it missed to clean up the allocated memory for the management command. (CVE-2022-48650)

  - 已修复 Linux 内核中的下列漏洞：ubi: ubi_create_volume: Fix use-after-free when volume creation failed There is an use-after-free problem for 'eba_tbl' in ubi_create_volume()'s error handling path: ubi_eba_replace_table(vol, eba_tbl) vol->eba_tbl = tbl out_mapping:
    ubi_eba_destroy_table(eba_tbl) // Free 'eba_tbl' out_unlock: put_device(&vol->dev) vol_release kfree(tbl->entries) // UAF Fix it by removing redundant 'eba_tbl' releasing. Fetch a reproducer in [Link].
    (CVE-2022-49388)

  - 已修复 Linux 内核中的下列漏洞：irqchip/gic-v3: Fix error handling in gic_populate_ppi_partitions of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. When kcalloc fails, it missing of_node_put() and results in refcount leak. Fix this by goto out_put_node label. (CVE-2022-49716)

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

CentOS Linux 7 主机上存在安装的程序包，该程序包受到 TuxCare CENTOS7：CLSA-2026：2026：1770040438 1 公告中提及的多个漏洞的影响。

  - 已修复 Linux 内核中的下列漏洞：cifs: fix oops during encryption When running xfstests against Azure the following oops occurred on an arm64 system Unable to handle kernel write to read-only memory at virtual address ffff0001221cf000 Mem abort info: ESR = 0x9600004f EC = 0x25:
    DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x0f: level 3 permission fault Data abort info: ISV = 0, ISS = 0x0000004f CM = 0, WnR = 1 swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000294f3000 [ffff0001221cf000] pgd=18000001ffff8003, p4d=18000001ffff8003, pud=18000001ff82e003, pmd=18000001ff71d003, pte=00600001221cf787 Internal error: Oops: 9600004f [#1] PREEMPT SMP ... pstate:
    80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--) pc : __memcpy+0x40/0x230 lr :
    scatterwalk_copychunks+0xe0/0x200 sp : ffff800014e92de0 x29: ffff800014e92de0 x28: ffff000114f9de80 x27:
    0000000000000008 x26: 0000000000000008 x25: ffff800014e92e78 x24: 0000000000000008 x23: 0000000000000001 x22: 0000040000000000 x21: ffff000000000000 x20: 0000000000000001 x19: ffff0001037c4488 x18:
    0000000000000014 x17: 235e1c0d6efa9661 x16: a435f9576b6edd6c x15: 0000000000000058 x14: 0000000000000001 x13: 0000000000000008 x12: ffff000114f2e590 x11: ffffffffffffffff x10: 0000040000000000 x9 :
    ffff8000105c3580 x8 : 2e9413b10000001a x7 : 534b4410fb86b005 x6 : 534b4410fb86b005 x5 : ffff0001221cf008 x4 : ffff0001037c4490 x3 : 0000000000000001 x2 : 0000000000000008 x1 : ffff0001037c4488 x0 :
    ffff0001221cf000 Call trace: __memcpy+0x40/0x230 scatterwalk_map_and_copy+0x98/0x100 crypto_ccm_encrypt+0x150/0x180 crypto_aead_encrypt+0x2c/0x40 crypt_message+0x750/0x880 smb3_init_transform_rq+0x298/0x340 smb_send_rqst.part.11+0xd8/0x180 smb_send_rqst+0x3c/0x100 compound_send_recv+0x534/0xbc0 smb2_query_info_compound+0x32c/0x440 smb2_set_ea+0x438/0x4c0 cifs_xattr_set+0x5d4/0x7c0 This is because in scatterwalk_copychunks(), we attempted to write to a buffer (@sign) that was allocated in the stack (vmalloc area) by crypt_message() and thus accessing its remaining 8 (x2) bytes ended up crossing a page boundary. To simply fix it, we could just pass @sign kmalloc'd from crypt_message() and then we're done. Luckily, we don't seem to pass any other vmalloc'd buffers in smb_rqst::rq_iov... Instead, let's map the correct pages and offsets from vmalloc buffers as well in cifs_sg_set_buf() and then avoiding such oopses. (CVE-2022-50341)

  - 已修复 Linux 内核中的下列漏洞：iomap: iomap: fix memory corruption when recording errors during writeback Every now and then I see this crash on arm64: Unable to handle kernel NULL pointer dereference at virtual address 00000000000000f8 Buffer I/O error on dev dm-0, logical block 8733687, async page read Mem abort info: ESR = 0x0000000096000006 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x06: level 2 translation fault Data abort info: ISV = 0, ISS = 0x00000006 CM = 0, WnR = 0 user pgtable: 64k pages, 42-bit VAs, pgdp=0000000139750000 [00000000000000f8] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000, pmd=0000000000000000 Internal error: Oops: 96000006 [#1] PREEMPT SMP Buffer I/O error on dev dm-0, logical block 8733688, async page read Dumping ftrace buffer: Buffer I/O error on dev dm-0, logical block 8733689, async page read (ftrace buffer empty) XFS (dm-0): log I/O error -5 Modules linked in: dm_thin_pool dm_persistent_data XFS (dm-0): Metadata I/O Error (0x1) detected at xfs_trans_read_buf_map+0x1ec/0x590 [xfs] (fs/xfs/xfs_trans_buf.c:296). dm_bio_prison XFS (dm-0): Please unmount the filesystem and rectify the problem(s) XFS (dm-0): xfs_imap_lookup: xfs_ialloc_read_agi() returned error -5, agno 0 dm_bufio dm_log_writes xfs nft_chain_nat xt_REDIRECT nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6t_REJECT potentially unexpected fatal signal 6. nf_reject_ipv6 potentially unexpected fatal signal 6. ipt_REJECT nf_reject_ipv4 CPU: 1 PID: 122166 Comm: fsstress Tainted: G W 6.0.0-rc5-djwa #rc5 3004c9f1de887ebae86015f2677638ce51ee7 rpcsec_gss_krb5 auth_rpcgss xt_tcpudp ip_set_hash_ip ip_set_hash_net xt_set nft_compat ip_set_hash_mac ip_set nf_tables Hardware name: QEMU KVM Virtual Machine, BIOS 1.5.1 06/16/2021 pstate: 60001000 (nZCv daif -PAN -UAO -TCO -DIT +SSBS BTYPE=--) ip_tables pc : 000003fd6d7df200 x_tables lr : 000003fd6d7df1ec overlay nfsv4 CPU: 0 PID: 54031 Comm: u4:3 Tainted: G W 6.0.0-rc5-djwa #rc5 3004c9f1de887ebae86015f2677638ce51ee7405 Hardware name: QEMU KVM Virtual Machine, BIOS 1.5.1 06/16/2021 Workqueue: writeback wb_workfn sp : 000003ffd9522fd0 (flush-253:0) pstate: 60401005 (nZCv daif +PAN -UAO
    -TCO -DIT +SSBS BTYPE=--) pc : errseq_set+0x1c/0x100 x29: 000003ffd9522fd0 x28: 0000000000000023 x27:
    000002acefeb6780 x26: 0000000000000005 x25: 0000000000000001 x24: 0000000000000000 x23: 00000000ffffffff x22: 0000000000000005 lr : __filemap_set_wb_err+0x24/0xe0 x21: 0000000000000006 sp : fffffe000f80f760 x29:
    fffffe000f80f760 x28: 0000000000000003 x27: fffffe000f80f9f8 x26: 0000000002523000 x25: 00000000fffffffb x24: fffffe000f80f868 x23: fffffe000f80fbb0 x22: fffffc0180c26a78 x21: 0000000002530000 x20:
    0000000000000000 x19: 0000000000000000 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 x14: 0000000000000001 x13: 0000000000470af3 x12: fffffc0058f70000 x11:
    0000000000000040 x10: 0000000000001b20 x9 : fffffe000836b288 x8 : fffffc00eb9fd480 x7 : 0000000000f83659 x6 : 0000000000000000 x5 : 0000000000000869 x4 : 0000000000000005 x3 : 00000000000000f8 x20:
    000003fd6d740020 x19: 000000000001dd36 x18: 0000000000000001 x17: 000003fd6d78704c x16: 0000000000000001 x15: 000002acfac87668 x2 : 0000000000000ffa x1 : 00000000fffffffb x0 : 00000000000000f8 Call trace:
    errseq_set+0x1c/0x100 __filemap_set_wb_err+0x24/0xe0 iomap_do_writepage+0x5e4/0xd5c write_cache_pages+0x208/0x674 iomap_writepages+0x34/0x60 xfs_vm_writepages+0x8c/0xcc [xfs 7a861f39c43631f15d3a5884246ba5035d4ca78b] x14: 0000000000000000 x13: 2064656e72757465 x12:
    0000000000002180 x11: 000003fd6d8a82d0 x10: 0000000000000000 x9 : 000003fd6d8ae288 x8 : 0000000000000083 x7 : 00000000ffffffff x6 : 00000000ffffffee x5 : 00000000fbad2887 x4 : 000003fd6d9abb58 x3 :
    000003fd6d740020 x2 : 0000000000000006 x1 : 000000000001dd36 x0 : 0000000000000000 CPU: ---truncated--- (CVE-2022-50406)

  - 已修复 Linux 内核中的下列漏洞：Bluetooth: hci_sysfs: Fix attempting to call device_add multiple times device_add shall not be called multiple times as stated in its documentation: 'Do not call this routine or device_register() more than once for any device structure' Syzkaller reports a bug as follows [1]: ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:33! invalid opcode: 0000 [#1] PREEMPT SMP KASAN [...] Call Trace: <TASK> __list_add include/linux/list.h:69 [inline] list_add_tail include/linux/list.h:102 [inline] kobj_kset_join lib/kobject.c:164 [inline] kobject_add_internal+0x18f/0x8f0 lib/kobject.c:214 kobject_add_varg lib/kobject.c:358 [inline] kobject_add+0x150/0x1c0 lib/kobject.c:410 device_add+0x368/0x1e90 drivers/base/core.c:3452 hci_conn_add_sysfs+0x9b/0x1b0 net/bluetooth/hci_sysfs.c:53 hci_le_cis_estabilished_evt+0x57c/0xae0 net/bluetooth/hci_event.c:6799 hci_le_meta_evt+0x2b8/0x510 net/bluetooth/hci_event.c:7110 hci_event_func net/bluetooth/hci_event.c:7440 [inline] hci_event_packet+0x63d/0xfd0 net/bluetooth/hci_event.c:7495 hci_rx_work+0xae7/0x1230 net/bluetooth/hci_core.c:4007 process_one_work+0x991/0x1610 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e4/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 </TASK> (CVE-2022-50419)

  - 已修复 Linux 内核中的下列漏洞：scsi: libsas: Fix use-after-free bug in smp_execute_task_sg() When executing SMP task failed, the smp_execute_task_sg() calls del_timer() to delete slow_task->timer. However, if the timer handler sas_task_internal_timedout() is running, the del_timer() in smp_execute_task_sg() will not stop it and a UAF will happen. The process is shown below:
    (thread 1) | (thread 2) smp_execute_task_sg() | sas_task_internal_timedout() ... | del_timer() | ... | ...
    sas_free_task(task) | kfree(task->slow_task) //FREE| | task->slow_task->... //USE Fix by calling del_timer_sync() in smp_execute_task_sg(), which makes sure the timer handler have finished before the task->slow_task is deallocated. (CVE-2022-50422)

  - 已修复 Linux 内核中的下列漏洞：scsi: lpfc: Fix use-after-free KFENCE violation during sysfs firmware write During the sysfs firmware write process, a use-after-free read warning is logged from the lpfc_wr_object() routine: BUG: KFENCE: use-after-free read in lpfc_wr_object+0x235/0x310 [lpfc] Use-after-free read at 0x0000000000cf164d (in kfence-#111):
    lpfc_wr_object+0x235/0x310 [lpfc] lpfc_write_firmware.cold+0x206/0x30d [lpfc] lpfc_sli4_request_firmware_update+0xa6/0x100 [lpfc] lpfc_request_firmware_upgrade_store+0x66/0xb0 [lpfc] kernfs_fop_write_iter+0x121/0x1b0 new_sync_write+0x11c/0x1b0 vfs_write+0x1ef/0x280 ksys_write+0x5f/0xe0 do_syscall_64+0x59/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd The driver accessed wr_object pointer data, which was initialized into mailbox payload memory, after the mailbox object was released back to the mailbox pool. Fix by moving the mailbox free calls to the end of the routine ensuring that we don't reference internal mailbox memory after release. (CVE-2023-53282)

请注意，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
275173	RHEL 9：kernel-rt (RHSA-2025:21136)	Nessus	Red Hat Local Security Checks	2025/11/12	2025/11/12	high
278028	RHEL 8：内核 (RHSA-2025:22998)	Nessus	Red Hat Local Security Checks	2025/12/10	2026/2/25	high
279558	RHEL 7：内核 (RHSA-2025:23947)	Nessus	Red Hat Local Security Checks	2025/12/22	2026/2/20	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 / 等多个漏洞（CENTOS8.4：CLSA-2026：1771078945）	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/1	high
274937	RHEL 9：内核 (RHSA-2025:21051)	Nessus	Red Hat Local Security Checks	2025/11/12	2025/11/12	high
275174	RHEL 9：内核 (RHSA-2025:21091)	Nessus	Red Hat Local Security Checks	2025/11/12	2025/11/12	high
275176	RHEL 9：kernel-rt (RHSA-2025:21128)	Nessus	Red Hat Local Security Checks	2025/11/12	2025/11/12	high
278950	RHEL 8：内核 (RHSA-2025:23445)	Nessus	Red Hat Local Security Checks	2025/12/17	2025/12/17	high
279030	RHEL 8：内核 (RHSA-2025:23463)	Nessus	Red Hat Local Security Checks	2025/12/17	2026/2/23	high
279557	RHEL 7：kernel-rt (RHSA-2025:23960)	Nessus	Red Hat Local Security Checks	2025/12/22	2026/2/20	high
265505	Linux Distros 未修补的漏洞：CVE-2022-50406	Nessus	Misc.	2025/9/19	2026/9/30	high
360716	AlmaLinux 9.2 [TuxCare] 安全更新：bpftool / kernel / kernel-abi-stablelists / kernel-core / 等多个漏洞（ALMALINUX9.2：CLSA-2026：1786350974）	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/1	high
360828	CentOS Linux 7 [TuxCare] 安全更新：bpftool / kernel / kernel-debug / kernel-debug-devel / kernel-devel / 等多个漏洞（CENTOS7：CLSA-2026：1770040438）	Nessus	CentOS Local Security Checks	2026/10/1	2026/10/1	high

检测

插件搜索

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high