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

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

    io_uring/kbuf始终使用 READ_ONCE() 读取环提供的缓冲区长度 (CVE-2025-39816)

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

    cryptoaf_alg - 在 af_alg_sendmsg 中提前将合并设置为零CVE-2025-39931

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

    dm-stripe修复可能的整数溢出 (CVE-2025-39940)

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

    tls确保在标头虚假时中止流 (CVE-2025-39946)

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

    net/mlx5e针对设备取消绑定强化上行链路 netdev 访问 (CVE-2025-39947)

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

    cgroup将 cgroup_destroy_wq 拆分为 3 个工作队列 (CVE-2025-39953)

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

    tcp清除 tcp_disconnect() 中的 tcp_sk(sk)->fastopen_rsk。 (CVE-2025-39955)

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

    igcLED 设置错误时不会使 igc_probe() 失败 (CVE-2025-39956)

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

    iommu/amd/pgtbl修复增加页面表级别时可能的争用 (CVE-2025-39961)

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

    io_uring修复 io_link_skb 中错误的 io_kiocb 引用 (CVE-2025-39963)

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

    cryptoaf_alg - 禁止 af_alg_sendmsg 中的并发写入 (CVE-2025-39964)

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

    xfrmxfrm_alloc_spi 不应使用 0 作为 SPICVE-2025-39965]

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

    fbcon修复 fbcon_do_set_font 中的整数溢出 (CVE-2025-39967)

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

    smb 客户端修复 smb2_compound_op() 中错误的索引引用 (CVE-2025-39975)

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

    futex阻止 requeue-PI 期间的释放后使用 (CVE-2025-39977)

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

    nexthop当 nexthop 在群组中时禁止 FDB 状态更改 (CVE-2025-39980)

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

    nettunXDP 进程后更新 napi->skb (CVE-2025-39984)

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

    bpf检查 get_helper_proto 中的帮助程序函数是否有效 (CVE-2025-39990)

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

    mmswap在 VMA 上操作之前检查稳定地址空间 (CVE-2025-39992)

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

    scsitargettarget_core_configfs添加长度检查以避免缓冲区溢出 (CVE-2025-39998)

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

    mm/hugetlb修复 folio 在删除时仍然会映射 (CVE-2025-40006)

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

    fs/proc/task_mmu检查 p->vec_buf 是否为空 (CVE-2025-40009)

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

    ipvsnetns 清理期间推迟 ip_vs_ftp 取消注册 (CVE-2025-40018)

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

    tracingdynevent在 dynevent 上添加缺少的锁定检查 (CVE-2025-40021)

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

    vhost在 struct vhost_task 中引用任务。 (CVE-2025-40024)

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

    pinctrl检查 pinmux_ops::get_function_name() 的返回值 (CVE-2025-40030)

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

    Inputuinput - 对 uinput_ff_upload_compat 进行零初始化以避免信息泄漏 (CVE-2025-40035)

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

    fsudf修复 lengthAllocDescs 处理中的 OOB 读取 (CVE-2025-40044)

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

    io_uring/waitid始终删除 io_waitid_wait() 中的等待队列条目 (CVE-2025-40047)

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

    uio_hv_generic让用户空间处理中断掩码 (CVE-2025-40048)

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

    Squashfs修复 squashfs_get_parent 中的 uninit-value (CVE-2025-40049)

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

    smbclient修复线性内存中的加密缓冲区 (CVE-2025-40052)

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

    ptp在 max_vclocks 添加上限 (CVE-2025-40057)

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

    iommu/vt-d如果页面移动不连贯则不允许脏跟踪 (CVE-2025-40058)

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

    fs/ntfs3如果 $BITMAP 为空但存在块则拒绝索引分配 (CVE-2025-40067)

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

    fsntfs3修复了 run_unpack() 中的整数溢出 (CVE-2025-40068)

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

    pps修复注册设备失败时 pps_register_cdev 中的警告 (CVE-2025-40070)

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

    bpf显式检查对 bpf_sock_addr 的访问 (CVE-2025-40078)

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

    nbd将套接字限制为 TCP 和 UDP (CVE-2025-40080)

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

    perfarm_spe防止 PERF_IDX2OFF() 中的溢出 (CVE-2025-40081)

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

    cryptorng - 确保 set_ent 始终存在 (CVE-2025-40109)

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

    scsimpt3sas修复使用 ioc_info() 删除传输端口时发生的崩溃 (CVE-2025-40115)

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

    bpf强制 expected_attach_type 以实现 tailcall 兼容性CVE-2025-40123

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

    blk-mq在 blk_mq_unregister_hctx 中删除之前检查 kobject state_in_sysfs (CVE-2025-40125)

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

    sunrpc修复零长度校验和的空指针取消引用 (CVE-2025-40129)

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

    dm修复 __dm_suspend() 中的空指针取消引用 (CVE-2025-40134)

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

    mmhugetlb大型内存区域保护时避免软锁定 (CVE-2025-40153)

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

    bpf拒绝 ALU 操作的负偏移 (CVE-2025-40169)

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

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

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

  - 已修复 Linux 内核中的下列漏洞：l2tp: prevent possible tunnel refcount underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session->tunnel is non-NULL. However, session->tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session->tunnel is non-NULL when the tunnel refcount hasn't been bumped.
    Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session->tunnel to get the tunnel's encap. Add an encap arg to l2tp_session_set_header_len to avoid using session->tunnel. If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn't yet have session->tunnel set. Add a check for this case. (CVE-2024-49940)

  - 已修复 Linux 内核中的下列漏洞：mm/thp: fix deferred split unqueue naming and locking Recent changes are putting more pressure on THP deferred split queues: under load revealing long-standing races, causing list_del corruptions, Bad page states and worse (I keep BUGs in both of those, so usually don't get to see how badly they end up without). The relevant recent changes being 6.8's mTHP, 6.10's mTHP swapout, and 6.12's mTHP swapin, improved swap allocation, and underused THP splitting. Before fixing locking: rename misleading folio_undo_large_rmappable(), which does not undo large_rmappable, to folio_unqueue_deferred_split(), which is what it does. But that and its out-of-line
    __callee are mm internals of very limited usability: add comment and WARN_ON_ONCEs to check usage; and return a bool to say if a deferred split was unqueued, which can then be used in WARN_ON_ONCEs around safety checks (sparing callers the arcane conditionals in __folio_unqueue_deferred_split()). Just omit the folio_unqueue_deferred_split() from free_unref_folios(), all of whose callers now call it beforehand (and if any forget then bad_page() will tell) - except for its caller put_pages_list(), which itself no longer has any callers (and will be deleted separately). Swapout: mem_cgroup_swapout() has been resetting folio->memcg_data 0 without checking and unqueueing a THP folio from deferred split list; which is unfortunate, since the split_queue_lock depends on the memcg (when memcg is enabled); so swapout has been unqueueing such THPs later, when freeing the folio, using the pgdat's lock instead: potentially corrupting the memcg's list. __remove_mapping() has frozen refcount to 0 here, so no problem with calling folio_unqueue_deferred_split() before resetting memcg_data. That goes back to 5.4 commit 87eaceb3faa5 (mm: thp: make deferred split shrinker memcg aware): which included a check on swapcache before adding to deferred queue, but no check on deferred queue before adding THP to swapcache. That worked fine with the usual sequence of events in reclaim (though there were a couple of rare ways in which a THP on deferred queue could have been swapped out), but 6.12 commit dafff3f4c850 (mm: split underused THPs) avoids splitting underused THPs in reclaim, which makes swapcache THPs on deferred queue commonplace. Keep the check on swapcache before adding to deferred queue? Yes: it is no longer essential, but preserves the existing behaviour, and is likely to be a worthwhile optimization (vmstat showed much more traffic on the queue under swapping load if the check was removed); update its comment. Memcg-v1 move (deprecated):
    mem_cgroup_move_account() has been changing folio->memcg_data without checking and unqueueing a THP folio from the deferred list, sometimes corrupting from memcg's list, like swapout. Refcount is non-zero here, so folio_unqueue_deferred_split() can only be used in a WARN_ON_ONCE to validate the fix, which must be done earlier: mem_cgroup_move_charge_pte_range() first try to split the THP (splitting of course unqueues), or skip it if that fails. Not ideal, but moving charge has been requested, and khugepaged should repair the THP later: nobody wants new custom unqueueing code just for this deprecated case. The 87eaceb3faa5 commit did have the code to move from one deferred list to another (but was not conscious of its unsafety while refcount non-0); but that was removed by 5.6 commit fac0516b5534 (mm: thp: don't need care deferred split queue in memcg charge move path), which argued that the existence of a PMD mapping guarantees that the THP cannot be on a deferred list. As above, false in rare cases, and now commonly false. Backport to 6.11 should be straightforward. Earlier backports must take care that other
    _deferred_list fixes and dependencies are included. There is not a strong case for backports, but they can fix cornercases. (CVE-2024-53079)

  - 已修复 Linux 内核中的下列漏洞：io_uring/kbuf: reallocate buf lists on upgrade IORING_REGISTER_PBUF_RING can reuse an old struct io_buffer_list if it was created for legacy selected buffer and has been emptied. It violates the requirement that most of the field should stay stable after publish. Always reallocate it instead. (CVE-2025-21836)

  - 已修复 Linux 内核中的下列漏洞：RDMA/bnxt_re: Add sanity checks on rdev validity There is a possibility that ulp_irq_stop and ulp_irq_start callbacks will be called when the device is in detached state. This can cause a crash due to NULL pointer dereference as the rdev is already freed. (CVE-2025-21901)

  - 已修复 Linux 内核中的下列漏洞：cpufreq/amd-pstate: Add missing NULL ptr check in amd_pstate_update Check if policy is NULL before dereferencing it in amd_pstate_update.
    (CVE-2025-23137)

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

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

  - igc不要使 LED 设置错误时的 igc_probe() 失败。当 igc_led_setup() 失败时igc_probe() 会失败并在 free_netdev() 中触发内核错误这是因为未调用 unregister_netdev()。 [1] 可使用错误注入框架尤其是 faillab 功能测试此行为。 [2] 由于 LED 支持不是强制要求请将 LED 设置失败视为非致命错误并继续探测并显示警告消息从而避免内核错误。 [1] 内核缺陷位于 net/core/dev.c:12047! Oops无效的 opcode0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 937 Comm: repro-igc-led-e 未受感染 6.17.0-rc4-enjuk-tnguy-00865-gc4940196ab02 #64 PREEMPT ) 硬件名称QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP0010:free_netdev+0x278/0x2b0 [...] 调用跟踪 <TASK> igc_probe+0x370/0x910 local_pci_probe+0x3a/0x80 pci_device_probe+0xd1/0x200 [...] [2] #!/bin/bash -ex FAILSLAB_PATH=/sys/kernel/debug/failslab/ DEVICE=0000:00 05.0 START_ADDR=$(grep igc_led_setup /proc/kallsyms \ | awk '{printf(0x%s, $1)}') END_ADDR=$(printf 0x%x $((START_ADDR + 0x100))) echo $START_ADDR > $FAILSLAB_PATH/require-start echo $END_ADDR > $FAILSLAB_PATH/require-end echo 1 > $FAILSLAB_PATH/times echo 100 > $FAILSLAB_PATH/probability echo N > $FAILSLAB_PATH/ignore-gfp-wait echo $DEVICE > /sys/bus/pci/drivers/igc/bind (CVE-2025-39956)

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

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

  - 已修复 Linux 内核中的下列漏洞：l2tp: prevent possible tunnel refcount underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session->tunnel is non-NULL. However, session->tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session->tunnel is non-NULL when the tunnel refcount hasn't been bumped.
    Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session->tunnel to get the tunnel's encap. Add an encap arg to l2tp_session_set_header_len to avoid using session->tunnel. If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn't yet have session->tunnel set. Add a check for this case. (CVE-2024-49940)

  - 已修复 Linux 内核中的下列漏洞：mm/thp: fix deferred split unqueue naming and locking Recent changes are putting more pressure on THP deferred split queues: under load revealing long-standing races, causing list_del corruptions, Bad page states and worse (I keep BUGs in both of those, so usually don't get to see how badly they end up without). The relevant recent changes being 6.8's mTHP, 6.10's mTHP swapout, and 6.12's mTHP swapin, improved swap allocation, and underused THP splitting. Before fixing locking: rename misleading folio_undo_large_rmappable(), which does not undo large_rmappable, to folio_unqueue_deferred_split(), which is what it does. But that and its out-of-line
    __callee are mm internals of very limited usability: add comment and WARN_ON_ONCEs to check usage; and return a bool to say if a deferred split was unqueued, which can then be used in WARN_ON_ONCEs around safety checks (sparing callers the arcane conditionals in __folio_unqueue_deferred_split()). Just omit the folio_unqueue_deferred_split() from free_unref_folios(), all of whose callers now call it beforehand (and if any forget then bad_page() will tell) - except for its caller put_pages_list(), which itself no longer has any callers (and will be deleted separately). Swapout: mem_cgroup_swapout() has been resetting folio->memcg_data 0 without checking and unqueueing a THP folio from deferred split list; which is unfortunate, since the split_queue_lock depends on the memcg (when memcg is enabled); so swapout has been unqueueing such THPs later, when freeing the folio, using the pgdat's lock instead: potentially corrupting the memcg's list. __remove_mapping() has frozen refcount to 0 here, so no problem with calling folio_unqueue_deferred_split() before resetting memcg_data. That goes back to 5.4 commit 87eaceb3faa5 (mm: thp: make deferred split shrinker memcg aware): which included a check on swapcache before adding to deferred queue, but no check on deferred queue before adding THP to swapcache. That worked fine with the usual sequence of events in reclaim (though there were a couple of rare ways in which a THP on deferred queue could have been swapped out), but 6.12 commit dafff3f4c850 (mm: split underused THPs) avoids splitting underused THPs in reclaim, which makes swapcache THPs on deferred queue commonplace. Keep the check on swapcache before adding to deferred queue? Yes: it is no longer essential, but preserves the existing behaviour, and is likely to be a worthwhile optimization (vmstat showed much more traffic on the queue under swapping load if the check was removed); update its comment. Memcg-v1 move (deprecated):
    mem_cgroup_move_account() has been changing folio->memcg_data without checking and unqueueing a THP folio from the deferred list, sometimes corrupting from memcg's list, like swapout. Refcount is non-zero here, so folio_unqueue_deferred_split() can only be used in a WARN_ON_ONCE to validate the fix, which must be done earlier: mem_cgroup_move_charge_pte_range() first try to split the THP (splitting of course unqueues), or skip it if that fails. Not ideal, but moving charge has been requested, and khugepaged should repair the THP later: nobody wants new custom unqueueing code just for this deprecated case. The 87eaceb3faa5 commit did have the code to move from one deferred list to another (but was not conscious of its unsafety while refcount non-0); but that was removed by 5.6 commit fac0516b5534 (mm: thp: don't need care deferred split queue in memcg charge move path), which argued that the existence of a PMD mapping guarantees that the THP cannot be on a deferred list. As above, false in rare cases, and now commonly false. Backport to 6.11 should be straightforward. Earlier backports must take care that other
    _deferred_list fixes and dependencies are included. There is not a strong case for backports, but they can fix cornercases. (CVE-2024-53079)

  - 已修复 Linux 内核中的下列漏洞：io_uring/kbuf: reallocate buf lists on upgrade IORING_REGISTER_PBUF_RING can reuse an old struct io_buffer_list if it was created for legacy selected buffer and has been emptied. It violates the requirement that most of the field should stay stable after publish. Always reallocate it instead. (CVE-2025-21836)

  - 已修复 Linux 内核中的下列漏洞：RDMA/bnxt_re: Add sanity checks on rdev validity There is a possibility that ulp_irq_stop and ulp_irq_start callbacks will be called when the device is in detached state. This can cause a crash due to NULL pointer dereference as the rdev is already freed. (CVE-2025-21901)

  - 已修复 Linux 内核中的下列漏洞：cpufreq/amd-pstate: Add missing NULL ptr check in amd_pstate_update Check if policy is NULL before dereferencing it in amd_pstate_update.
    (CVE-2025-23137)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
271737	Amazon Linux 2023 bpftool6.12、kernel6.12、kernel6.12-devel (ALAS2023-2025-1254)	Nessus	Amazon Linux Local Security Checks	2025/10/28	2026/9/18	high
352240	Rocky Linux 9.6 [TuxCare] 安全更新：kernel / kernel-abi-stablelists / kernel-core / 等多个漏洞（ALMALINUX9.6：CLSA-2026：1787305050）	Nessus	Rocky Linux Local Security Checks	2026/9/30	2026/9/30	high
270204	Linux Distros 未修补的漏洞：CVE-2025-39956	Nessus	Misc.	2025/10/13	2026/7/31	medium
352220	AlmaLinux 9.6 [TuxCare] 安全更新：kernel / kernel-abi-stablelists / kernel-core / 等多个漏洞（ALMALINUX9.6：CLSA-2026：1787305050）	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/9/30	high

检测

插件搜索

high

high

medium

high