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

  - 已修复 Linux 内核中的下列漏洞：net/mlx5: HWS, change error flow on matcher disconnect Currently, when firmware failure occurs during matcher disconnect flow, the error flow of the function reconnects the matcher back and returns an error, which continues running the calling function and eventually frees the matcher that is being disconnected. This leads to a case where we have a freed matcher on the matchers list, which in turn leads to use-after-free and eventual crash. This patch fixes that by not trying to reconnect the matcher back when some FW command fails during disconnect. Note that we're dealing here with FW error. We can't overcome this problem. This might lead to bad steering state (e.g. wrong connection between matchers), and will also lead to resource leakage, as it is the case with any other error handling during resource destruction. However, the goal here is to allow the driver to continue and not crash the machine with use-after-free error. (CVE-2025-21751)

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

Rocky Linux 9.6 主机上存在安装的程序包，该程序包受到 TuxCare ALMALINUX9.6：CLSA-2026：2026：1789986443公告中提及的多个漏洞的影响。

  - 已修复 Linux 内核中的下列漏洞：net: hns3: add vlan list lock to protect vlan list When adding port base VLAN, vf VLAN need to remove from HW and modify the vlan state in vf VLAN list as false. If the periodicity task is freeing the same node, it may cause use after free error. This patch adds a vlan list lock to protect the vlan list. (CVE-2022-49182)

  - 已修复 Linux 内核中的下列漏洞：tracing: Fix reading strings from synthetic events The follow commands caused a crash: # cd /sys/kernel/tracing # echo 's:open char file[]' > dynamic_events # echo 'hist:keys=common_pid:file=filename:onchange($file).trace(open,$file)' > events/syscalls/sys_enter_openat/trigger' # echo 1 > events/synthetic/open/enable BOOM! The problem is that the synthetic event field char file[] will read the value given to it as a string without any memory checks to make sure the address is valid. The above example will pass in the user space address and the sythetic event code will happily call strlen() on it and then strscpy() where either one will cause an oops when accessing user space addresses. Use the helper functions from trace_kprobe and trace_eprobe that can read strings safely (and actually succeed when the address is from user space and the memory is mapped in). Now the above can show: packagekitd-1721 [000] ...2. 104.597170: open:
    file=/usr/lib/rpm/fileattrs/cmake.attr in:imjournal-978 [006] ...2. 104.599642: open:
    file=/var/lib/rsyslog/imjournal.state.tmp packagekitd-1721 [000] ...2. 104.626308: open:
    file=/usr/lib/rpm/fileattrs/debuginfo.attr (CVE-2022-50255)

  - 已修复 Linux 内核中的下列漏洞：ipc: fix memleak if msg_init_ns failed in create_ipc_ns Percpu memory allocation may failed during create_ipc_ns however this fail is not handled properly since ipc sysctls and mq sysctls is not released properly. Fix this by release these two resource when failure. Here is the kmemleak stack when percpu failed: unreferenced object 0xffff88819de2a600 (size 512): comm shmem_2nstest, pid 120711, jiffies 4300542254 hex dump (first 32 bytes): 60 aa 9d 84 ff ff ff ff fc 18 48 b2 84 88 ff ff `.........H..... 04 00 00 00 a4 01 00 00 20 e4 56 81 ff ff ff ff ........
    .V..... backtrace (crc be7cba35): [<ffffffff81b43f83>] __kmalloc_node_track_caller_noprof+0x333/0x420 [<ffffffff81a52e56>] kmemdup_noprof+0x26/0x50 [<ffffffff821b2f37>] setup_mq_sysctls+0x57/0x1d0 [<ffffffff821b29cc>] copy_ipcs+0x29c/0x3b0 [<ffffffff815d6a10>] create_new_namespaces+0x1d0/0x920 [<ffffffff815d7449>] copy_namespaces+0x2e9/0x3e0 [<ffffffff815458f3>] copy_process+0x29f3/0x7ff0 [<ffffffff8154b080>] kernel_clone+0xc0/0x650 [<ffffffff8154b6b1>] __do_sys_clone+0xa1/0xe0 [<ffffffff843df8ff>] do_syscall_64+0xbf/0x1c0 [<ffffffff846000b0>] entry_SYSCALL_64_after_hwframe+0x4b/0x53 (CVE-2024-53175)

  - 已修复 Linux 内核中的下列漏洞：net/mlx5: HWS, change error flow on matcher disconnect Currently, when firmware failure occurs during matcher disconnect flow, the error flow of the function reconnects the matcher back and returns an error, which continues running the calling function and eventually frees the matcher that is being disconnected. This leads to a case where we have a freed matcher on the matchers list, which in turn leads to use-after-free and eventual crash. This patch fixes that by not trying to reconnect the matcher back when some FW command fails during disconnect. Note that we're dealing here with FW error. We can't overcome this problem. This might lead to bad steering state (e.g. wrong connection between matchers), and will also lead to resource leakage, as it is the case with any other error handling during resource destruction. However, the goal here is to allow the driver to continue and not crash the machine with use-after-free error. (CVE-2025-21751)

  - 已修复 Linux 内核中的下列漏洞：wifi: ath12k: Avoid memory leak while enabling statistics Driver uses monitor destination rings for extended statistics mode and standalone monitor mode. In extended statistics mode, TLVs are parsed from the buffer received from the monitor destination ring and assigned to the ppdu_info structure to update per-packet statistics. In standalone monitor mode, along with per-packet statistics, the packet data (payload) is captured, and the driver updates per MSDU to mac80211. When the AP interface is enabled, only extended statistics mode is activated. As part of enabling monitor rings for collecting statistics, the driver subscribes to HAL_RX_MPDU_START TLV in the filter configuration. This TLV is received from the monitor destination ring, and kzalloc for the mon_mpdu object occurs, which is not freed, leading to a memory leak. The kzalloc for the mon_mpdu object is only required while enabling the standalone monitor interface. This causes a memory leak while enabling extended statistics mode in the driver. Fix this memory leak by removing the kzalloc for the mon_mpdu object in the HAL_RX_MPDU_START TLV handling. Additionally, remove the standalone monitor mode handlings in the HAL_MON_BUF_ADDR and HAL_RX_MSDU_END TLVs. These TLV tags will be handled properly when enabling standalone monitor mode in the future. Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1 Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 (CVE-2025-37743)

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

因此，该软件受到 ALAS2023-2025-948 公告中提及的多个漏洞影响。

    在 Linux 内核中，以下漏洞已修复：

    PCI/ASPM：修复在移除交换机上游功能期间退出链路状态的问题 (CVE-2024-58093)

    在 Linux 内核中，以下漏洞已修复：

    net/mlx5：HWS，更改匹配程序断开连接时的错误流 (CVE-2025-21751)

    在 Linux 内核中，以下漏洞已修复：

    nfsd：修复监听器传输的管理 (CVE-2025-22024)

    在 Linux 内核中，以下漏洞已修复：

    nfsd：如果无法将 dl_recall 排入队列，则放置 dl_stid (CVE-2025-22025)

    在 Linux 内核中，以下漏洞已修复：

    media：streamzap：修复设备断开连接和 urb 回调之间的争用 (CVE-2025-22027)

    在 Linux 内核中，以下漏洞已修复：

    mm：zswap：修复 zswap_cpu_comp_dead() 中的 crypto_free_acomp() 死锁 (CVE-2025-22030)

    在 Linux 内核中，以下漏洞已修复：

    arm64：不调用 do_compat_alignment_fixup() 中的 NULL (CVE-2025-22033)

    在 Linux 内核中，以下漏洞已修复：

    mm/gup：拒绝使用 hugetlb VMAs 的 FOLL_SPLIT_PMD (CVE-2025-22034)

    在 Linux 内核中，以下漏洞已修复：

    tracing: 修复切换跟踪程序期间 print_graph_function_flags 中的释放后使用问题 (CVE-2025-22035)

    在 Linux 内核中，以下漏洞已修复：

    exfat: 修复 get_block 之后的随机堆栈损坏 (CVE-2025-22036)

    在 Linux 内核中，以下漏洞已修复：

    acpi：nfit：修复了 acpi_nfit_ctl 中的窄化转换 (CVE-2025-22044)

    在 Linux 内核中，以下漏洞已修复：

    x86/mm：修复用于快速切换正常 PMD 时的 flush_tlb_range() (CVE-2025-22045)

    在 Linux 内核中，以下漏洞已修复：

    uprobes/x86：强化 uretprobe syscall trampoline 检查 (CVE-2025-22046)

    在 Linux 内核中，以下漏洞已修复：

    x86/microcode/AMD：修复 __apply_microcode_amd() 的返回值 (CVE-2025-22047)

    在 Linux 内核中，以下漏洞已修复：

    net：修复 geneve_opt 长度整数溢出 (CVE-2025-22055)

    在 Linux 内核中，以下漏洞已修复：

    netfilter: nft_tunnel: 修复 geneve_opt 类型混淆添加问题 (CVE-2025-22056)

    在 Linux 内核中，以下漏洞已修复：

    net：减少 dst_release 中缓存的 dst 计数器 (CVE-2025-22057)

    在 Linux 内核中，以下漏洞已修复：

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

    在 Linux 内核中，以下漏洞已修复：

    udp：修复 sk->sk_rmem_alloc 的多个回绕。(CVE-2025-22059)

    在 Linux 内核中，以下漏洞已修复：

    sctp：在 proc_sctp_do_udp_port() 中添加互斥 (CVE-2025-22062)

    在 Linux 内核中，以下漏洞已修复：

    netlabel：修复 IPv4 套接字上的 CALIPSO 造成的空指针异常 (CVE-2025-22063)

    在 Linux 内核中，以下漏洞已修复：

    netfilter：nf_tables：表休眠时不取消注册挂钩 (CVE-2025-22064)

    在 Linux 内核中，以下漏洞已修复：

    rtnetlink：支持时为 VF GUID 分配 vfinfo 大小 (CVE-2025-22075)

    在 Linux 内核中，以下漏洞已修复：

    exfat：修复缺少的关机检查 (CVE-2025-22076)

    在 Linux 内核中，以下漏洞已修复：

    fs/ntfs3：防止 hdr_first_de() 中的整数溢出 (CVE-2025-22080)

    在 Linux 内核中，以下漏洞已修复：

    fs/ntfs3：修复 32 位系统中的几个整数溢出 (CVE-2025-22081)

    在 Linux 内核中，以下漏洞已修复：

    RDMA/core：修复重命名设备名称时的释放后使用 (CVE-2025-22085)

    在 Linux 内核中，以下漏洞已修复：

    RDMA/mlx5：修复 mlx5_poll_one() cur_qp 更新流 (CVE-2025-22086)

    在 Linux 内核中，以下漏洞已修复：

    bpf：修复 may_goto 的数组边界错误 (CVE-2025-22087)

    在 Linux 内核中，以下漏洞已修复：

    RDMA/core：不要在 init net 命名空间之外暴露 hw_counters (CVE-2025-22089)

    在 Linux 内核中，以下漏洞已修复：

    x86/mm/pat：修复 fork() 在 copy_page_range() 中失败时的 VM_PAT 处理 (CVE-2025-22090)

    在 Linux 内核中，以下漏洞已修复：

    RDMA/mlx5：修复 page_size 变量溢出 (CVE-2025-22091)

    在 Linux 内核中，以下漏洞已修复：

    thermal：int340x：添加对 adev 的空检查 (CVE-2025-23136)

    在 Linux 内核中，以下漏洞已修复：

    watch_queue：修复管道核算不匹配 (CVE-2025-23138)

    在 Linux 内核中，以下漏洞已修复：

    ext4: 修复检查 dotdot 目录时出现的 OOB 读取问题 (CVE-2025-37785)

    在 Linux 内核中，以下漏洞已修复：

    net_sched：skbprio：删除过于严格的队列断言 (CVE-2025-38637)

    在 Linux 内核中，以下漏洞已修复：

    nfsd：通过 nfs4_lookup_stateid() 搜索时允许 SC_STATUS_FREEABLE (CVE-2025-39688)

    在 Linux 内核中，以下漏洞已修复：

    x86/mce：使用 is_copy_from_user() 确定 copy-from-user 上下文 (CVE-2025-39989)

Tenable 已直接从测试产品的安全公告中提取上述描述块。

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

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

  - 已修复 Linux 内核中的下列漏洞：net: hns3: add vlan list lock to protect vlan list When adding port base VLAN, vf VLAN need to remove from HW and modify the vlan state in vf VLAN list as false. If the periodicity task is freeing the same node, it may cause use after free error. This patch adds a vlan list lock to protect the vlan list. (CVE-2022-49182)

  - 已修复 Linux 内核中的下列漏洞：tracing: Fix reading strings from synthetic events The follow commands caused a crash: # cd /sys/kernel/tracing # echo 's:open char file[]' > dynamic_events # echo 'hist:keys=common_pid:file=filename:onchange($file).trace(open,$file)' > events/syscalls/sys_enter_openat/trigger' # echo 1 > events/synthetic/open/enable BOOM! The problem is that the synthetic event field char file[] will read the value given to it as a string without any memory checks to make sure the address is valid. The above example will pass in the user space address and the sythetic event code will happily call strlen() on it and then strscpy() where either one will cause an oops when accessing user space addresses. Use the helper functions from trace_kprobe and trace_eprobe that can read strings safely (and actually succeed when the address is from user space and the memory is mapped in). Now the above can show: packagekitd-1721 [000] ...2. 104.597170: open:
    file=/usr/lib/rpm/fileattrs/cmake.attr in:imjournal-978 [006] ...2. 104.599642: open:
    file=/var/lib/rsyslog/imjournal.state.tmp packagekitd-1721 [000] ...2. 104.626308: open:
    file=/usr/lib/rpm/fileattrs/debuginfo.attr (CVE-2022-50255)

  - 已修复 Linux 内核中的下列漏洞：ipc: fix memleak if msg_init_ns failed in create_ipc_ns Percpu memory allocation may failed during create_ipc_ns however this fail is not handled properly since ipc sysctls and mq sysctls is not released properly. Fix this by release these two resource when failure. Here is the kmemleak stack when percpu failed: unreferenced object 0xffff88819de2a600 (size 512): comm shmem_2nstest, pid 120711, jiffies 4300542254 hex dump (first 32 bytes): 60 aa 9d 84 ff ff ff ff fc 18 48 b2 84 88 ff ff `.........H..... 04 00 00 00 a4 01 00 00 20 e4 56 81 ff ff ff ff ........
    .V..... backtrace (crc be7cba35): [<ffffffff81b43f83>] __kmalloc_node_track_caller_noprof+0x333/0x420 [<ffffffff81a52e56>] kmemdup_noprof+0x26/0x50 [<ffffffff821b2f37>] setup_mq_sysctls+0x57/0x1d0 [<ffffffff821b29cc>] copy_ipcs+0x29c/0x3b0 [<ffffffff815d6a10>] create_new_namespaces+0x1d0/0x920 [<ffffffff815d7449>] copy_namespaces+0x2e9/0x3e0 [<ffffffff815458f3>] copy_process+0x29f3/0x7ff0 [<ffffffff8154b080>] kernel_clone+0xc0/0x650 [<ffffffff8154b6b1>] __do_sys_clone+0xa1/0xe0 [<ffffffff843df8ff>] do_syscall_64+0xbf/0x1c0 [<ffffffff846000b0>] entry_SYSCALL_64_after_hwframe+0x4b/0x53 (CVE-2024-53175)

  - 已修复 Linux 内核中的下列漏洞：net/mlx5: HWS, change error flow on matcher disconnect Currently, when firmware failure occurs during matcher disconnect flow, the error flow of the function reconnects the matcher back and returns an error, which continues running the calling function and eventually frees the matcher that is being disconnected. This leads to a case where we have a freed matcher on the matchers list, which in turn leads to use-after-free and eventual crash. This patch fixes that by not trying to reconnect the matcher back when some FW command fails during disconnect. Note that we're dealing here with FW error. We can't overcome this problem. This might lead to bad steering state (e.g. wrong connection between matchers), and will also lead to resource leakage, as it is the case with any other error handling during resource destruction. However, the goal here is to allow the driver to continue and not crash the machine with use-after-free error. (CVE-2025-21751)

  - 已修复 Linux 内核中的下列漏洞：wifi: ath12k: Avoid memory leak while enabling statistics Driver uses monitor destination rings for extended statistics mode and standalone monitor mode. In extended statistics mode, TLVs are parsed from the buffer received from the monitor destination ring and assigned to the ppdu_info structure to update per-packet statistics. In standalone monitor mode, along with per-packet statistics, the packet data (payload) is captured, and the driver updates per MSDU to mac80211. When the AP interface is enabled, only extended statistics mode is activated. As part of enabling monitor rings for collecting statistics, the driver subscribes to HAL_RX_MPDU_START TLV in the filter configuration. This TLV is received from the monitor destination ring, and kzalloc for the mon_mpdu object occurs, which is not freed, leading to a memory leak. The kzalloc for the mon_mpdu object is only required while enabling the standalone monitor interface. This causes a memory leak while enabling extended statistics mode in the driver. Fix this memory leak by removing the kzalloc for the mon_mpdu object in the HAL_RX_MPDU_START TLV handling. Additionally, remove the standalone monitor mode handlings in the HAL_MON_BUF_ADDR and HAL_RX_MSDU_END TLVs. These TLV tags will be handled properly when enabling standalone monitor mode in the future. Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1 Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 (CVE-2025-37743)

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

远程 Debian 13 主机上存在安装的程序包该程序包受到 dsa-6008 公告中提及的多个漏洞的影响。

    - ------------------------------------------------- ------------------------ Debian 安全公告 DSA-6008-1 security@debian.org https://www.debian.org/security/Salvatore Bonaccorso 2025 年 9 月 22 日 https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    程序包：linux CVE ID：CVE-2025-21751 CVE-2025-22103 CVE-2025-22113 CVE-2025-22124 CVE-2025-22125 CVE-2025-23133 CVE-2025-38272 CVE-2025-38306 CVE-2025-38453 CVE-2025-38502 CVE-2025-38556 CVE-2025-38676 CVE-2025-38677 CVE-2025-38730 CVE-2025-38732 CVE-2025-38733 CVE-2025-38734 CVE-2025-38735 CVE-2025-38736 CVE-2025-38737 CVE-2025-39673 CVE-2025-39675 CVE-2025-39676 CVE-2025-39679 CVE-2025-39681 CVE-2025-39682 CVE-2025-39683 CVE-2025-39684 CVE-2025-39685 CVE-2025-39686 CVE-2025-39687 CVE-2025-39689 CVE-2025-39691 CVE-2025-39692 CVE-2025-39693 CVE-2025-39694 CVE-2025-39695 CVE-2025-39697 CVE-2025-39698 CVE-2025-39700 CVE-2025-39701 CVE-2025-39702 CVE-2025-39703 CVE-2025-39705 CVE-2025-39706 CVE-2025-39707 CVE-2025-39709 CVE-2025-39710 CVE-2025-39711 CVE-2025-39712 CVE-2025-39713 CVE-2025-39714 CVE-2025-39715 CVE-2025-39716 CVE-2025-39718 CVE-2025-39719 CVE-2025-39720 CVE-2025-39721 CVE-2025-39722 CVE-2025-39723 CVE-2025-39724 CVE-2025-39759 CVE-2025-39765 CVE-2025-39766 CVE-2025-39767 CVE-2025-39770 CVE-2025-39772 CVE-2025-39773 CVE-2025-39776 CVE-2025-39779 CVE-2025-39780 CVE-2025-39781 CVE-2025-39782 CVE-2025-39783 CVE-2025-39787 CVE-2025-39788 CVE-2025-39790 CVE-2025-39791 CVE-2025-39800 CVE-2025-39801 CVE-2025-39805 CVE-2025-39806 CVE-2025-39807 CVE-2025-39808 CVE-2025-39810 CVE-2025-39811 CVE-2025-39812 CVE-2025-39813 CVE-2025-39815 CVE-2025-39817 CVE-2025-39819 CVE-2025-39823 CVE-2025-39824 CVE-2025-39825 CVE-2025-39826 CVE-2025-39827 CVE-2025-39828 CVE-2025-39829 CVE-2025-39831 CVE-2025-39832 CVE-2025-39835 CVE-2025-39836 CVE-2025-39838 CVE-2025-39839 CVE-2025-39841 CVE-2025-39842 CVE-2025-39843 CVE-2025-39844 CVE-2025-39845 CVE-2025-39846 CVE-2025-39847 CVE-2025-39848 CVE-2025-39849 CVE-2025-39850 CVE-2025-39851 CVE-2025-39852 CVE-2025-39853 CVE-2025-39854 CVE-2025-39857 CVE-2025-39860 CVE-2025-39861 CVE-2025-39863 CVE-2025-39864 CVE-2025-39865 CVE-2025-39866 CVE-2025-40300

    在 Linux 内核中发现多个可能导致权限升级、拒绝服务或信息泄漏的漏洞。

    对于稳定发行版本 (trixie)这些问题已在版本 6.12.48-1中修复。

    建议您升级 linux 程序包。

    如需了解 linux 的详细安全状态，请参阅其安全跟踪页面：
    https://security-tracker.debian.org/tracker/linux

    有关 Debian 安全公告、如何将这些更新应用到系统以及常见问题解答的更多信息，请访问以下网址：https://www.debian.org/security/

    邮件列表：debian-security-announce@lists.debian.org

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

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
231715	Linux Distros 未修补的漏洞：CVE-2025-21751	Nessus	Misc.	2025/3/6	2026/7/18	high
352273	Rocky Linux 9.6 [TuxCare] 安全更新：kernel / kernel-abi-stablelists / kernel-core / 等多个漏洞（ALMALINUX9.6：CLSA-2026：1789986443）	Nessus	Rocky Linux Local Security Checks	2026/9/30	2026/9/30	high
234946	Amazon Linux 2023：bpftool、kernel6.12、kernel6.12-modules-extra (ALAS2023-2025-948)	Nessus	Amazon Linux Local Security Checks	2025/4/29	2026/2/13	high
352548	AlmaLinux 9.6 [TuxCare] 安全更新：kernel / kernel-abi-stablelists / kernel-core / 等多个漏洞（ALMALINUX9.6：CLSA-2026：1789986443）	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/9/30	high
265710	Debian dsa-6008ata-modules-6.12.31-armmp-di - 安全更新	Nessus	Debian Local Security Checks	2025/9/22	2026/9/18	high

检测

插件搜索

high

high

high

high

high