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 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

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 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

遠端 Ubuntu 24.04 LTS 主機上安裝的一個套件受到 USN-8886-1 公告中所提及的多個弱點影響。

    在 Linux 核心中發現數個安全性問題。攻擊者可能會利用這些弱點入侵系統。此更新可更正下列子系統中的瑕疵：

    - NVDIMM (非易失性記憶體裝置) 驅動程式；

    - 交握 API；

    - ARM32 架構；

    - ARM64 架構 ;

    - MIPS 架構；

    - OpenRISC 架構；

    - PowerPC 架構；

    - S390 架構；

    - x86 架構;

    - 區塊層子系統；

    - 密碼編譯 API;

    - 英特爾 NPU 驅動程式;

    - Android 驅動程式 ;

    - Rados 區塊裝置 （RBD） 驅動程式;

    - 藍牙驅動程式;

    - 硬體亂數產生器核心；

    - TPM 裝置驅動程式；

    - CPU 頻率縮放架構;

    - 硬體加密裝置驅動程式；

    - DMA 引擎子系統;

    - FireWire 子系統；

    - 適用於 ARMv8-A(FFA) 的 Arm 韌體架構；

    - GPIO 子系統；

    - GPU 驅動程式；

    - HID 子系統 ;

    - 硬體監控驅動程式;

    - CoreSight 硬體追蹤驅動程式;

    - I2C 子系統；

    - IIO ADC 驅動程式；

    - IIO 子系統；

    - InfiniBand 驅動程式;

    - 輸入裝置核心驅動程式;

    - 輸入裝置 (滑鼠) 驅動程式；

    - IOMMU 子系統;

    - 多個裝置驅動程式；

    - 媒體驅動程式；

    - 多功能裝置驅動程式；

    - Fastrpc 驅動程式 ;

    - Amazon Nitro 安全模組驅動程式;

    - MMC 子系統；

    - MTD 區塊裝置驅動程式；

    - 乙太網路綁定驅動程式；

    - 網路驅動程式；

    - Mellanox 網路驅動程式；

    - Texas Instruments 網路驅動程式；

    - NTB 驅動程式；

    - NVME 驅動程式；

    - NVMEM（非揮發性記憶體）驅動程式;

    - Parport 驅動程式；

    - 針腳控制器子系統；

    - x86 平台驅動程式；

    - i.MX PM 網域；

    - 系統重置/關閉驅動程序;

    - PTP 時鐘架構；

    - 電壓和電流調節器驅動程式；

    - S/390 驅動程式 ;

    - SCSI 子系統 ;

    - SPI 子系統；

    - Realtek RTL8723BS SDIO 驅動程式；

    - VME 匯流排暫存驅動程式;

    - 熱驅動程式；

    - Thunderbolt 和 USB4 驅動程式 ;

    - TTY 驅動程式；

    - DesignWare USB2 驅動程式;

    - USB Gadget 驅動程式；

    - USB 主機控制器驅動程式；

    - USB Dual Role (OTG-ready) 控制器驅動程式；

    - USB 序列驅動程式；

    - USB Type-C Port Controller Manager 驅動程式；

    - vDPA 驅動程式;

    - Virtio Host (VHOST) 子系統;

    - Framebuffer 層；

    - Watchdog 驅動程式；

    - 9P 分散式檔案系統 ;

    - AFS 檔案系統;

    - 檔案系統基礎架構；

    - BTRFS 檔案系統 ;

    - Ceph 分散式檔案系統；

    - EROFS 檔案系統；

    - AexFAT 檔案系統；

    - F2FS 檔案系統；

    - FUSE (使用者空間中的檔案系統)；

    - 區塊裝置的日誌記錄層 (JBD2)；

    - 網路檔案系統 (NFS) 用戶端；

    - 網路檔案系統 (NFS) 伺服器程序；

    - NTFS3 檔案系統；

    - OCFS2 檔案系統；

    - Proc 檔案系統；

    - SMB 網路檔案系統 ;

    - 追蹤檔案系統 ;

    - UDF 檔案系統；

    - XFS 檔案系統；

    - 金鑰管理；

    - BPF 子系統；

    - 控制群組 (cgroup);

    - Glob 模式匹配庫;

    - MAC80211 子系統；

    - Mellanox 驅動程式；

    - 網路核心；

    - 網路通訊端；

    - IPv6 網路；

    - 藍牙子系統；

    - 無線網路 ；

    - IPv4 網路；

    - Netfilter；

    - 網路流量控制 ;

    - SCTP 通訊協定；

    - TCP 網路通訊協定；

    - XFRM 子系統；

    - RDMA 動詞 API；

    - io_uring 子系統;

    - IPC 子系統；

    - 稽核子系統；

    - Kernel CPU 控制基礎架構；

    - Perf 事件；

    - 核心 exit() 系統呼叫；

    - 核心 fork() 系統呼叫；

    - 排程器基礎架構；

    - 訊號處理機制；

    - Timer 子系統;

    - 追蹤基礎架構；

    - 可調整大小的雜湊表庫;

    - 記憶體管理；

    - 6LoWPAN網路協定;

    - 非同步傳輸模式 (ATM) 子系統；

    - B.A.T.M.A.N. 網狀通訊協定；

    - 乙太網路橋接器；

    - CAN 網路層

    - Ceph Core 程式庫；

    - Ethtool 驅動程式；

    - HSR 網路通訊協定；

    - IEEE802154.4 網路通訊協定；

    - IUCV 驅動程式；

    - KCM (核心連線多工器) 通訊端驅動程式 ;

    - IEEE 802.15.4 子系統；

    - 多重路徑 TCP;

    Open vSwitch；

    - 封包通訊端；

    - Phonet 通訊協定 ;

    - 高通IPC路由器（QRTR）;

    - RDS 通訊協定;

    - RxRPC 工作階段通訊端；

    - SMC 通訊端;

    - Sun RPC 通訊協定；

    - TIPC 通訊協定 ;

    - TLS 通訊協定；

    - Unix 網域通訊端;

    - VMware vSockets 驅動程式；

    - X.25 network layer;

    - eXpress 資料路徑；

    - AppArmor 安全性模組 ;

    - 完整性測量架構 (IMA) 框架；

    - SELinux 安全性模組；

    - ALSA 架構;

    - HD 音訊驅動程式；

    - QCOM ASoC 驅動程式；

    - 簡單的音頻多路復用器編解碼器驅動程序;

    - Texas InstrumentS Audio (ASoC/HDA) 驅動程式 ;

    - 適用於 Freescale CPU 的 SoC Audio 驅動程式 ;

    - Amlogic Meson SoC 驅動程式；

    - SOF 驅動程式；

    - NVIDIA Tegra ASoC 驅動程式;

    - USB 音效裝置；

    - 性能工具;

    - KVM 子系統;（CVE-2025-37807 ， ， ， CVE-2026-43022， CVE-2026-46321CVE-2026-53267CVE-2026-53160CVE-2026-53161CVE-2026-53136CVE-2026-53137CVE-2026-52994CVE-2026-53143CVE-2026-53138CVE-2026-53146CVE-2026-53147CVE-2026-53149CVE-2026-53156CVE-2026-53157CVE-2026-52947CVE-2026-53189CVE-2026-53184CVE-2026-53194CVE-2026-53195CVE-2026-53199CVE-2026-53202CVE-2026-53205CVE-2026-52943CVE-2026-53223CVE-2026-53209CVE-2026-53229CVE-2026-53253CVE-2026-53255CVE-2026-53268CVE-2026-53272CVE-2026-52942CVE-2026-53330CVE-2026-53329CVE-2026-53389CVE-2026-53388CVE-2026-53390CVE-2026-53387CVE-2026-53383CVE-2026-53381CVE-2026-53391CVE-2026-53366CVE-2026-53365CVE-2026-53362CVE-2026-53392CVE-2026-53356CVE-2026-52935CVE-2026-53397CVE-2026-63794CVE-2026-53402CVE-2026-63802CVE-2026-53401CVE-2026-63803CVE-2026-63805CVE-2026-46322CVE-2026-52923CVE-2026-63806CVE-2026-52917CVE-2026-52927CVE-2026-52929CVE-2026-53400CVE-2026-23265、、、 CVE-2026-64005CVE-2026-63869CVE-2026-63867CVE-2026-63870CVE-2026-63875CVE-2026-63879CVE-2026-63881CVE-2026-63884CVE-2026-63833CVE-2026-63909CVE-2026-63889CVE-2026-63913CVE-2026-63920CVE-2026-63925CVE-2026-63927CVE-2026-63930CVE-2026-63827CVE-2026-63954CVE-2026-63942CVE-2026-63968CVE-2026-63970CVE-2026-63971CVE-2026-63985CVE-2026-64002CVE-2026-63824CVE-2026-64004CVE-2026-64003CVE-2026-64009CVE-2026-64017CVE-2026-64023CVE-2026-64239CVE-2026-64222CVE-2026-64210CVE-2026-64242CVE-2026-64189CVE-2026-64188CVE-2026-64123CVE-2026-64243CVE-2026-64095CVE-2026-64036CVE-2026-64026CVE-2026-64245CVE-2026-63823CVE-2026-63817CVE-2026-64277CVE-2026-64272CVE-2026-64276CVE-2026-64266CVE-2026-64270CVE-2026-64271CVE-2026-64274CVE-2026-64279CVE-2026-63819CVE-2026-64273CVE-2026-63816CVE-2026-64246CVE-2026-63814CVE-2026-63812CVE-2026-63809、 、 、 、 CVE-2026-64418CVE-2026-64322CVE-2026-64318CVE-2026-64324CVE-2026-64323CVE-2026-64333CVE-2026-64368CVE-2026-64372CVE-2026-64374CVE-2026-64375CVE-2026-64317CVE-2026-64379CVE-2026-64378CVE-2026-64380CVE-2026-64388CVE-2026-64389CVE-2026-64395CVE-2026-64398CVE-2026-64312CVE-2026-64402CVE-2026-64401CVE-2026-64403CVE-2026-64411CVE-2026-64412CVE-2026-64413CVE-2026-64442CVE-2026-64440CVE-2026-64443CVE-2026-64436CVE-2026-64435CVE-2026-64432CVE-2026-64444CVE-2026-64430CVE-2026-64423CVE-2026-64422CVE-2026-64448CVE-2026-64420CVE-2026-64304CVE-2026-64299CVE-2026-64298CVE-2026-64532CVE-2026-64463CVE-2026-64468CVE-2026-64469CVE-2026-64456CVE-2026-64496CVE-2026-64533CVE-2026-64481CVE-2026-64449CVE-2026-64452CVE-2026-64524CVE-2026-64296CVE-2026-64287CVE-2026-64286CVE-2026-64283、 、 、 、 CVE-2026-68104CVE-2026-64563CVE-2026-64560CVE-2026-64568CVE-2026-64567CVE-2026-64570CVE-2026-64574CVE-2026-64576CVE-2026-64577CVE-2026-64578CVE-2026-64556CVE-2026-64581CVE-2026-64580CVE-2026-64582CVE-2026-64583CVE-2026-64584CVE-2026-64585CVE-2026-64599CVE-2026-64550CVE-2026-68091CVE-2026-64600CVE-2026-68096CVE-2026-68097CVE-2026-68098CVE-2026-68100CVE-2026-68129CVE-2026-68125CVE-2026-68131CVE-2026-68121CVE-2026-68119CVE-2026-68118CVE-2026-68140CVE-2026-68116CVE-2026-68108CVE-2026-68107CVE-2026-68141CVE-2026-68106CVE-2026-64547CVE-2026-64546CVE-2026-64545CVE-2026-68179CVE-2026-68148CVE-2026-68149CVE-2026-68153CVE-2026-68145CVE-2026-68157CVE-2026-68189CVE-2026-68155CVE-2026-68142CVE-2026-68143CVE-2026-68178CVE-2026-64543CVE-2026-64540CVE-2026-64539CVE-2026-64536、 、 、 、 CVE-2026-68329CVE-2026-68253CVE-2026-68245CVE-2026-68258CVE-2026-68255CVE-2026-68260CVE-2026-68262CVE-2026-68263CVE-2026-68266CVE-2026-68273CVE-2026-68236CVE-2026-68287CVE-2026-68284CVE-2026-68290CVE-2026-68293CVE-2026-68294CVE-2026-68297CVE-2026-68299CVE-2026-68222CVE-2026-68315CVE-2026-68314CVE-2026-68320CVE-2026-68322CVE-2026-68323CVE-2026-68326CVE-2026-68371CVE-2026-68370CVE-2026-68373CVE-2026-68354CVE-2026-68353CVE-2026-68352CVE-2026-68376CVE-2026-68348CVE-2026-68340CVE-2026-68338CVE-2026-68377CVE-2026-68335CVE-2026-68219CVE-2026-68216CVE-2026-68204CVE-2026-68402CVE-2026-68392CVE-2026-68397CVE-2026-68398CVE-2026-68391CVE-2026-68400CVE-2026-68404CVE-2026-68399CVE-2026-68383CVE-2026-68389CVE-2026-68401CVE-2026-68202CVE-2026-68199CVE-2026-68196CVE-2026-68192、 、 、 、 CVE-2026-72049CVE-2026-68446CVE-2026-68445CVE-2026-68451CVE-2026-68447CVE-2026-68452CVE-2026-68453CVE-2026-68454CVE-2026-68466CVE-2026-68467CVE-2026-68442CVE-2026-68474CVE-2026-68471CVE-2026-68479CVE-2026-72005CVE-2026-72009CVE-2026-72012CVE-2026-72019CVE-2026-68433CVE-2026-72024CVE-2026-72021CVE-2026-72029CVE-2026-72035CVE-2026-72036CVE-2026-72045CVE-2026-72067CVE-2026-72066CVE-2026-72072CVE-2026-72061CVE-2026-72057CVE-2026-72055CVE-2026-72089CVE-2026-72054CVE-2026-72053CVE-2026-72052CVE-2026-72099CVE-2026-72051CVE-2026-68432CVE-2026-68425CVE-2026-68419CVE-2026-72116CVE-2026-72108CVE-2026-72109CVE-2026-72110CVE-2026-72107CVE-2026-72114CVE-2026-72117CVE-2026-72113CVE-2026-72102CVE-2026-72105CVE-2026-72115CVE-2026-68417CVE-2026-68414CVE-2026-68409CVE-2026-68408、 、 、 、 CVE-2026-72233CVE-2026-72146CVE-2026-72144CVE-2026-72149CVE-2026-72148CVE-2026-72157CVE-2026-72160CVE-2026-72162CVE-2026-72164CVE-2026-72165CVE-2026-72136CVE-2026-72171CVE-2026-72170CVE-2026-72172CVE-2026-72175CVE-2026-72181CVE-2026-72195CVE-2026-72196CVE-2026-72135CVE-2026-72213CVE-2026-72197CVE-2026-72225CVE-2026-72227CVE-2026-72231CVE-2026-72232CVE-2026-72254CVE-2026-72253CVE-2026-72261CVE-2026-72252CVE-2026-72250CVE-2026-72247CVE-2026-72262CVE-2026-72244CVE-2026-72243CVE-2026-72242CVE-2026-72282CVE-2026-72235CVE-2026-72133CVE-2026-72123CVE-2026-72122CVE-2026-72330CVE-2026-72301CVE-2026-72302CVE-2026-72304CVE-2026-72298CVE-2026-72312CVE-2026-72334CVE-2026-72310CVE-2026-72284CVE-2026-72297CVE-2026-72314CVE-2026-72121CVE-2026-72120CVE-2026-72119CVE-2026-72118、 、 、 、 CVE-2026-72435CVE-2026-72373CVE-2026-72371CVE-2026-72375CVE-2026-72374CVE-2026-72378CVE-2026-72382CVE-2026-72389CVE-2026-72390CVE-2026-72397CVE-2026-72369CVE-2026-72404CVE-2026-72400CVE-2026-72405CVE-2026-72406CVE-2026-72409CVE-2026-72410CVE-2026-72416CVE-2026-72352CVE-2026-72419CVE-2026-72418CVE-2026-72420CVE-2026-72423CVE-2026-72425CVE-2026-72427CVE-2026-72469CVE-2026-72464CVE-2026-72470CVE-2026-72460CVE-2026-72459CVE-2026-72450CVE-2026-72476CVE-2026-72449CVE-2026-72444CVE-2026-72440CVE-2026-72478CVE-2026-72438CVE-2026-72350CVE-2026-72347CVE-2026-72343CVE-2026-74270CVE-2026-72492CVE-2026-72502CVE-2026-74256CVE-2026-72485CVE-2026-74258CVE-2026-74281CVE-2026-74257CVE-2026-72480CVE-2026-72483CVE-2026-74262CVE-2026-72342CVE-2026-72340CVE-2026-72338CVE-2026-72335、 、 、 、 CVE-2026-74378CVE-2026-74300CVE-2026-74297CVE-2026-74313CVE-2026-74312CVE-2026-74314CVE-2026-74317CVE-2026-74321CVE-2026-74330CVE-2026-74334CVE-2026-74296CVE-2026-74340CVE-2026-74338CVE-2026-74341CVE-2026-74344CVE-2026-74347CVE-2026-74349CVE-2026-74356CVE-2026-74295CVE-2026-74363CVE-2026-74359CVE-2026-74365CVE-2026-74374CVE-2026-74375CVE-2026-74377CVE-2026-74444CVE-2026-74443CVE-2026-74446CVE-2026-74438CVE-2026-74397CVE-2026-74390CVE-2026-74450CVE-2026-74388CVE-2026-74387CVE-2026-74385CVE-2026-74453CVE-2026-74380CVE-2026-74294CVE-2026-74293CVE-2026-74292CVE-2026-74481CVE-2026-74465CVE-2026-74467CVE-2026-74469CVE-2026-74461CVE-2026-74471CVE-2026-74482CVE-2026-74470CVE-2026-74454CVE-2026-74456CVE-2026-74479CVE-2026-74289CVE-2026-74288CVE-2026-74283CVE-2026-74282、 、 、 、 CVE-2026-74557CVE-2026-74512CVE-2026-74510CVE-2026-74516CVE-2026-74515CVE-2026-74518CVE-2026-74519CVE-2026-74522CVE-2026-74523CVE-2026-74527CVE-2026-74509CVE-2026-74531CVE-2026-74530CVE-2026-74533CVE-2026-74534CVE-2026-74535CVE-2026-74536CVE-2026-74537CVE-2026-74508CVE-2026-74544CVE-2026-74540CVE-2026-74548CVE-2026-74549CVE-2026-74550CVE-2026-74551CVE-2026-74579CVE-2026-74578CVE-2026-74580CVE-2026-74575CVE-2026-74574CVE-2026-74572CVE-2026-74581CVE-2026-74567CVE-2026-74565CVE-2026-74564CVE-2026-74582CVE-2026-74563CVE-2026-74507CVE-2026-74497CVE-2026-74496CVE-2026-74595CVE-2026-74587CVE-2026-74588CVE-2026-74589CVE-2026-74586CVE-2026-74592CVE-2026-74597CVE-2026-74590CVE-2026-74583CVE-2026-74584CVE-2026-74594CVE-2026-74492CVE-2026-74490CVE-2026-74488CVE-2026-74485、 、 、 、 CVE-2026-74649CVE-2026-74611CVE-2026-74610CVE-2026-74613CVE-2026-74612CVE-2026-74614CVE-2026-74615CVE-2026-74616CVE-2026-74621CVE-2026-74624CVE-2026-74609CVE-2026-74626CVE-2026-74625CVE-2026-74628CVE-2026-74630CVE-2026-74631CVE-2026-74632CVE-2026-74634CVE-2026-74608CVE-2026-74637CVE-2026-74635CVE-2026-74641CVE-2026-74646CVE-2026-74647CVE-2026-74648CVE-2026-74668CVE-2026-74667CVE-2026-74669CVE-2026-74666CVE-2026-74663CVE-2026-74662CVE-2026-74670CVE-2026-74661CVE-2026-74660CVE-2026-74656CVE-2026-74675CVE-2026-74651CVE-2026-74607CVE-2026-74606CVE-2026-74605CVE-2026-74696CVE-2026-74688CVE-2026-74689CVE-2026-74690CVE-2026-74687CVE-2026-74692CVE-2026-74697CVE-2026-74691CVE-2026-74678CVE-2026-74684CVE-2026-74695CVE-2026-74604CVE-2026-74603CVE-2026-74601CVE-2026-74598、 、 、 、 CVE-2026-80540CVE-2026-74720CVE-2026-74717CVE-2026-74724CVE-2026-74723CVE-2026-74725CVE-2026-74726CVE-2026-74730CVE-2026-74733CVE-2026-74736CVE-2026-74715CVE-2026-74739CVE-2026-74737CVE-2026-74743CVE-2026-74744CVE-2026-74746CVE-2026-74747CVE-2026-74748CVE-2026-74714CVE-2026-80521CVE-2026-74752CVE-2026-80526CVE-2026-80527CVE-2026-80528CVE-2026-80536CVE-2026-80554CVE-2026-80553CVE-2026-80555CVE-2026-80552CVE-2026-80551CVE-2026-80550CVE-2026-80556CVE-2026-80549CVE-2026-80548CVE-2026-80547CVE-2026-80557CVE-2026-80541CVE-2026-74713CVE-2026-74711CVE-2026-74710CVE-2026-80574CVE-2026-80561CVE-2026-80565CVE-2026-80568CVE-2026-80560CVE-2026-80570CVE-2026-80576CVE-2026-80569CVE-2026-80558CVE-2026-80559CVE-2026-80572CVE-2026-74705CVE-2026-74704CVE-2026-74701CVE-2026-74700CVE-2026-80578、CVE-2026-80579、、CVE-2026-80580、CVE-2026-80583CVE-2026-80901CVE-2026-97509CVE-2026-80589CVE-2026-80586CVE-2026-80721CVE-2026-80584CVE-2026-80585CVE-2026-80587）

Tenable 已直接從 Ubuntu 安全公告擷取前置描述區塊。

請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

Linux/Unix 主機上安裝了一個或多個受到弱點影響的套件，且廠商未提供可用的修補程式。

  - md/raid1：修正寫入失敗時的 writes_pending 和屏障參照洩漏 raid1_make_request（） 在呼叫 raid1_write_request（） 之前使用 md_write_start（） 取得writes_pending參照。raid1_write_request（） 中的幾個失敗路徑完成 bio 並返回，而沒有到達正常的寫入完成路徑，導致對應的 md_write_end（） 被跳過。使 raid1_write_request（） 傳回一個狀態，指示寫入要求是否已成功排入佇列。這允許 raid1_make_request（） 在 raid1_write_request（） 失敗時呼叫 md_write_end（）。此外，如果 wait_blocked_rdev（） 在 wait_barrier（） 成功後失敗，則不會釋放相關聯的屏障參照。在從該路徑返回之前呼叫 allow_barrier（），以保持障礙會計的平衡。（CVE-2026-72440）

請注意，Nessus 的判定取決於廠商所報告的套件是否存在。

ID	名稱	產品	系列	已發布	已更新	嚴重性
374300	Rocky Linux 9.6 [TuxCare] 安全性更新：kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc 多個弱點（ALMALINUX9.6：CLSA-2026：1793370479）	Nessus	Rocky Linux Local Security Checks	2026/10/30	2026/10/30	high
365768	Ubuntu 26.04 LTS：Linux 核心 (Azure) 弱點 (USN-8888-1)	Nessus	Ubuntu Local Security Checks	2026/10/14	2026/10/14	medium
365767	Ubuntu 26.04 LTS : Linux 核心弱點 (USN-8887-1)	Nessus	Ubuntu Local Security Checks	2026/10/14	2026/10/14	medium
374299	AlmaLinux 9.6 [TuxCare] 安全性更新：kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc 多個弱點（ALMALINUX9.6：CLSA-2026：1793370479）	Nessus	Alma Linux Local Security Checks	2026/10/30	2026/10/30	high
365457	Ubuntu 24.04 LTS：Linux 核心 (NVIDIA Tegra) 弱點 (USN-8886-1)	Nessus	Ubuntu Local Security Checks	2026/10/13	2026/10/13	high
365463	Ubuntu 26.04 LTS：Linux 核心 (OEM) 弱點 (USN-8889-1)	Nessus	Ubuntu Local Security Checks	2026/10/13	2026/10/13	medium
335628	Linux Distros 未修補弱點：CVE-2026-72440	Nessus	Misc.	2026/8/15	2026/10/19	high

偵測

搜尋 Plugin

high

medium

medium

high

high

medium

high