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

  - 已修复 Linux 内核中的下列漏洞：wifi: ath12k: Fix buffer overflow in debugfs If the user tries to write more than 32 bytes then it results in memory corruption. Fortunately, this is debugfs so it's limited to root users. (CVE-2025-38317)

  - 已修复 Linux 内核中的下列漏洞：drm/xe/pf: Clear all LMTT pages on alloc Our LMEM buffer objects are not cleared by default on alloc and during VF provisioning we only setup LMTT PTEs for the actually provisioned LMEM range. But beyond that valid range we might leave some stale data that could either point to some other VFs allocations or even to the PF pages. Explicitly clear all new LMTT page to avoid the risk that a malicious VF would try to exploit that gap. While around add asserts to catch any undesired PTE overwrites and low-level debug traces to track LMTT PT life-cycle.
    (cherry picked from commit 3fae6918a3e27cce20ded2551f863fb05d4bef8d) (CVE-2025-38511)

  - 已修复 Linux 内核中的下列漏洞：wifi: ath12k: fix memory leak in ath12k_service_ready_ext_event Currently, in ath12k_service_ready_ext_event(), svc_rdy_ext.mac_phy_caps is not freed in the failure case, causing a memory leak. The following trace is observed in kmemleak:
    unreferenced object 0xffff8b3eb5789c00 (size 1024): comm softirq, pid 0, jiffies 4294942577 hex dump (first 32 bytes): 00 00 00 00 01 00 00 00 00 00 00 00 7b 00 00 10 ............{... 01 00 00 00 00 00 00 00 01 00 00 00 1f 38 00 00 .............8.. backtrace (crc 44e1c357): __kmalloc_noprof+0x30b/0x410 ath12k_wmi_mac_phy_caps_parse+0x84/0x100 [ath12k] ath12k_wmi_tlv_iter+0x5e/0x140 [ath12k] ath12k_wmi_svc_rdy_ext_parse+0x308/0x4c0 [ath12k] ath12k_wmi_tlv_iter+0x5e/0x140 [ath12k] ath12k_service_ready_ext_event.isra.0+0x44/0xd0 [ath12k] ath12k_wmi_op_rx+0x2eb/0xd70 [ath12k] ath12k_htc_rx_completion_handler+0x1f4/0x330 [ath12k] ath12k_ce_recv_process_cb+0x218/0x300 [ath12k] ath12k_pci_ce_workqueue+0x1b/0x30 [ath12k] process_one_work+0x219/0x680 bh_worker+0x198/0x1f0 tasklet_action+0x13/0x30 handle_softirqs+0xca/0x460 __irq_exit_rcu+0xbe/0x110 irq_exit_rcu+0x9/0x30 Free svc_rdy_ext.mac_phy_caps in the error case to fix this memory leak. Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.4.1-00199-QCAHKSWPL_SILICONZ-1 (CVE-2025-39890)

  - 已修复 Linux 内核中的下列漏洞：bpf: Fix metadata_dst leak
    __bpf_redirect_neigh_v{4,6} Cilium has a BPF egress gateway feature which forces outgoing K8s Pod traffic to pass through dedicated egress gateways which then SNAT the traffic in order to interact with stable IPs outside the cluster. The traffic is directed to the gateway via vxlan tunnel in collect md mode. A recent BPF change utilized the bpf_redirect_neigh() helper to forward packets after the arrival and decap on vxlan, which turned out over time that the kmalloc-256 slab usage in kernel was ever-increasing. The issue was that vxlan allocates the metadata_dst object and attaches it through a fake dst entry to the skb. The latter was never released though given bpf_redirect_neigh() was merely setting the new dst entry via skb_dst_set() without dropping an existing one first. (CVE-2025-40183)

  - 已修复 Linux 内核中的下列漏洞：mlxsw: spectrum_router: Fix neighbour use-after-free We sometimes observe use-after-free when dereferencing a neighbour [1]. The problem seems to be that the driver stores a pointer to the neighbour, but without holding a reference on it. A reference is only taken when the neighbour is used by a nexthop. Fix by simplifying the reference counting scheme. Always take a reference when storing a neighbour pointer in a neighbour entry. Avoid taking a referencing when the neighbour is used by a nexthop as the neighbour entry associated with the nexthop already holds a reference. Tested by running the test that uncovered the problem over 300 times. Without this patch the problem was reproduced after a handful of iterations. [1] BUG: KASAN: slab-use-after-free in mlxsw_sp_neigh_entry_update+0x2d4/0x310 Read of size 8 at addr ffff88817f8e3420 by task ip/3929 CPU: 3 UID: 0 PID: 3929 Comm: ip Not tainted 6.18.0-rc4-virtme-g36b21a067510 #3 PREEMPT(full) Hardware name:
    Nvidia SN5600/VMOD0013, BIOS 5.13 05/31/2023 Call Trace: <TASK> dump_stack_lvl+0x6f/0xa0 print_address_description.constprop.0+0x6e/0x300 print_report+0xfc/0x1fb kasan_report+0xe4/0x110 mlxsw_sp_neigh_entry_update+0x2d4/0x310 mlxsw_sp_router_rif_gone_sync+0x35f/0x510 mlxsw_sp_rif_destroy+0x1ea/0x730 mlxsw_sp_inetaddr_port_vlan_event+0xa1/0x1b0
    __mlxsw_sp_inetaddr_lag_event+0xcc/0x130 __mlxsw_sp_inetaddr_event+0xf5/0x3c0 mlxsw_sp_router_netdevice_event+0x1015/0x1580 notifier_call_chain+0xcc/0x150 call_netdevice_notifiers_info+0x7e/0x100 __netdev_upper_dev_unlink+0x10b/0x210 netdev_upper_dev_unlink+0x79/0xa0 vrf_del_slave+0x18/0x50 do_set_master+0x146/0x7d0 do_setlink.isra.0+0x9a0/0x2880 rtnl_newlink+0x637/0xb20 rtnetlink_rcv_msg+0x6fe/0xb90 netlink_rcv_skb+0x123/0x380 netlink_unicast+0x4a3/0x770 netlink_sendmsg+0x75b/0xc90
    __sock_sendmsg+0xbe/0x160 ____sys_sendmsg+0x5b2/0x7d0 ___sys_sendmsg+0xfd/0x180 __sys_sendmsg+0x124/0x1c0 do_syscall_64+0xbb/0xfd0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 [...] Allocated by task 109:
    kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x7b/0x90
    __kmalloc_noprof+0x2c1/0x790 neigh_alloc+0x6af/0x8f0 ___neigh_create+0x63/0xe90 mlxsw_sp_nexthop_neigh_init+0x430/0x7e0 mlxsw_sp_nexthop_type_init+0x212/0x960 mlxsw_sp_nexthop6_group_info_init.constprop.0+0x81f/0x1280 mlxsw_sp_nexthop6_group_get+0x392/0x6a0 mlxsw_sp_fib6_entry_create+0x46a/0xfd0 mlxsw_sp_router_fib6_replace+0x1ed/0x5f0 mlxsw_sp_router_fib6_event_work+0x10a/0x2a0 process_one_work+0xd57/0x1390 worker_thread+0x4d6/0xd40 kthread+0x355/0x5b0 ret_from_fork+0x1d4/0x270 ret_from_fork_asm+0x11/0x20 Freed by task 154:
    kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_save_free_info+0x3b/0x60
    __kasan_slab_free+0x43/0x70 kmem_cache_free_bulk.part.0+0x1eb/0x5e0 kvfree_rcu_bulk+0x1f2/0x260 kfree_rcu_work+0x130/0x1b0 process_one_work+0xd57/0x1390 worker_thread+0x4d6/0xd40 kthread+0x355/0x5b0 ret_from_fork+0x1d4/0x270 ret_from_fork_asm+0x11/0x20 Last potentially related work creation:
    kasan_save_stack+0x30/0x50 kasan_record_aux_stack+0x8c/0xa0 kvfree_call_rcu+0x93/0x5b0 mlxsw_sp_router_neigh_event_work+0x67d/0x860 process_one_work+0xd57/0x1390 worker_thread+0x4d6/0xd40 kthread+0x355/0x5b0 ret_from_fork+0x1d4/0x270 ret_from_fork_asm+0x11/0x20 (CVE-2025-68801)

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

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

  - 已修复 Linux 内核中的下列漏洞：wifi: ath12k: Fix buffer overflow in debugfs If the user tries to write more than 32 bytes then it results in memory corruption. Fortunately, this is debugfs so it's limited to root users. (CVE-2025-38317)

  - 已修复 Linux 内核中的下列漏洞：drm/xe/pf: Clear all LMTT pages on alloc Our LMEM buffer objects are not cleared by default on alloc and during VF provisioning we only setup LMTT PTEs for the actually provisioned LMEM range. But beyond that valid range we might leave some stale data that could either point to some other VFs allocations or even to the PF pages. Explicitly clear all new LMTT page to avoid the risk that a malicious VF would try to exploit that gap. While around add asserts to catch any undesired PTE overwrites and low-level debug traces to track LMTT PT life-cycle.
    (cherry picked from commit 3fae6918a3e27cce20ded2551f863fb05d4bef8d) (CVE-2025-38511)

  - 已修复 Linux 内核中的下列漏洞：wifi: ath12k: fix memory leak in ath12k_service_ready_ext_event Currently, in ath12k_service_ready_ext_event(), svc_rdy_ext.mac_phy_caps is not freed in the failure case, causing a memory leak. The following trace is observed in kmemleak:
    unreferenced object 0xffff8b3eb5789c00 (size 1024): comm softirq, pid 0, jiffies 4294942577 hex dump (first 32 bytes): 00 00 00 00 01 00 00 00 00 00 00 00 7b 00 00 10 ............{... 01 00 00 00 00 00 00 00 01 00 00 00 1f 38 00 00 .............8.. backtrace (crc 44e1c357): __kmalloc_noprof+0x30b/0x410 ath12k_wmi_mac_phy_caps_parse+0x84/0x100 [ath12k] ath12k_wmi_tlv_iter+0x5e/0x140 [ath12k] ath12k_wmi_svc_rdy_ext_parse+0x308/0x4c0 [ath12k] ath12k_wmi_tlv_iter+0x5e/0x140 [ath12k] ath12k_service_ready_ext_event.isra.0+0x44/0xd0 [ath12k] ath12k_wmi_op_rx+0x2eb/0xd70 [ath12k] ath12k_htc_rx_completion_handler+0x1f4/0x330 [ath12k] ath12k_ce_recv_process_cb+0x218/0x300 [ath12k] ath12k_pci_ce_workqueue+0x1b/0x30 [ath12k] process_one_work+0x219/0x680 bh_worker+0x198/0x1f0 tasklet_action+0x13/0x30 handle_softirqs+0xca/0x460 __irq_exit_rcu+0xbe/0x110 irq_exit_rcu+0x9/0x30 Free svc_rdy_ext.mac_phy_caps in the error case to fix this memory leak. Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.4.1-00199-QCAHKSWPL_SILICONZ-1 (CVE-2025-39890)

  - 已修复 Linux 内核中的下列漏洞：bpf: Fix metadata_dst leak
    __bpf_redirect_neigh_v{4,6} Cilium has a BPF egress gateway feature which forces outgoing K8s Pod traffic to pass through dedicated egress gateways which then SNAT the traffic in order to interact with stable IPs outside the cluster. The traffic is directed to the gateway via vxlan tunnel in collect md mode. A recent BPF change utilized the bpf_redirect_neigh() helper to forward packets after the arrival and decap on vxlan, which turned out over time that the kmalloc-256 slab usage in kernel was ever-increasing. The issue was that vxlan allocates the metadata_dst object and attaches it through a fake dst entry to the skb. The latter was never released though given bpf_redirect_neigh() was merely setting the new dst entry via skb_dst_set() without dropping an existing one first. (CVE-2025-40183)

  - 已修复 Linux 内核中的下列漏洞：mlxsw: spectrum_router: Fix neighbour use-after-free We sometimes observe use-after-free when dereferencing a neighbour [1]. The problem seems to be that the driver stores a pointer to the neighbour, but without holding a reference on it. A reference is only taken when the neighbour is used by a nexthop. Fix by simplifying the reference counting scheme. Always take a reference when storing a neighbour pointer in a neighbour entry. Avoid taking a referencing when the neighbour is used by a nexthop as the neighbour entry associated with the nexthop already holds a reference. Tested by running the test that uncovered the problem over 300 times. Without this patch the problem was reproduced after a handful of iterations. [1] BUG: KASAN: slab-use-after-free in mlxsw_sp_neigh_entry_update+0x2d4/0x310 Read of size 8 at addr ffff88817f8e3420 by task ip/3929 CPU: 3 UID: 0 PID: 3929 Comm: ip Not tainted 6.18.0-rc4-virtme-g36b21a067510 #3 PREEMPT(full) Hardware name:
    Nvidia SN5600/VMOD0013, BIOS 5.13 05/31/2023 Call Trace: <TASK> dump_stack_lvl+0x6f/0xa0 print_address_description.constprop.0+0x6e/0x300 print_report+0xfc/0x1fb kasan_report+0xe4/0x110 mlxsw_sp_neigh_entry_update+0x2d4/0x310 mlxsw_sp_router_rif_gone_sync+0x35f/0x510 mlxsw_sp_rif_destroy+0x1ea/0x730 mlxsw_sp_inetaddr_port_vlan_event+0xa1/0x1b0
    __mlxsw_sp_inetaddr_lag_event+0xcc/0x130 __mlxsw_sp_inetaddr_event+0xf5/0x3c0 mlxsw_sp_router_netdevice_event+0x1015/0x1580 notifier_call_chain+0xcc/0x150 call_netdevice_notifiers_info+0x7e/0x100 __netdev_upper_dev_unlink+0x10b/0x210 netdev_upper_dev_unlink+0x79/0xa0 vrf_del_slave+0x18/0x50 do_set_master+0x146/0x7d0 do_setlink.isra.0+0x9a0/0x2880 rtnl_newlink+0x637/0xb20 rtnetlink_rcv_msg+0x6fe/0xb90 netlink_rcv_skb+0x123/0x380 netlink_unicast+0x4a3/0x770 netlink_sendmsg+0x75b/0xc90
    __sock_sendmsg+0xbe/0x160 ____sys_sendmsg+0x5b2/0x7d0 ___sys_sendmsg+0xfd/0x180 __sys_sendmsg+0x124/0x1c0 do_syscall_64+0xbb/0xfd0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 [...] Allocated by task 109:
    kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x7b/0x90
    __kmalloc_noprof+0x2c1/0x790 neigh_alloc+0x6af/0x8f0 ___neigh_create+0x63/0xe90 mlxsw_sp_nexthop_neigh_init+0x430/0x7e0 mlxsw_sp_nexthop_type_init+0x212/0x960 mlxsw_sp_nexthop6_group_info_init.constprop.0+0x81f/0x1280 mlxsw_sp_nexthop6_group_get+0x392/0x6a0 mlxsw_sp_fib6_entry_create+0x46a/0xfd0 mlxsw_sp_router_fib6_replace+0x1ed/0x5f0 mlxsw_sp_router_fib6_event_work+0x10a/0x2a0 process_one_work+0xd57/0x1390 worker_thread+0x4d6/0xd40 kthread+0x355/0x5b0 ret_from_fork+0x1d4/0x270 ret_from_fork_asm+0x11/0x20 Freed by task 154:
    kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_save_free_info+0x3b/0x60
    __kasan_slab_free+0x43/0x70 kmem_cache_free_bulk.part.0+0x1eb/0x5e0 kvfree_rcu_bulk+0x1f2/0x260 kfree_rcu_work+0x130/0x1b0 process_one_work+0xd57/0x1390 worker_thread+0x4d6/0xd40 kthread+0x355/0x5b0 ret_from_fork+0x1d4/0x270 ret_from_fork_asm+0x11/0x20 Last potentially related work creation:
    kasan_save_stack+0x30/0x50 kasan_record_aux_stack+0x8c/0xa0 kvfree_call_rcu+0x93/0x5b0 mlxsw_sp_router_neigh_event_work+0x67d/0x860 process_one_work+0xd57/0x1390 worker_thread+0x4d6/0xd40 kthread+0x355/0x5b0 ret_from_fork+0x1d4/0x270 ret_from_fork_asm+0x11/0x20 (CVE-2025-68801)

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

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

  - PCI：访问之前检查 ROM 标头和数据结构地址 在计算机上运行 stress-ng 时x86_64会遇到崩溃： 缺陷：无法处理地址的页面错误：ffa0000007f40000 RIP：
    0010：pci_get_rom_size+0x52/0x220 调用跟踪： <TASK> pci_map_rom+0x80/0x130 pci_read_rom+0x4b/0xe0 kernfs_file_read_iter+0x96/0x180 vfs_read+0x1b1/0x300 我们的分析显示，ROM 空间的起始地址为 0xffa0000007f30000，大小为 0x10000。由于 ROM 空间损坏，在调用 readl（pds） 之前，pds 的值为 0xffa0000007f3ffff，其已指向 ROM 空间端，调用 readl（） 会读取 4 个字节，因此会造成越界访问并触发崩溃。通过添加图像标头和数据结构检查修复此问题。我们还在 arm64 机器上发现另一个崩溃：无法处理虚拟地址 ffff8000dd1393ff 上的内核分页请求 内存中止信息：ESR = 0x0000000096000021 EC = 0x25：DABT（当前 EL），IL = 32 位 SET = 0，FnV = 0 EA = 0，S1PTW = 0 FSC = 0x21：对齐错误 调用跟踪与 x86_64 相同，但崩溃原因是数据结构地址未与 4 对齐， 和 arm64 计算机报告对齐错误。通过添加对齐检查修复此问题。[bhelgaas：
    缩短函数名，封装注释] （CVE-2026-72487）

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

远程 Ubuntu 24.04 LTS / Pro Realtime 24.04 LTS 主机上安装的软件包存在多个漏洞，如 USN-8781-1 告警中所述。

    已发现在全局观察到通过无效转换进行的内存写入之前，某些 Arm 处理器可完成广播转换后备缓冲器 （TLB） 无效化。本地攻击者可能利用此缺陷在撤销权限后写入内存，从而绕过内存保护或升级权限。（CVE-2025-10263）

    在 Linux 内核中发现多个安全问题。攻击者可能利用这些问题入侵系统。此更新修正了以下子系统中的缺陷：

    - ARM64 架构；

    - 用户空间 API (UAPI)；

    - 内核构建系统;

    - ARM32 架构；

    - PowerPC 架构；

    - RISC-V 架构；

    - S390 架构；

    - User-Mode Linux (UML)；

    - x86 架构；

    - 加密 API；

    - 英特尔 NPU 驱动程序;

    - 计算加速框架；

    - ACPI 驱动程序；

    - 驱动程序核心；

    - DRBD 分布式复制块设备驱动程序；

    - 雷达斯块设备 （RBD） 驱动程序;

    - Ublk userspace block 驱动程序；

    - 压缩 RAM 块设备驱动程序；

    - 蓝牙驱动程序；

    - 硬件加密设备驱动程序；

    - CXL (Compute Express Link) 驱动程序；

    - Arm Firmware Framework for ARMv8-A(FFA)；

    - EFI 核心；

    - FPGA 架构；

    - GPU 驱动程序；

    - HID 子系统；

    - 硬件监控驱动程序；

    - I2C 子系统；

    - I3C 子系统；

    - InfiniBand 驱动程序；

    - 输入设备核心驱动程序；

    - 输入设备（鼠标）驱动程序；

    - IOMMU 子系统；

    - 多设备驱动程序；

    - 媒体驱动程序；

    - Fastrpc 驱动程序；

    - 网络驱动程序；

    - Mellanox 网络驱动程序；

    - Microsoft Azure Network Adapter (MANA) 驱动程序；

    - MediaTek 网络驱动程序；

    - NVME 驱动程序；

    - 操作性能点 (OPP) 驱动程序；

    - PCI 子系统；

    - PTP 时钟框架；

    - RPMSG 子系统；

    - SCSI 子系统；

    - SoundWire 子系统；

    - SPI 子系统；

    - Greybus lights 分段驱动程序；

    - 媒体分段驱动程序；

    - NVIDIA Tegra 嵌入式控制器 （NVEC） 暂存驱动程序;

    - Realtek RTL8723BS SDIO 驱动程序；

    - TCM 子系统；

    - 受信任执行环境驱动程序；

    - Thunderbolt 和 USB4 驱动程序；

    - TTY 驱动程序；

    - USB Gadget 驱动程序；

    - USB Dual Role (OTG-ready) Controller 驱动程序；

    - USB 串口驱动程序；

    - vDPA 驱动程序；

    - VFIO 驱动程序；

    - Virtio Host (VHOST) 子系统；

    - Virtio 驱动程序；

    - Xen 管理程序驱动程序；

    - 9P 分布式文件系统；

    - AFS 文件系统；

    - 文件系统基础设施；

    - BTRFS 文件系统；

    - Ceph 分布式文件系统；

    - exFAT 文件系统；

    - F2FS 文件系统；

    - GFS2 文件系统；

    - HFS 文件系统；

    - HFS+ 文件系统；

    - JFS 文件系统；

    - 网络文件系统库；

    - 网络文件系统 (NFS) 客户端；

    - 网络文件系统 (NFS) 服务器后台程序；

    - NTFS3 文件系统；

    - OCFS2 文件系统；

    - OrangeFS 文件系统；

    - SMB 网络文件系统；

    - BPF 子系统；

    - 文件系统加密 （fscrypt）;

    - 软件节点和设备属性;

    - IPv4 联网；

    - KVM 子系统；

    - Mellanox 驱动程序；

    - 内存管理；

    - Networking 核心；

    - Netfilter；

    - 套接字消息基础架构；

    - MediaTek SoC 驱动程序；

    - Sun RPC 协议；

    - 网络流量控制；

    - IPv6 联网；

    - Amateur Radio 驱动程序；

    - 蓝牙子系统；

    - IP 隧道定义；

    - KCM（Kernel Connection Multiplexor）套接字驱动程序；

    - MultiProtocol Label Switching 驱动程序；

    - TCP 网络协议；

    - XFRM 子系统；

    - 跟踪基础设施；

    - io_uring 子系统；

    - 控制群组 (cgroup)；

    - Perf 事件；

    - IRQ 子系统；

    - 锁定基元；

    - KProbes 跟踪;

    - 9P 文件系统网络协议；

    - B.A.T.M.A.N. 网格协议；

    - 以太网桥接；

    - CAN 网络层；

    - Ceph Core 库；

    - 握手 API；

    - HSR 网络协议；

    - IFE协议;

    - L2TP 协议；

    - MAC80211 子系统；

    - IEEE 802.15.4 子系统；

    - 多路径 TCP；

    - NFC 子系统；

    - Open vSwitch；

    - Phonet 协议；

    - RDS 协议；

    - RxRPC 会话套接字；

    - SCTP 协议；

    - SMC 套接字；

    - TIPC 协议；

    - TLS 协议；

    - Unix 域套接字；

    - VMware vSockets 驱动程序；

    - 无线网络；

    - X.25 network layer;

    - eXpress 数据路径；

    - Rust 绑定机制；

    - AppArmor 安全模块；

    - 密钥管理；

    - Linux 安全模块 (LSM) 框架；

    - SELinux 安全模块；

    - ALSA 框架；

    - AudioScience HPI 驱动程序；

    - Intel ASoC 驱动程序；

    - USB音响设备;（CVE-2024-14040 ， ， ， CVE-2024-41008， CVE-2024-43872CVE-2025-38498CVE-2025-21985CVE-2025-22104CVE-2024-57857CVE-2024-58089CVE-2024-56591CVE-2024-58098CVE-2024-58094CVE-2024-58100CVE-2024-58241CVE-2025-21687CVE-2025-21693CVE-2025-21984CVE-2024-56552CVE-2025-22109CVE-2025-22108CVE-2025-23132CVE-2025-37776CVE-2025-37876CVE-2025-37906CVE-2025-38064CVE-2024-53098CVE-2025-38187CVE-2025-38069CVE-2025-38204CVE-2025-38206CVE-2025-38242CVE-2025-38563CVE-2025-38565CVE-2024-52560CVE-2025-38717CVE-2025-38636CVE-2025-40025CVE-2025-39990CVE-2025-40040CVE-2025-39958CVE-2025-39933CVE-2025-39896CVE-2025-40054CVE-2025-39862CVE-2025-39859CVE-2025-39789CVE-2025-40064CVE-2025-39677CVE-2024-50217CVE-2025-40074CVE-2025-40168CVE-2025-40158CVE-2025-40170CVE-2025-40139CVE-2025-40203CVE-2025-40274CVE-2024-44932CVE-2024-49932CVE-2025-40344CVE-2024-44964CVE-2024-49940CVE-2024-50106CVE-2025-40075CVE-2024-35948、 、 、 CVE-2026-43213CVE-2026-23239CVE-2026-23208CVE-2026-23240CVE-2026-23327CVE-2026-23393CVE-2026-23469CVE-2026-31420CVE-2025-71289CVE-2026-31486CVE-2026-31479CVE-2026-31493CVE-2026-31560CVE-2026-31568CVE-2026-31630CVE-2026-31663CVE-2025-71202CVE-2026-43009CVE-2026-31771CVE-2026-43029CVE-2026-43042CVE-2026-43048CVE-2026-43101CVE-2026-43116CVE-2025-71074CVE-2026-43172CVE-2026-43126CVE-2026-43263CVE-2026-43303CVE-2026-43352CVE-2026-46158CVE-2026-46130CVE-2026-46054CVE-2026-46170CVE-2026-45944CVE-2026-45932CVE-2026-45894CVE-2026-46175CVE-2026-45850CVE-2026-43464CVE-2026-43353CVE-2026-46181CVE-2025-71073CVE-2025-68745CVE-2026-52910CVE-2026-46324CVE-2026-52909CVE-2026-46275CVE-2026-46315CVE-2026-46320CVE-2026-52908CVE-2026-52912CVE-2025-68822CVE-2026-46330CVE-2025-68360CVE-2026-46203CVE-2025-68304CVE-2025-68174CVE-2025-40354、 、 、 CVE-2026-53159CVE-2026-52988CVE-2026-52991CVE-2026-53000CVE-2026-52956CVE-2026-53009CVE-2026-53005CVE-2026-53024CVE-2026-53025CVE-2026-53053CVE-2026-53070CVE-2026-53078CVE-2026-52941CVE-2026-53090CVE-2026-53089CVE-2026-53091CVE-2026-53109CVE-2026-53118CVE-2026-53120CVE-2026-53129CVE-2026-52934CVE-2026-53132CVE-2026-53131CVE-2026-53133CVE-2026-53148CVE-2026-53182CVE-2026-53230CVE-2026-53221CVE-2026-53217CVE-2026-53232CVE-2026-53216CVE-2026-53198CVE-2026-53196CVE-2026-53239CVE-2026-53186CVE-2026-53185CVE-2026-53183CVE-2026-53250CVE-2026-52926CVE-2026-52921CVE-2026-53275CVE-2026-53266CVE-2026-53273CVE-2026-53256CVE-2026-53262CVE-2026-53264CVE-2026-53270CVE-2026-53281CVE-2026-52922CVE-2026-53269CVE-2026-52919CVE-2026-53254CVE-2026-52918CVE-2026-52916CVE-2026-52915、 、 、 CVE-2026-63906CVE-2026-63795CVE-2026-63796CVE-2026-63797CVE-2026-53399CVE-2026-63801CVE-2026-63800CVE-2026-63804CVE-2026-63807CVE-2026-63808CVE-2026-63815CVE-2026-63818CVE-2026-53398CVE-2026-63828CVE-2026-63825CVE-2026-63829CVE-2026-63830CVE-2026-63831CVE-2026-63853CVE-2026-63858CVE-2026-53384CVE-2026-63887CVE-2026-63886CVE-2026-63888CVE-2026-63893CVE-2026-63912CVE-2026-63926CVE-2026-63924CVE-2026-63922CVE-2026-63940CVE-2026-63921CVE-2026-63919CVE-2026-63917CVE-2026-63944CVE-2026-63916CVE-2026-63915CVE-2026-63914CVE-2026-63945CVE-2026-53368CVE-2026-53358CVE-2026-63979CVE-2026-63974CVE-2026-63978CVE-2026-63947CVE-2026-63948CVE-2026-63952CVE-2026-63976CVE-2026-63980CVE-2026-53361CVE-2026-63975CVE-2026-53357CVE-2026-63946CVE-2026-53355CVE-2026-53354CVE-2026-53284、 、 、 CVE-2026-64087CVE-2026-64025CVE-2026-64029CVE-2026-64032CVE-2026-64018CVE-2026-64034CVE-2026-64033CVE-2026-64039CVE-2026-64046CVE-2026-64047CVE-2026-64048CVE-2026-64051CVE-2026-64015CVE-2026-64056CVE-2026-64055CVE-2026-64064CVE-2026-64073CVE-2026-64076CVE-2026-64077CVE-2026-64082CVE-2026-64011CVE-2026-64084CVE-2026-64083CVE-2026-64085CVE-2026-64086CVE-2026-64088CVE-2026-64102CVE-2026-64099CVE-2026-64098CVE-2026-64103CVE-2026-64097CVE-2026-64096CVE-2026-64093CVE-2026-64106CVE-2026-64092CVE-2026-64091CVE-2026-64089CVE-2026-64108CVE-2026-64010CVE-2026-64000CVE-2026-64118CVE-2026-64114CVE-2026-64117CVE-2026-64111CVE-2026-64112CVE-2026-64113CVE-2026-64116CVE-2026-64121CVE-2026-64007CVE-2026-64115CVE-2026-63994CVE-2026-64109CVE-2026-63993CVE-2026-63992CVE-2026-63984、 、 、 CVE-2026-64191CVE-2026-64144CVE-2026-64147CVE-2026-64148CVE-2026-64138CVE-2026-64155CVE-2026-64153CVE-2026-64160CVE-2026-64163CVE-2026-64165CVE-2026-64166CVE-2026-64168CVE-2026-64137CVE-2026-64173CVE-2026-64170CVE-2026-64174CVE-2026-64177CVE-2026-64178CVE-2026-64179CVE-2026-64180CVE-2026-64136CVE-2026-64183CVE-2026-64182CVE-2026-64184CVE-2026-64185CVE-2026-64206CVE-2026-64237CVE-2026-64231CVE-2026-64225CVE-2026-64247CVE-2026-64221CVE-2026-64220CVE-2026-64219CVE-2026-64249CVE-2026-64218CVE-2026-64217CVE-2026-64214CVE-2026-64268CVE-2026-64135CVE-2026-64133CVE-2026-64361CVE-2026-64315CVE-2026-64355CVE-2026-64280CVE-2026-64303CVE-2026-64313CVE-2026-64320CVE-2026-64364CVE-2026-64134CVE-2026-64319CVE-2026-64128CVE-2026-64269CVE-2026-64127CVE-2026-64126CVE-2026-64125、 、 、 CVE-2026-64552CVE-2026-64394CVE-2026-64396CVE-2026-64397CVE-2026-64393CVE-2026-64400CVE-2026-64399CVE-2026-64408CVE-2026-64438CVE-2026-64441CVE-2026-64445CVE-2026-64450CVE-2026-64392CVE-2026-64510CVE-2026-64475CVE-2026-64518CVE-2026-64523CVE-2026-64529CVE-2026-64530CVE-2026-64534CVE-2026-64391CVE-2026-64541CVE-2026-64535CVE-2026-64548CVE-2026-64551CVE-2026-64554CVE-2026-68082CVE-2026-64598CVE-2026-64597CVE-2026-68083CVE-2026-64586CVE-2026-64564CVE-2026-64562CVE-2026-68117CVE-2026-64561CVE-2026-64557CVE-2026-64555CVE-2026-68123CVE-2026-64390CVE-2026-64386CVE-2026-68154CVE-2026-68138CVE-2026-68152CVE-2026-68127CVE-2026-68136CVE-2026-68137CVE-2026-68147CVE-2026-68156CVE-2026-64387CVE-2026-68144CVE-2026-64385CVE-2026-68124CVE-2026-64384CVE-2026-64383CVE-2026-64382、 、 、 CVE-2026-72083CVE-2026-68228CVE-2026-68229CVE-2026-68300CVE-2026-68213CVE-2026-68343CVE-2026-68302CVE-2026-68381CVE-2026-68388CVE-2026-68426CVE-2026-68431CVE-2026-68457CVE-2026-68210CVE-2026-68470CVE-2026-68461CVE-2026-68476CVE-2026-68477CVE-2026-72014CVE-2026-72020CVE-2026-72033CVE-2026-68209CVE-2026-72065CVE-2026-72041CVE-2026-72069CVE-2026-72071CVE-2026-72084CVE-2026-72191CVE-2026-72130CVE-2026-72129CVE-2026-72192CVE-2026-72126CVE-2026-72125CVE-2026-72124CVE-2026-72194CVE-2026-72111CVE-2026-72098CVE-2026-72085CVE-2026-72200CVE-2026-68206CVE-2026-68162CVE-2026-72289CVE-2026-72234CVE-2026-72288CVE-2026-72221CVE-2026-72222CVE-2026-72226CVE-2026-72255CVE-2026-72296CVE-2026-68198CVE-2026-72251CVE-2026-68161CVE-2026-72217CVE-2026-68160CVE-2026-68159CVE-2026-68158、 、 、 CVE-2026-72499CVE-2026-72351CVE-2026-72380CVE-2026-72383CVE-2026-72348CVE-2026-72399CVE-2026-72398CVE-2026-72421CVE-2026-72422CVE-2026-72434CVE-2026-72436CVE-2026-72451CVE-2026-72339CVE-2026-72466CVE-2026-72454CVE-2026-72472CVE-2026-72473CVE-2026-72487CVE-2026-72488CVE-2026-72489CVE-2026-72329CVE-2026-72494CVE-2026-72491CVE-2026-72495CVE-2026-72496CVE-2026-74255CVE-2026-74305CVE-2026-74302CVE-2026-74287CVE-2026-74310CVE-2026-74280CVE-2026-74279CVE-2026-74269CVE-2026-74345CVE-2026-74268CVE-2026-74267CVE-2026-74264CVE-2026-74350CVE-2026-72323CVE-2026-72320CVE-2026-74408CVE-2026-74401CVE-2026-74407CVE-2026-74384CVE-2026-74394CVE-2026-74398CVE-2026-74406CVE-2026-74410CVE-2026-72322CVE-2026-74405CVE-2026-72319CVE-2026-74376CVE-2026-72318CVE-2026-72317CVE-2026-72299、 、 、 CVE-2026-74495CVE-2026-74474CVE-2026-74473CVE-2026-74439CVE-2026-74556CVE-2026-74493CVE-2026-74541CVE-2026-74476CVE-2026-74478CVE-2026-74480CVE-2026-74538CVE-2026-74569CVE-2026-74440CVE-2026-74521CVE-2026-74436CVE-2026-74475CVE-2026-74427CVE-2026-74417CVE-2026-74411

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

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
365767	Ubuntu 26.04 LTS：Linux 内核漏洞 (USN-8887-1)	Nessus	Ubuntu Local Security Checks	2026/10/14	2026/10/14	medium
337226	Amazon Linux 2023：bpftool、kernel、kernel-devel (ALAS2023-2026-2058)	Nessus	Amazon Linux Local Security Checks	2026/8/18	2026/9/10	high
365525	Ubuntu 24.04 LTS：Linux kernel (Azure) 漏洞 (USN-8918-1)	Nessus	Ubuntu Local Security Checks	2026/10/14	2026/10/14	medium
341880	Amazon Linux 2023：bpftool6.18、kernel6.18、kernel6.18-devel (ALAS2023-2026-2071)	Nessus	Amazon Linux Local Security Checks	2026/8/31	2026/9/15	high
374299	AlmaLinux 9.6 [TuxCare] 安全更新：kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / 等多个漏洞（ALMALINUX9.6：CLSA-2026：1793370479）	Nessus	Alma Linux Local Security Checks	2026/10/30	2026/10/30	high
365522	Ubuntu 24.04 LTS：Linux 内核漏洞 (USN-8917-1)	Nessus	Ubuntu Local Security Checks	2026/10/14	2026/10/14	medium
374300	Rocky Linux 9.6 [TuxCare] 安全更新：kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / 等多个漏洞（ALMALINUX9.6：CLSA-2026：1793370479）	Nessus	Rocky Linux Local Security Checks	2026/10/30	2026/10/30	high
335605	Linux Distros 未修补的漏洞：CVE-2026-72487	Nessus	Misc.	2026/8/15	2026/11/7	high
365768	Ubuntu 26.04 LTS：Linux kernel (Azure) 漏洞 (USN-8888-1)	Nessus	Ubuntu Local Security Checks	2026/10/14	2026/10/14	medium
343049	Oracle Linux 10 / 9：Unbreakable Enterprise 内核 (ELSA-2026-500248)	Nessus	Oracle Linux Local Security Checks	2026/9/4	2026/9/23	high
348386	Ubuntu 24.04 LTS / Pro Realtime 24.04 LTS：Linux 内核（NVIDIA Tegra）漏洞（USN-8781-1）	Nessus	Ubuntu Local Security Checks	2026/9/21	2026/9/21	high
365463	Ubuntu 26.04 LTS：Linux 内核 (OEM) 漏洞 (USN-8889-1)	Nessus	Ubuntu Local Security Checks	2026/10/13	2026/10/13	medium
337239	Amazon Linux 2023：bpftool6.12、kernel6.12、kernel6.12-devel （ALAS2023-2026-2057）	Nessus	Amazon Linux Local Security Checks	2026/8/18	2026/9/23	high

检测

插件搜索

medium

high

medium

high

high

medium

high

high

medium

high

high

medium

high