AlmaLinux 9.2 主機已安裝的套件會受到 TuxCare ALMALINUX9.2：CLSA-2026：1767864313 公告中提及的多個弱點影響。

  - 已解決 Linux 核心中的下列弱點：firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails When scpi probe fails, at any point, we need to ensure that the scpi_info is not set and will remain NULL until the probe succeeds. If it is not taken care, then it could result use-after-free as the value is exported via get_scpi_ops() and could refer to a memory allocated via devm_kzalloc() but freed when the probe fails. (CVE-2022-50087)

  - 已解決 Linux 核心中的下列弱點：wifi: rtlwifi: Fix global-out-of-bounds bug in _rtl8812ae_phy_set_txpower_limit() There is a global-out-of-bounds reported by KASAN: BUG:
    KASAN: global-out-of-bounds in _rtl8812ae_eq_n_byte.part.0+0x3d/0x84 [rtl8821ae] Read of size 1 at addr ffffffffa0773c43 by task NetworkManager/411 CPU: 6 PID: 411 Comm: NetworkManager Tainted: G D 6.1.0-rc8+ #144 e15588508517267d37 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), Call Trace: <TASK> ...
    kasan_report+0xbb/0x1c0 _rtl8812ae_eq_n_byte.part.0+0x3d/0x84 [rtl8821ae] rtl8821ae_phy_bb_config.cold+0x346/0x641 [rtl8821ae] rtl8821ae_hw_init+0x1f5e/0x79b0 [rtl8821ae] ...
    </TASK> The root cause of the problem is that the comparison order of prate_section in
    _rtl8812ae_phy_set_txpower_limit() is wrong. The _rtl8812ae_eq_n_byte() is used to compare the first n bytes of the two strings from tail to head, which causes the problem. In the
    _rtl8812ae_phy_set_txpower_limit(), it was originally intended to meet this requirement by carefully designing the comparison order. For example, pregulation and pbandwidth are compared in order of length from small to large, first is 3 and last is 4. However, the comparison order of prate_section dose not obey such order requirement, therefore when prate_section is HT, when comparing from tail to head, it will lead to access out of bounds in _rtl8812ae_eq_n_byte(). As mentioned above, the
    _rtl8812ae_eq_n_byte() has the same function as strcmp(), so just strcmp() is enough. Fix it by removing
    _rtl8812ae_eq_n_byte() and use strcmp() barely. Although it can be fixed by adjusting the comparison order of prate_section, this may cause the value of rate_section to not be from 0 to 5. In addition, commit 21e4b0726dc6 not only moved driver from staging to regular tree, but also added setting txpower limit function during the driver config phase, so the problem was introduced by this commit. (CVE-2022-50279)

  - 已解決 Linux 核心中的下列弱點：wifi: ath11k: fix monitor mode bringup crash When the interface is brought up in monitor mode, it leads to NULL pointer dereference crash. This crash happens when the packet type is extracted for a SKB. This extraction which is present in the received msdu delivery path,is not needed for the monitor ring packets since they are all RAW packets.
    Hence appending the flags with RX_FLAG_ONLY_MONITOR to skip that extraction. Observed calltrace: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000064 Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004 CM = 0, WnR = 0 user pgtable:
    4k pages, 48-bit VAs, pgdp=0000000048517000 [0000000000000064] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP Modules linked in: ath11k_pci ath11k qmi_helpers CPU: 2 PID: 1781 Comm: napi/-271 Not tainted 6.1.0-rc5-wt-ath-656295-gef907406320c-dirty #6 Hardware name:
    Qualcomm Technologies, Inc. IPQ8074/AP-HK10-C2 (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : ath11k_hw_qcn9074_rx_desc_get_decap_type+0x34/0x60 [ath11k] lr :
    ath11k_hw_qcn9074_rx_desc_get_decap_type+0x5c/0x60 [ath11k] sp : ffff80000ef5bb10 x29: ffff80000ef5bb10 x28: 0000000000000000 x27: ffff000007baafa0 x26: ffff000014a91ed0 x25: 0000000000000000 x24:
    0000000000000000 x23: ffff800002b77378 x22: ffff000014a91ec0 x21: ffff000006c8d600 x20: 0000000000000000 x19: ffff800002b77740 x18: 0000000000000006 x17: 736564203634343a x16: 656e694c20657079 x15:
    0000000000000143 x14: 00000000ffffffea x13: ffff80000ef5b8b8 x12: ffff80000ef5b8c8 x11: ffff80000a591d30 x10: ffff80000a579d40 x9 : c0000000ffffefff x8 : 0000000000000003 x7 : 0000000000017fe8 x6 :
    ffff80000a579ce8 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 x2 : 3a35ec12ed7f8900 x1 : 0000000000000000 x0 : 0000000000000052 Call trace: ath11k_hw_qcn9074_rx_desc_get_decap_type+0x34/0x60 [ath11k] ath11k_dp_rx_deliver_msdu.isra.42+0xa4/0x3d0 [ath11k] ath11k_dp_rx_mon_deliver.isra.43+0x2f8/0x458 [ath11k] ath11k_dp_rx_process_mon_rings+0x310/0x4c0 [ath11k] ath11k_dp_service_srng+0x234/0x338 [ath11k] ath11k_pcic_ext_grp_napi_poll+0x30/0xb8 [ath11k]
    __napi_poll+0x5c/0x190 napi_threaded_poll+0xf0/0x118 kthread+0xf4/0x110 ret_from_fork+0x10/0x20 Tested-on:
    QCN9074 hw1.0 PCI WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1 (CVE-2022-50627)

  - 已解決 Linux 核心中的下列弱點：mm: hugetlb: fix UAF in hugetlb_handle_userfault The vma_lock and hugetlb_fault_mutex are dropped before handling userfault and reacquire them again after handle_userfault(), but reacquire the vma_lock could lead to UAF[1,2] due to the following race, hugetlb_fault hugetlb_no_page /*unlock vma_lock */ hugetlb_handle_userfault handle_userfault /* unlock mm->mmap_lock*/ vm_mmap_pgoff do_mmap mmap_region munmap_vma_range /* clean old vma */ /* lock vma_lock again <--- UAF */ /* unlock vma_lock */ Since the vma_lock will unlock immediately after hugetlb_handle_userfault(), let's drop the unneeded lock and unlock in hugetlb_handle_userfault() to fix the issue. [1] https://lore.kernel.org/linux-mm/000000000000d5e00a05e834962e@google.com/ [2] https://lore.kernel.org/linux-mm/20220921014457.1668-1-liuzixian4@huawei.com/ (CVE-2022-50630)

  - 已解決 Linux 核心中的下列弱點：PCI: Fix pci_device_is_present() for VFs by checking PF pci_device_is_present() previously didn't work for VFs because it reads the Vendor and Device ID, which are 0xffff for VFs, which looks like they aren't present. Check the PF instead. Wei Gong reported that if virtio I/O is in progress when the driver is unbound or 0 is written to /sys/.../sriov_numvfs, the virtio I/O operation hangs, which may result in output like this: task:bash state:D stack: 0 pid: 1773 ppid: 1241 flags:0x00004002 Call Trace: schedule+0x4f/0xc0 blk_mq_freeze_queue_wait+0x69/0xa0 blk_mq_freeze_queue+0x1b/0x20 blk_cleanup_queue+0x3d/0xd0 virtblk_remove+0x3c/0xb0 [virtio_blk] virtio_dev_remove+0x4b/0x80 ... device_unregister+0x1b/0x60 unregister_virtio_device+0x18/0x30 virtio_pci_remove+0x41/0x80 pci_device_remove+0x3e/0xb0 This happened because pci_device_is_present(VF) returned false in virtio_pci_remove(), so it called virtio_break_device(). The broken vq meant that vring_interrupt() skipped the vq.callback() that would have completed the virtio I/O operation via virtblk_done(). [bhelgaas: commit log, simplify to always use pci_physfn(), add stable tag] (CVE-2022-50636)

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

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

  - drm/amdkfd修正 kfd_process_device_translate_handle 傳回的潛在 kgd_mem UAF kgd_mem 指標只有在保留 p->mutex 時才保證有效。解除鎖定 mutex 後另一個執行緒可釋放 BO。 (CVE-2023-53816)

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

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

  - 已修复 Linux 内核中的下列漏洞：firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails When scpi probe fails, at any point, we need to ensure that the scpi_info is not set and will remain NULL until the probe succeeds. If it is not taken care, then it could result use-after-free as the value is exported via get_scpi_ops() and could refer to a memory allocated via devm_kzalloc() but freed when the probe fails. (CVE-2022-50087)

  - 已修复 Linux 内核中的下列漏洞：wifi: rtlwifi: Fix global-out-of-bounds bug in _rtl8812ae_phy_set_txpower_limit() There is a global-out-of-bounds reported by KASAN: BUG:
    KASAN: global-out-of-bounds in _rtl8812ae_eq_n_byte.part.0+0x3d/0x84 [rtl8821ae] Read of size 1 at addr ffffffffa0773c43 by task NetworkManager/411 CPU: 6 PID: 411 Comm: NetworkManager Tainted: G D 6.1.0-rc8+ #144 e15588508517267d37 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), Call Trace: <TASK> ...
    kasan_report+0xbb/0x1c0 _rtl8812ae_eq_n_byte.part.0+0x3d/0x84 [rtl8821ae] rtl8821ae_phy_bb_config.cold+0x346/0x641 [rtl8821ae] rtl8821ae_hw_init+0x1f5e/0x79b0 [rtl8821ae] ...
    </TASK> The root cause of the problem is that the comparison order of prate_section in
    _rtl8812ae_phy_set_txpower_limit() is wrong. The _rtl8812ae_eq_n_byte() is used to compare the first n bytes of the two strings from tail to head, which causes the problem. In the
    _rtl8812ae_phy_set_txpower_limit(), it was originally intended to meet this requirement by carefully designing the comparison order. For example, pregulation and pbandwidth are compared in order of length from small to large, first is 3 and last is 4. However, the comparison order of prate_section dose not obey such order requirement, therefore when prate_section is HT, when comparing from tail to head, it will lead to access out of bounds in _rtl8812ae_eq_n_byte(). As mentioned above, the
    _rtl8812ae_eq_n_byte() has the same function as strcmp(), so just strcmp() is enough. Fix it by removing
    _rtl8812ae_eq_n_byte() and use strcmp() barely. Although it can be fixed by adjusting the comparison order of prate_section, this may cause the value of rate_section to not be from 0 to 5. In addition, commit 21e4b0726dc6 not only moved driver from staging to regular tree, but also added setting txpower limit function during the driver config phase, so the problem was introduced by this commit. (CVE-2022-50279)

  - 已修复 Linux 内核中的下列漏洞：wifi: ath11k: fix monitor mode bringup crash When the interface is brought up in monitor mode, it leads to NULL pointer dereference crash. This crash happens when the packet type is extracted for a SKB. This extraction which is present in the received msdu delivery path,is not needed for the monitor ring packets since they are all RAW packets.
    Hence appending the flags with RX_FLAG_ONLY_MONITOR to skip that extraction. Observed calltrace: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000064 Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004 CM = 0, WnR = 0 user pgtable:
    4k pages, 48-bit VAs, pgdp=0000000048517000 [0000000000000064] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP Modules linked in: ath11k_pci ath11k qmi_helpers CPU: 2 PID: 1781 Comm: napi/-271 Not tainted 6.1.0-rc5-wt-ath-656295-gef907406320c-dirty #6 Hardware name:
    Qualcomm Technologies, Inc. IPQ8074/AP-HK10-C2 (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : ath11k_hw_qcn9074_rx_desc_get_decap_type+0x34/0x60 [ath11k] lr :
    ath11k_hw_qcn9074_rx_desc_get_decap_type+0x5c/0x60 [ath11k] sp : ffff80000ef5bb10 x29: ffff80000ef5bb10 x28: 0000000000000000 x27: ffff000007baafa0 x26: ffff000014a91ed0 x25: 0000000000000000 x24:
    0000000000000000 x23: ffff800002b77378 x22: ffff000014a91ec0 x21: ffff000006c8d600 x20: 0000000000000000 x19: ffff800002b77740 x18: 0000000000000006 x17: 736564203634343a x16: 656e694c20657079 x15:
    0000000000000143 x14: 00000000ffffffea x13: ffff80000ef5b8b8 x12: ffff80000ef5b8c8 x11: ffff80000a591d30 x10: ffff80000a579d40 x9 : c0000000ffffefff x8 : 0000000000000003 x7 : 0000000000017fe8 x6 :
    ffff80000a579ce8 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 x2 : 3a35ec12ed7f8900 x1 : 0000000000000000 x0 : 0000000000000052 Call trace: ath11k_hw_qcn9074_rx_desc_get_decap_type+0x34/0x60 [ath11k] ath11k_dp_rx_deliver_msdu.isra.42+0xa4/0x3d0 [ath11k] ath11k_dp_rx_mon_deliver.isra.43+0x2f8/0x458 [ath11k] ath11k_dp_rx_process_mon_rings+0x310/0x4c0 [ath11k] ath11k_dp_service_srng+0x234/0x338 [ath11k] ath11k_pcic_ext_grp_napi_poll+0x30/0xb8 [ath11k]
    __napi_poll+0x5c/0x190 napi_threaded_poll+0xf0/0x118 kthread+0xf4/0x110 ret_from_fork+0x10/0x20 Tested-on:
    QCN9074 hw1.0 PCI WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1 (CVE-2022-50627)

  - 已修复 Linux 内核中的下列漏洞：mm: hugetlb: fix UAF in hugetlb_handle_userfault The vma_lock and hugetlb_fault_mutex are dropped before handling userfault and reacquire them again after handle_userfault(), but reacquire the vma_lock could lead to UAF[1,2] due to the following race, hugetlb_fault hugetlb_no_page /*unlock vma_lock */ hugetlb_handle_userfault handle_userfault /* unlock mm->mmap_lock*/ vm_mmap_pgoff do_mmap mmap_region munmap_vma_range /* clean old vma */ /* lock vma_lock again <--- UAF */ /* unlock vma_lock */ Since the vma_lock will unlock immediately after hugetlb_handle_userfault(), let's drop the unneeded lock and unlock in hugetlb_handle_userfault() to fix the issue. [1] https://lore.kernel.org/linux-mm/000000000000d5e00a05e834962e@google.com/ [2] https://lore.kernel.org/linux-mm/20220921014457.1668-1-liuzixian4@huawei.com/ (CVE-2022-50630)

  - 已修复 Linux 内核中的下列漏洞：PCI: Fix pci_device_is_present() for VFs by checking PF pci_device_is_present() previously didn't work for VFs because it reads the Vendor and Device ID, which are 0xffff for VFs, which looks like they aren't present. Check the PF instead. Wei Gong reported that if virtio I/O is in progress when the driver is unbound or 0 is written to /sys/.../sriov_numvfs, the virtio I/O operation hangs, which may result in output like this: task:bash state:D stack: 0 pid: 1773 ppid: 1241 flags:0x00004002 Call Trace: schedule+0x4f/0xc0 blk_mq_freeze_queue_wait+0x69/0xa0 blk_mq_freeze_queue+0x1b/0x20 blk_cleanup_queue+0x3d/0xd0 virtblk_remove+0x3c/0xb0 [virtio_blk] virtio_dev_remove+0x4b/0x80 ... device_unregister+0x1b/0x60 unregister_virtio_device+0x18/0x30 virtio_pci_remove+0x41/0x80 pci_device_remove+0x3e/0xb0 This happened because pci_device_is_present(VF) returned false in virtio_pci_remove(), so it called virtio_break_device(). The broken vq meant that vring_interrupt() skipped the vq.callback() that would have completed the virtio I/O operation via virtblk_done(). [bhelgaas: commit log, simplify to always use pci_physfn(), add stable tag] (CVE-2022-50636)

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

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

  - drm/amdkfd修复潜在的 kgd_mem UAF 仅当保留 p->mutex 时才能保证由 kfd_process_device_translate_handle 返回的 kgd_mem 指针有效。互斥体解锁后另一个线程就可以释放 BO。 (CVE-2023-53816)

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

リモートの SUSE Linux SLES15 / SLES_SAP15 ホストには、SUSE-SU-2026:0317-1 のアドバイザリに記載された複数の脆弱性の影響を受けるパッケージがインストールされています。

    SUSE Linux Enterprise 15 SP5 のカーネルが更新され、いくつかの問題が修正されました。

    以下のセキュリティ問題が修正されました。

    - CVE-2022-50630:mm:hugetlb:hugetlb_handle_userfault の UAF を修正します(bsc#1254785)。
    - CVE-2022-50700:wifi:ath10k:バッファのマッピング解除を遅らせます(bsc#1255576)。
    - CVE-2023-53254:cacheinfo:異なるレベルで共有キャッシュを処理するためのshared_cpu_mapを修正します(bsc#1249871)。
    - CVE-2023-53781:smc:tcp_write_timer_handler() の use-after-free を修正します(bsc#1254751)。
    - CVE-2024-56590:Bluetooth:hci_core:hci_acldata_packetの skb 長をチェックしない問題を修正します(bsc#1235038)。
    - CVE-2025-39977:futex:requeue-PI 中の use-after-free を防ぎます(bsc#1252046)。
    - CVE-2025-40019:crypto:essiv - 復号化およびインプレース暗号化に対して ssize をチェックします(bsc#1252678)。
    - CVE-2025-40139:smc:smc_clc_prfx_set() (bsc#1253409) の __sk_dst_get() と dst_dev_rcu() を使用します。
    - CVE-2025-40215:kABI:xfrm:x を削除する際に x->tunnel を削除します(bsc#1254959)。
    - CVE-2025-40220: fuse: fuseblk ワーカーからの同期的なファイル削除におけるライブロックを修正 (bsc#1254520)。
    - CVE-2025-40233:ocfs2:エクステントを移動/デフラグした後、エクステントキャッシュをクリアします(bsc#1254813)。
    - CVE-2025-40258:mptcp:mptcp_schedule_work() での競合状態を修正します(bsc#1254843)。
    - CVE-2025-40277:drm/vmwgfx:コマンドヘッダーサイズを(bsc#1254894)に対して検証します。
    - CVE-2025-40280:tipc:tipc_mon_reinit_self() の use-after-free を修正します(bsc#1254847)。
    - CVE-2025-40331:sctp:TOCTOU の領域外書き込みを防止します(bsc#1254615)。
    - CVE-2025-68732:gpu:host1x:syncpt alloc/free での競合を修正します(bsc#1255688)。

    セキュリティに関係しない以下の問題が修正されました。

    - ACPI/IORT:iort_rmr_alloc_sids() でのメモリ漏洩を修正します(git-fixes)。
    - ACPI:PRM:不要な厳格なハンドラーアドレスチェックを削除します(git-fixes)。
    - ACPI:プロパティ:NULL ハンドルを acpi_attach_data() に渡しません(git-fixes)。
    - ACPI:プロパティ:サブノードのバッファプロパティ抽出を修正します(git-fixes)。
    - KVM:SVM:TSC_AUX仮想化セットアップを修正します(git-fixes)。
    - RDMA/cm:レート制限が CM ID を破壊するタイムアウトエラーメッセージ(git-fixes)。
    - RDMA/カウンター:RDMA カウンターに対するユーザーの名前空間をチェックCAP_NET_RAWチェックします(git-fixes)。
    - RDMA/hns:max_send_sge の修正を修正します(git-fixes)。
    - RDMA/mlx5:アンカー作成のためにユーザー名前空間のCAP_NET_RAWをチェックします(git-fixes)。
    - RDMA/mlx5:devx 作成用のユーザー名前空間のCAP_NET_RAWをチェックします(git-fixes)。
    - RDMA/mlx5:フロー作成のためにユーザー名前空間のCAP_NET_RAWをチェックします(git-fixes)。
    - RDMA/mlx5:USER_ACCESSが設定されていないときのコンパイル警告を修正します(git-fixes)。
    - RDMA/nldev:QP 変更のためにユーザー名前空間のCAP_NET_RAWをチェックします(git-fixes)。
    - RDMA/uverbs:空の rdma_uattrs_has_raw_cap() 宣言を追加します(git-fixes)。
    - RDMA/uverbs:QP 作成のためのユーザー名前空間のCAP_NET_RAWをチェックします(git-fixes)。
    - RDMA/uverbs:RAW QP 作成用のユーザー名前空間のCAP_NET_RAWをチェックします(git-fixes)。
    - RDMA/uverbs:フロー作成のためにユーザー名前空間のCAP_NET_RAWをチェックします(git-fixes)。
    - arch/idle:arch_cpu_idle() 動作を変更します:IRQ を無効にして常に終了します(git-fixes)。
    - cpuidle/poll:cpuidle_state::enter() の呼び出し後に IRQ が無効のままになるようにします(git-fixes)。
    - cpuidle:IRQ 状態検証を移動します(git-fixes)。
    - cpuidle:haltpoll:アイドル状態になる際に割り込みを有効化しません(git-fixes)。
    - dm:__bind で使用されていない場合、テーブル mempool を解放します(git-fixes)。
    - padata:chunk_size 0(bsc#1237563)の場合、呼び出し元のアライメントを尊重します。
    - platform/x86/intel-uncore-freq:plat_info が NULL の場合にモジュールのロードが失敗します(git-fixes)。
    - x86/bugs:indirect_branch_prediction_barrier() での RSB 消去を修正します(git-fixes)。
    - x86/bugs:該当する場合は write_ibpb() で SBPB を使用します(git-fixes)。
    - x86/paravirt:halt paravirt 呼び出しを CONFIG_PARAVIRT の下に移動します(git-fixes)。
    - x86/tdx:__tdx_hypercall() からフラグをドロップします(git-fixes)。
    - x86/tdx:#VEs を引き起こす SEPT 違反を動的に無効にします(git-fixes)。
    - x86/tdx:HLT #VE 処理中に IRQ が有効である場合に警告を発します(git-fixes)。
    - x86/tdx:TDX_MODULE_CALLを拡張し、より多くの TDCALL/SEAMCALL リーフをサポートします(git-fixes)。
    - x86/tdx:__tdx_hypercall_failed() 周辺__noreturnビルド警告を修正します(git-fixes)。
    - x86/tdx:TDX VM に対する arch_safe_halt() 実行を修正します(git-fixes)。
    - x86/tdx:TD メタデータを読み書きするためにラッパーを導入します(git-fixes)。
    - x86/tdx:TDX_HYPERCALL asm を TDX_MODULE_CALL に類似させます(git-fixes)。
    - x86/tdx:TDCALL のマクロを仕様(git-fixes)と一致させます。
    - x86/tdx:構造体を介して TDCALL/SEAMCALL 入出力レジスタを渡します(git-fixes)。
    - x86/tdx:TDX_MODULE_CALL asm を使用して __tdx_hypercall() を再実装します(git-fixes)。
    - x86/tdx:「struct tdx_hypercall_args」を削除します(git-fixes)。
    - x86/tdx:TDX_HCALL_ISSUE_STI を削除します(git-fixes)。
    - x86/tdx:__tdx_module_call() を __tdcall() に名前を変更します(git-fixes)。
    - x86/tdx:tdx_parse_tdinfo() を tdx_setup() に名前を変更します(git-fixes)。
    - x86/tdx:部分的に完了したページ変換ハイパーコールを再試行します(git-fixes)。
    - x86/tdx:SEAMCALL が VMFailInvalid で失敗した場合、出力レジスタの保存をスキップします(git-fixes)。
    - x86/tdx:TDX_HYPERCALL マクロで欠如している RSI をゼロにします(git-fixes)。
    - x86/virt/tdx:TDX_MODULE_CALLに SEAMCALL #UD および #GP を処理させます(git-fixes)。
    - x86/virt/tdx:基本的な SEAMCALL 関数をつなげます(git-fixes)。
    - xfs:runt AG のまばらな inode 制限を修正します(bsc#1254392)。

Tenable は、前述の記述ブロックを SUSE セキュリティアドバイザリから直接抽出しています。

Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。

リモートの SUSE Linux SLES12 ホストには、SUSE-SU-2026:1078-1 のアドバイザリに記載された複数の脆弱性の影響を受けるパッケージがインストールされています。

    SUSE Linux Enterprise 12 SP5 カーネルが更新され、さまざまなセキュリティのバグ修正が行われています。


    次のセキュリティバグを修正しました。

    - CVE-2022-50453: gpiolib: cdev: NULL ポインタ参照を修正 (bsc#1250887)。
    - CVE-2023-53794: cifs: メモリ解放後使用 (Use-After-Free) の問題を回避するため、再接続時のセッション状態チェックを修正 (bsc#1255163)。
    - CVE-2023-53802: wifi: ath9k: htc_hst: コールバック関数がない場合に ath9k_htc_rx_msg() 内で skb を解放 (bsc#1254725)。
    - CVE-2023-53808: wifi: mwifiex: mwifiex_histogram_read() のメモリリークを修正 (bsc#1254723)。
    - CVE-2023-53816: drm/amdkfd: 潜在的な kgd_mem UAF を修正 (bsc#1254958)。
    - CVE-2023-53817: crypto: lib/mpi - mpi_cmp_ui() での NULL ポインターデリファレンスを回避します (bsc#1254992)。
    - CVE-2023-53827: Bluetooth: L2CAP: l2cap_disconnect_{req,rsp} のメモリ解放後使用 (Use-After-Free) を修正 (bsc#1255049)。
    - CVE-2023-54184: scsi: target: iscsit: セッション解放前に cmds を解放 (bsc#1255991)。
    - CVE-2025-21738: ata: libata-sff: 割り当てられたバッファ外に書き込めないことを確認 (bsc#1238917)。
    - CVE-2025-22083: vhost-scsi: vhost_scsi_set_endpoint への複数の呼び出しの処理を修正 (bsc#1241414)。
    - CVE-2025-22125: md/raid1,raid10: IO フラグを無視しないように修正 (bsc#1241596)。
    - CVE-2025-39748: bpf: JSET 後に tnum を改良する際に範囲を考慮しません (bsc#1249587)。
    - CVE-2025-39817: efivarfs: efivarfs_d_compare の slab-out-of-bounds を修正します (bsc#1249998)。
    - CVE-2025-39964: crypto: af_alg - af_alg_sendmsg で同時書き込みを許可しません (bsc#1251966)。
    - CVE-2025-39998: scsi: target: target_core_configfs: バッファオーバーフローを避けるために長さチェックを追加 (bsc#1252073)。
    - CVE-2025-40099: cifs: parse_dfs_referrals: 不正な形式の入力による OOB を防ぎます (bsc#1252911)。
    - CVE-2025-40103: smb: client: cifs_sb_tlink の refcount リークを修正します (bsc#1252924)。
    - CVE-2025-40219: PCI/IOV: SR-IOV を有効化/無効化する際に、PCI 再スキャン/削除操作のロックを追加 (bsc#1254518)。
    - CVE-2025-40220: fuse: fuseblk ワーカーからの同期的なファイル削除におけるライブロックを修正 (bsc#1254520)。
    - CVE-2025-40242: gfs2: gdlm_put_lock で稀に発生する競合状態を修正 (bsc#1255075)。
    - CVE-2025-40342: nvme-fc:port_state および rport state へのアクセス時にロックを使用 (bsc#1255274)。
    - CVE-2025-68223: drm/radeon: is_signaled 内で radeon_fence_process を削除し、デッドロックを回避 (bsc#1255357)。
    - CVE-2025-68234: scsi: imm: 未完了の遅延作業によって引き起こされるメモリ解放後使用 (Use-After-Free) バグを修正 (bsc#1255416)。
    - CVE-2025-68283: libceph: map->max_osd の境界チェックで BUG_ON を置き換えます (bsc#1255379)。
    - CVE-2025-68285: libceph: libceph: have_mon_and_osd_map() における潜在的なメモリ解放後使用 (Use After Free) の問題を修正 (bsc#1255401)。
    - CVE-2025-68287: usb: dwc3: 同時に行われる複数の dwc3_remove_requests() 呼び出しパスの競合状態を修正 (bsc#1255152)。
    - CVE-2025-68295: smb: client: cifs_construct_tcon() のメモリリークを修正 (bsc#1255129)。
    - CVE-2025-68724: crypto: asymmetric_keys - asymmetric_key_generate_id におけるオーバーフローを回避 (bsc#1255550)。
    - CVE-2025-68818: scsi: qla2xxx: 中止パスでロックなしのコマンド完了処理を実行 (bsc#1256675)。
    - CVE-2025-71075: scsi: aic94xx: デバイスの削除パスでメモリ解放後使用 (Use-After-Free) を修正 (bsc#1256629)。
    - CVE-2025-71104: KVM: x86: 定期的な HV タイマーにより長時間の非アクティブ後に発生する VM ハードロックアップを修正します (bsc#1256708)。
    - CVE-2025-71113: crypto: af_alg - sock_kmalloc により割り当てられたメモリをゼロ初期化します (bsc#1256716)。
    - CVE-2025-71116: libceph: 破損した OSD マップに対応できるよう、decode_pool() の耐障害性を向上 (bsc#1256744)。
    - CVE-2025-71131: crypto: seqiv - crypto_aead_encrypt の実行後に req->iv を使用しないよう修正 (bsc#1256742)。
    - CVE-2025-71183: inode 参照をログ出力する際に、常に競合する inode を検出 (bsc#1257631)。
    - CVE-2025-71184: btrfs: inode の evict をトレースする際の root での NULL ポインターデリファレンスを修正します (bsc#1257635)。
    - CVE-2025-71194: btrfs: 無視されたトランザクションタイプに起因する wait_current_trans() のデッドロックを修正します (bsc#1257687)。
    - CVE-2025-71224: wifi: mac80211: ocb: インターフェースが参加していない場合は skip rx_no_sta をスキップ (bsc#1258824)。
    - CVE-2025-71236: scsi: qla2xxx: 関連するメモリを解放する前に sp を検証 (bsc#1258442)。
    - CVE-2026-22991: libceph: free_choose_arg_map() を、部分的な割り当てに対しても安全に動作するよう改善 (bsc#1257220)。
    - CVE-2026-22998: nvme-tcp: nvmet_tcp_build_pdu_iovec での NULL ポインターデリファレンスを修正します (bsc#1257209)。
    - CVE-2026-23004: dst: rt6_uncached_list_del() と rt_del_uncached_list() における競合を修正します (bsc#1257231)。
    - CVE-2026-23054: net: hv_netvsc: RX インダイレクションテーブルなしでの RSS ハッシュキープログラミングを拒否 (bsc#1257732)。
    - CVE-2026-23060: crypto: authencesn - ESP/ESN 仕様に合わせて、短すぎる AAD (assoclen<8) を拒否します (bsc#1257735)。
    - CVE-2026-23064: net/sched: act_ife: NULL ポインターデリファレンスの可能性を回避します (bsc#1257765)。
    - CVE-2026-23069: vsock/virtio: virtio_transport_get_credit() における潜在的なアンダーフローを修正します (bsc#1257755)。
    - CVE-2026-23074: net/sched: teql をルート qdisc としてのみ使用できるように強制します (bsc#1257749)。
    - CVE-2026-23083: fou: FOU_ATTR_IPPROTO に対して 0 を許可しません (bsc#1257745)。
    - CVE-2026-23084: be2net: be_cmd_get_mac_from_list() における NULL ポインターデリファレンスを修正します (bsc#1257830)。
    - CVE-2026-23085: irqchip/gic-v3-its: メモリアドレスの切り詰めを回避します (bsc#1257758)。
    - CVE-2026-23086: vsock/virtio: TX クレジットをローカルバッファサイズに制限します (bsc#1257757)。
    - CVE-2026-23089: ALSA: usb-audio: snd_usb_mixer_free() におけるメモリ解放後使用 (Use-After-Free) を修正します (bsc#1257790)。
    - CVE-2026-23095: gue: 内部 IP プロトコルが 0 の場合の skb メモリリークを修正します (bsc#1257808)。
    - CVE-2026-23099: bonding: BOND_MODE_8023AD をイーサネット デバイスに限定します (bsc#1257816)。
    - CVE-2026-23105: net/sched: qfq: qfq_rm_from_ag でクラスがアクティブかどうかを cl_is_active で判定します (bsc#1257775)。
    - CVE-2026-23112: nvmet-tcp: nvmet_tcp_build_pdu_iovec に境界チェックを追加します (bsc#1258184)。
    - CVE-2026-23125: sctp: SCTP_CMD_PEER_INIT の直後に SCTP_CMD_ASSOC_SHKEY を移動します (bsc#1258293)。
    - CVE-2026-23141: btrfs: send: range_is_hole_in_parent() でインラインエクステントをチェックします (bsc#1258377)。
    - CVE-2026-23191: ALSA: aloop: PCM トリガーにおける競合アクセスを修正します (bsc#1258395)。
    - CVE-2026-23198: KVM: irqfd の割り当て解除時に irqfd ルーティングタイプを破壊しません (bsc#1258321)。
    - CVE-2026-23204: net/sched: cls_u32: skb_header_pointer_careful() を使用します (bsc#1258340)。
    - CVE-2026-23208: ALSA: usb-audio: フレーム数の過剰を防ぎます (bsc#1258468)。
    - CVE-2026-23209: macvlan: macvlan_common_newlink() におけるエラー回復処理を修正します (bsc#1258518)。
    - CVE-2026-23268: apparmor: 権限のないローカルユーザーが特権ポリシー管理を実行できる問題を修正 (bsc#1258850)。
    - CVE-2026-23269: apparmor: unpack_pdb において DFA の開始状態が範囲内にあることを検証 (bsc#1259857)。


Tenable は、前述の記述ブロックを SUSE セキュリティアドバイザリから直接抽出しています。

Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。

AlmaLinux 9.2 ホストには、TuxCare ALMALINUX9.2:CLSA-2026:1767864313アドバイザリに記載されている複数の脆弱性の影響を受けるパッケージがインストールされています。

  - Linux カーネルでは、以下の脆弱性が解決されています: firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails When scpi probe fails, at any point, we need to ensure that the scpi_info is not set and will remain NULL until the probe succeeds. If it is not taken care, then it could result use-after-free as the value is exported via get_scpi_ops() and could refer to a memory allocated via devm_kzalloc() but freed when the probe fails. (CVE-2022-50087)

  - Linux カーネルでは、以下の脆弱性が解決されています: wifi: rtlwifi: Fix global-out-of-bounds bug in _rtl8812ae_phy_set_txpower_limit() There is a global-out-of-bounds reported by KASAN: BUG:
    KASAN: global-out-of-bounds in _rtl8812ae_eq_n_byte.part.0+0x3d/0x84 [rtl8821ae] Read of size 1 at addr ffffffffa0773c43 by task NetworkManager/411 CPU: 6 PID: 411 Comm: NetworkManager Tainted: G D 6.1.0-rc8+ #144 e15588508517267d37 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), Call Trace: <TASK> ...
    kasan_report+0xbb/0x1c0 _rtl8812ae_eq_n_byte.part.0+0x3d/0x84 [rtl8821ae] rtl8821ae_phy_bb_config.cold+0x346/0x641 [rtl8821ae] rtl8821ae_hw_init+0x1f5e/0x79b0 [rtl8821ae] ...
    </TASK> The root cause of the problem is that the comparison order of prate_section in
    _rtl8812ae_phy_set_txpower_limit() is wrong. The _rtl8812ae_eq_n_byte() is used to compare the first n bytes of the two strings from tail to head, which causes the problem. In the
    _rtl8812ae_phy_set_txpower_limit(), it was originally intended to meet this requirement by carefully designing the comparison order. For example, pregulation and pbandwidth are compared in order of length from small to large, first is 3 and last is 4. However, the comparison order of prate_section dose not obey such order requirement, therefore when prate_section is HT, when comparing from tail to head, it will lead to access out of bounds in _rtl8812ae_eq_n_byte(). As mentioned above, the
    _rtl8812ae_eq_n_byte() has the same function as strcmp(), so just strcmp() is enough. Fix it by removing
    _rtl8812ae_eq_n_byte() and use strcmp() barely. Although it can be fixed by adjusting the comparison order of prate_section, this may cause the value of rate_section to not be from 0 to 5. In addition, commit 21e4b0726dc6 not only moved driver from staging to regular tree, but also added setting txpower limit function during the driver config phase, so the problem was introduced by this commit. (CVE-2022-50279)

  - Linux カーネルでは、以下の脆弱性が解決されています: wifi: ath11k: fix monitor mode bringup crash When the interface is brought up in monitor mode, it leads to NULL pointer dereference crash. This crash happens when the packet type is extracted for a SKB. This extraction which is present in the received msdu delivery path,is not needed for the monitor ring packets since they are all RAW packets.
    Hence appending the flags with RX_FLAG_ONLY_MONITOR to skip that extraction. Observed calltrace: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000064 Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004 CM = 0, WnR = 0 user pgtable:
    4k pages, 48-bit VAs, pgdp=0000000048517000 [0000000000000064] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP Modules linked in: ath11k_pci ath11k qmi_helpers CPU: 2 PID: 1781 Comm: napi/-271 Not tainted 6.1.0-rc5-wt-ath-656295-gef907406320c-dirty #6 Hardware name:
    Qualcomm Technologies, Inc. IPQ8074/AP-HK10-C2 (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : ath11k_hw_qcn9074_rx_desc_get_decap_type+0x34/0x60 [ath11k] lr :
    ath11k_hw_qcn9074_rx_desc_get_decap_type+0x5c/0x60 [ath11k] sp : ffff80000ef5bb10 x29: ffff80000ef5bb10 x28: 0000000000000000 x27: ffff000007baafa0 x26: ffff000014a91ed0 x25: 0000000000000000 x24:
    0000000000000000 x23: ffff800002b77378 x22: ffff000014a91ec0 x21: ffff000006c8d600 x20: 0000000000000000 x19: ffff800002b77740 x18: 0000000000000006 x17: 736564203634343a x16: 656e694c20657079 x15:
    0000000000000143 x14: 00000000ffffffea x13: ffff80000ef5b8b8 x12: ffff80000ef5b8c8 x11: ffff80000a591d30 x10: ffff80000a579d40 x9 : c0000000ffffefff x8 : 0000000000000003 x7 : 0000000000017fe8 x6 :
    ffff80000a579ce8 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 x2 : 3a35ec12ed7f8900 x1 : 0000000000000000 x0 : 0000000000000052 Call trace: ath11k_hw_qcn9074_rx_desc_get_decap_type+0x34/0x60 [ath11k] ath11k_dp_rx_deliver_msdu.isra.42+0xa4/0x3d0 [ath11k] ath11k_dp_rx_mon_deliver.isra.43+0x2f8/0x458 [ath11k] ath11k_dp_rx_process_mon_rings+0x310/0x4c0 [ath11k] ath11k_dp_service_srng+0x234/0x338 [ath11k] ath11k_pcic_ext_grp_napi_poll+0x30/0xb8 [ath11k]
    __napi_poll+0x5c/0x190 napi_threaded_poll+0xf0/0x118 kthread+0xf4/0x110 ret_from_fork+0x10/0x20 Tested-on:
    QCN9074 hw1.0 PCI WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1 (CVE-2022-50627)

  - Linux カーネルでは、以下の脆弱性が解決されています: mm: hugetlb: fix UAF in hugetlb_handle_userfault The vma_lock and hugetlb_fault_mutex are dropped before handling userfault and reacquire them again after handle_userfault(), but reacquire the vma_lock could lead to UAF[1,2] due to the following race, hugetlb_fault hugetlb_no_page /*unlock vma_lock */ hugetlb_handle_userfault handle_userfault /* unlock mm->mmap_lock*/ vm_mmap_pgoff do_mmap mmap_region munmap_vma_range /* clean old vma */ /* lock vma_lock again <--- UAF */ /* unlock vma_lock */ Since the vma_lock will unlock immediately after hugetlb_handle_userfault(), let's drop the unneeded lock and unlock in hugetlb_handle_userfault() to fix the issue. [1] https://lore.kernel.org/linux-mm/000000000000d5e00a05e834962e@google.com/ [2] https://lore.kernel.org/linux-mm/20220921014457.1668-1-liuzixian4@huawei.com/ (CVE-2022-50630)

  - Linux カーネルでは、以下の脆弱性が解決されています: PCI: Fix pci_device_is_present() for VFs by checking PF pci_device_is_present() previously didn't work for VFs because it reads the Vendor and Device ID, which are 0xffff for VFs, which looks like they aren't present. Check the PF instead. Wei Gong reported that if virtio I/O is in progress when the driver is unbound or 0 is written to /sys/.../sriov_numvfs, the virtio I/O operation hangs, which may result in output like this: task:bash state:D stack: 0 pid: 1773 ppid: 1241 flags:0x00004002 Call Trace: schedule+0x4f/0xc0 blk_mq_freeze_queue_wait+0x69/0xa0 blk_mq_freeze_queue+0x1b/0x20 blk_cleanup_queue+0x3d/0xd0 virtblk_remove+0x3c/0xb0 [virtio_blk] virtio_dev_remove+0x4b/0x80 ... device_unregister+0x1b/0x60 unregister_virtio_device+0x18/0x30 virtio_pci_remove+0x41/0x80 pci_device_remove+0x3e/0xb0 This happened because pci_device_is_present(VF) returned false in virtio_pci_remove(), so it called virtio_break_device(). The broken vq meant that vring_interrupt() skipped the vq.callback() that would have completed the virtio I/O operation via virtblk_done(). [bhelgaas: commit log, simplify to always use pci_physfn(), add stable tag] (CVE-2022-50636)

Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。

Linux/Unix ホストには、ベンダーが提供するパッチが利用できない脆弱性の影響を受ける複数のパッケージがインストールされています。

  - drm/amdkfd潜在的な kgd_mem UAFs を修正します kfd_process_device_translate_handle によって返される kgd_mem ポインターは、p->mutex が保持される間だけ有効であることが保証されています。mutex がロック解除されるとすぐに、別のスレッドが BO を解放できます。CVE-2023-53816

Nessus は、ベンダーによって報告されたパッケージの存在に依存していることに注意してください。

The remote SUSE Linux SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:1078-1 advisory.

    The SUSE Linux Enterprise 12 SP5 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2022-50453: gpiolib: cdev: fix NULL-pointer dereferences (bsc#1250887).
    - CVE-2023-53794: cifs: fix session state check in reconnect to avoid use-after-free issue (bsc#1255163).
    - CVE-2023-53802: wifi: ath9k: htc_hst: free skb in ath9k_htc_rx_msg() if there is no callback function     (bsc#1254725).
    - CVE-2023-53808: wifi: mwifiex: fix memory leak in mwifiex_histogram_read() (bsc#1254723).
    - CVE-2023-53816: drm/amdkfd: fix potential kgd_mem UAFs (bsc#1254958).
    - CVE-2023-53817: crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui() (bsc#1254992).
    - CVE-2023-53827: Bluetooth: L2CAP: Fix use-after-free in l2cap_disconnect_{req,rsp} (bsc#1255049).
    - CVE-2023-54184: scsi: target: iscsit: Free cmds before session free (bsc#1255991).
    - CVE-2025-21738: ata: libata-sff: Ensure that we cannot write outside the allocated buffer (bsc#1238917).
    - CVE-2025-22083: vhost-scsi: Fix handling of multiple calls to vhost_scsi_set_endpoint (bsc#1241414).
    - CVE-2025-22125: md/raid1,raid10: do not ignore IO flags (bsc#1241596).
    - CVE-2025-39748: bpf: Forget ranges when refining tnum after JSET (bsc#1249587).
    - CVE-2025-39817: efivarfs: Fix slab-out-of-bounds in efivarfs_d_compare (bsc#1249998).
    - CVE-2025-39964: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (bsc#1251966).
    - CVE-2025-39998: scsi: target: target_core_configfs: Add length check to avoid buffer overflow     (bsc#1252073).
    - CVE-2025-40099: cifs: parse_dfs_referrals: prevent oob on malformed input (bsc#1252911).
    - CVE-2025-40103: smb: client: Fix refcount leak for cifs_sb_tlink (bsc#1252924).
    - CVE-2025-40219: PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV (bsc#1254518).
    - CVE-2025-40220: fuse: fix livelock in synchronous file put from fuseblk workers (bsc#1254520).
    - CVE-2025-40242: gfs2: Fix unlikely race in gdlm_put_lock (bsc#1255075).
    - CVE-2025-40342: nvme-fc: use lock accessing port_state and rport state (bsc#1255274).
    - CVE-2025-68223: drm/radeon: delete radeon_fence_process in is_signaled, no deadlock (bsc#1255357).
    - CVE-2025-68234: scsi: imm: Fix use-after-free bug caused by unfinished delayed work (bsc#1255416).
    - CVE-2025-68283: libceph: replace BUG_ON with bounds check for map->max_osd (bsc#1255379).
    - CVE-2025-68285: libceph: fix potential use-after-free in have_mon_and_osd_map() (bsc#1255401).
    - CVE-2025-68287: usb: dwc3: Fix race condition between concurrent dwc3_remove_requests() call paths     (bsc#1255152).
    - CVE-2025-68295: smb: client: fix memory leak in cifs_construct_tcon() (bsc#1255129).
    - CVE-2025-68724: crypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id (bsc#1255550).
    - CVE-2025-68818: scsi: qla2xxx: Perform lockless command completion in abort path (bsc#1256675).
    - CVE-2025-71075: scsi: aic94xx: fix use-after-free in device removal path (bsc#1256629).
    - CVE-2025-71104: KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer     (bsc#1256708).
    - CVE-2025-71113: crypto: af_alg - zero initialize memory allocated via sock_kmalloc (bsc#1256716).
    - CVE-2025-71116: libceph: make decode_pool() more resilient against corrupted osdmaps (bsc#1256744).
    - CVE-2025-71131: crypto: seqiv - Do not use req->iv after crypto_aead_encrypt (bsc#1256742).
    - CVE-2025-71183: btrfs: always detect conflicting inodes when logging inode refs (bsc#1257631).
    - CVE-2025-71184: btrfs: fix NULL dereference on root when tracing inode eviction (bsc#1257635).
    - CVE-2025-71194: btrfs: fix deadlock in wait_current_trans() due to ignored transaction type     (bsc#1257687).
    - CVE-2025-71224: wifi: mac80211: ocb: skip rx_no_sta when interface is not joined (bsc#1258824).
    - CVE-2025-71236: scsi: qla2xxx: Validate sp before freeing associated memory (bsc#1258442).
    - CVE-2026-22991: libceph: make free_choose_arg_map() resilient to partial allocation (bsc#1257220).
    - CVE-2026-22998: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (bsc#1257209).
    - CVE-2026-23004: dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() (bsc#1257231).
    - CVE-2026-23054: net: hv_netvsc: reject RSS hash key programming without RX indirection table     (bsc#1257732).
    - CVE-2026-23060: crypto: authencesn - reject too-short AAD (assoclen<8) to match ESP/ESN spec     (bsc#1257735).
    - CVE-2026-23064: net/sched: act_ife: avoid possible NULL deref (bsc#1257765).
    - CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).
    - CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc (bsc#1257749).
    - CVE-2026-23083: fou: Don't allow 0 for FOU_ATTR_IPPROTO (bsc#1257745).
    - CVE-2026-23084: be2net: Fix NULL pointer dereference in be_cmd_get_mac_from_list (bsc#1257830).
    - CVE-2026-23085: irqchip/gic-v3-its: Avoid truncating memory addresses (bsc#1257758).
    - CVE-2026-23086: vsock/virtio: cap TX credit to local buffer size (bsc#1257757).
    - CVE-2026-23089: ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() (bsc#1257790).
    - CVE-2026-23095: gue: Fix skb memleak with inner IP protocol 0 (bsc#1257808).
    - CVE-2026-23099: bonding: limit BOND_MODE_8023AD to Ethernet devices (bsc#1257816).
    - CVE-2026-23105: net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag     (bsc#1257775).
    - CVE-2026-23112: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (bsc#1258184).
    - CVE-2026-23125: sctp: move SCTP_CMD_ASSOC_SHKEY right after SCTP_CMD_PEER_INIT (bsc#1258293).
    - CVE-2026-23141: btrfs: send: check for inline extents in range_is_hole_in_parent() (bsc#1258377).
    - CVE-2026-23191: ALSA: aloop: Fix racy access at PCM trigger (bsc#1258395).
    - CVE-2026-23198: KVM: Don't clobber irqfd routing type when deassigning irqfd (bsc#1258321).
    - CVE-2026-23204: net/sched: cls_u32: use skb_header_pointer_careful() (bsc#1258340).
    - CVE-2026-23208: ALSA: usb-audio: Prevent excessive number of frames (bsc#1258468).
    - CVE-2026-23209: macvlan: fix error recovery in macvlan_common_newlink() (bsc#1258518).
    - CVE-2026-23268: apparmor: fix unprivileged local user can do privileged policy management (bsc#1258850).
    - CVE-2026-23269: apparmor: validate DFA start states are in bounds in unpack_pdb (bsc#1259857).


Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1767864313 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: firmware: arm_scpi: Ensure scpi_info     is not assigned if the probe fails When scpi probe fails, at any point, we need to ensure that the     scpi_info is not set and will remain NULL until the probe succeeds. If it is not taken care, then it could     result use-after-free as the value is exported via get_scpi_ops() and could refer to a memory allocated     via devm_kzalloc() but freed when the probe fails. (CVE-2022-50087)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: rtlwifi: Fix global-out-of-     bounds bug in _rtl8812ae_phy_set_txpower_limit() There is a global-out-of-bounds reported by KASAN: BUG:
    KASAN: global-out-of-bounds in _rtl8812ae_eq_n_byte.part.0+0x3d/0x84 [rtl8821ae] Read of size 1 at addr     ffffffffa0773c43 by task NetworkManager/411 CPU: 6 PID: 411 Comm: NetworkManager Tainted: G D 6.1.0-rc8+     #144 e15588508517267d37 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), Call Trace: <TASK> ...
    kasan_report+0xbb/0x1c0 _rtl8812ae_eq_n_byte.part.0+0x3d/0x84 [rtl8821ae]     rtl8821ae_phy_bb_config.cold+0x346/0x641 [rtl8821ae] rtl8821ae_hw_init+0x1f5e/0x79b0 [rtl8821ae] ...
    </TASK> The root cause of the problem is that the comparison order of prate_section in
    _rtl8812ae_phy_set_txpower_limit() is wrong. The _rtl8812ae_eq_n_byte() is used to compare the first n     bytes of the two strings from tail to head, which causes the problem. In the
    _rtl8812ae_phy_set_txpower_limit(), it was originally intended to meet this requirement by carefully     designing the comparison order. For example, pregulation and pbandwidth are compared in order of     length from small to large, first is 3 and last is 4. However, the comparison order of prate_section     dose not obey such order requirement, therefore when prate_section is HT, when comparing from tail to     head, it will lead to access out of bounds in _rtl8812ae_eq_n_byte(). As mentioned above, the
    _rtl8812ae_eq_n_byte() has the same function as strcmp(), so just strcmp() is enough. Fix it by removing
    _rtl8812ae_eq_n_byte() and use strcmp() barely. Although it can be fixed by adjusting the comparison order     of prate_section, this may cause the value of rate_section to not be from 0 to 5. In addition, commit     21e4b0726dc6 not only moved driver from staging to regular tree, but also added setting txpower limit     function during the driver config phase, so the problem was introduced by this commit. (CVE-2022-50279)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix monitor mode bringup     crash When the interface is brought up in monitor mode, it leads to NULL pointer dereference crash. This     crash happens when the packet type is extracted for a SKB. This extraction which is present in the     received msdu delivery path,is not needed for the monitor ring packets since they are all RAW packets.
    Hence appending the flags with RX_FLAG_ONLY_MONITOR to skip that extraction. Observed calltrace: Unable     to handle kernel NULL pointer dereference at virtual address 0000000000000064 Mem abort info: ESR =     0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC =     0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004 CM = 0, WnR = 0 user pgtable:
    4k pages, 48-bit VAs, pgdp=0000000048517000 [0000000000000064] pgd=0000000000000000, p4d=0000000000000000     Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP Modules linked in: ath11k_pci ath11k qmi_helpers     CPU: 2 PID: 1781 Comm: napi/-271 Not tainted 6.1.0-rc5-wt-ath-656295-gef907406320c-dirty #6 Hardware name:
    Qualcomm Technologies, Inc. IPQ8074/AP-HK10-C2 (DT) pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS     BTYPE=--) pc : ath11k_hw_qcn9074_rx_desc_get_decap_type+0x34/0x60 [ath11k] lr :
    ath11k_hw_qcn9074_rx_desc_get_decap_type+0x5c/0x60 [ath11k] sp : ffff80000ef5bb10 x29: ffff80000ef5bb10     x28: 0000000000000000 x27: ffff000007baafa0 x26: ffff000014a91ed0 x25: 0000000000000000 x24:
    0000000000000000 x23: ffff800002b77378 x22: ffff000014a91ec0 x21: ffff000006c8d600 x20: 0000000000000000     x19: ffff800002b77740 x18: 0000000000000006 x17: 736564203634343a x16: 656e694c20657079 x15:
    0000000000000143 x14: 00000000ffffffea x13: ffff80000ef5b8b8 x12: ffff80000ef5b8c8 x11: ffff80000a591d30     x10: ffff80000a579d40 x9 : c0000000ffffefff x8 : 0000000000000003 x7 : 0000000000017fe8 x6 :
    ffff80000a579ce8 x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 x2 : 3a35ec12ed7f8900     x1 : 0000000000000000 x0 : 0000000000000052 Call trace: ath11k_hw_qcn9074_rx_desc_get_decap_type+0x34/0x60     [ath11k] ath11k_dp_rx_deliver_msdu.isra.42+0xa4/0x3d0 [ath11k]     ath11k_dp_rx_mon_deliver.isra.43+0x2f8/0x458 [ath11k] ath11k_dp_rx_process_mon_rings+0x310/0x4c0 [ath11k]     ath11k_dp_service_srng+0x234/0x338 [ath11k] ath11k_pcic_ext_grp_napi_poll+0x30/0xb8 [ath11k]
    __napi_poll+0x5c/0x190 napi_threaded_poll+0xf0/0x118 kthread+0xf4/0x110 ret_from_fork+0x10/0x20 Tested-on:
    QCN9074 hw1.0 PCI WLAN.HK.2.7.0.1-01744-QCAHKSWPL_SILICONZ-1 (CVE-2022-50627)

  - In the Linux kernel, the following vulnerability has been resolved: mm: hugetlb: fix UAF in     hugetlb_handle_userfault The vma_lock and hugetlb_fault_mutex are dropped before handling userfault and     reacquire them again after handle_userfault(), but reacquire the vma_lock could lead to UAF[1,2] due to     the following race, hugetlb_fault hugetlb_no_page /*unlock vma_lock */ hugetlb_handle_userfault     handle_userfault /* unlock mm->mmap_lock*/ vm_mmap_pgoff do_mmap mmap_region munmap_vma_range /* clean old     vma */ /* lock vma_lock again <--- UAF */ /* unlock vma_lock */ Since the vma_lock will unlock immediately     after hugetlb_handle_userfault(), let's drop the unneeded lock and unlock in hugetlb_handle_userfault() to     fix the issue. [1] https://lore.kernel.org/linux-mm/000000000000d5e00a05e834962e@google.com/ [2]     https://lore.kernel.org/linux-mm/20220921014457.1668-1-liuzixian4@huawei.com/ (CVE-2022-50630)

  - In the Linux kernel, the following vulnerability has been resolved: PCI: Fix pci_device_is_present() for     VFs by checking PF pci_device_is_present() previously didn't work for VFs because it reads the Vendor and     Device ID, which are 0xffff for VFs, which looks like they aren't present. Check the PF instead. Wei Gong     reported that if virtio I/O is in progress when the driver is unbound or 0 is written to     /sys/.../sriov_numvfs, the virtio I/O operation hangs, which may result in output like this: task:bash     state:D stack: 0 pid: 1773 ppid: 1241 flags:0x00004002 Call Trace: schedule+0x4f/0xc0     blk_mq_freeze_queue_wait+0x69/0xa0 blk_mq_freeze_queue+0x1b/0x20 blk_cleanup_queue+0x3d/0xd0     virtblk_remove+0x3c/0xb0 [virtio_blk] virtio_dev_remove+0x4b/0x80 ... device_unregister+0x1b/0x60     unregister_virtio_device+0x18/0x30 virtio_pci_remove+0x41/0x80 pci_device_remove+0x3e/0xb0 This happened     because pci_device_is_present(VF) returned false in virtio_pci_remove(), so it called     virtio_break_device(). The broken vq meant that vring_interrupt() skipped the vq.callback() that would     have completed the virtio I/O operation via virtblk_done(). [bhelgaas: commit log, simplify to always use     pci_physfn(), add stable tag] (CVE-2022-50636)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - drm/amdkfd: fix potential kgd_mem UAFs kgd_mem pointers returned by kfd_process_device_translate_handle     are only guaranteed to be valid while p->mutex is held. As soon as the mutex is unlocked, another thread     can free the BO. (CVE-2023-53816)

Note that Nessus relies on the presence of the package as reported by the vendor.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-142478 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    drm/amdkfd: fix potential kgd_mem UAFs

    kgd_mem pointers returned by kfd_process_device_translate_handle are     only guaranteed to be valid while p->mutex is held. As soon as the mutex     is unlocked, another thread can free the BO.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:0317-1 advisory.

    The SUSE Linux Enterprise 15 SP5 kernel was updated to fix various security issues

    The following security issues were fixed:

    - CVE-2022-50630: mm: hugetlb: fix UAF in hugetlb_handle_userfault (bsc#1254785).
    - CVE-2022-50700: wifi: ath10k: Delay the unmapping of the buffer (bsc#1255576).
    - CVE-2023-53254: cacheinfo: Fix shared_cpu_map to handle shared caches at different levels (bsc#1249871).
    - CVE-2023-53781: smc: Fix use-after-free in tcp_write_timer_handler() (bsc#1254751).
    - CVE-2024-56590: Bluetooth: hci_core: Fix not checking skb length on hci_acldata_packet (bsc#1235038).
    - CVE-2025-39977: futex: Prevent use-after-free during requeue-PI (bsc#1252046).
    - CVE-2025-40019: crypto: essiv - Check ssize for decryption and in-place encryption (bsc#1252678).
    - CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).
    - CVE-2025-40215: kABI: xfrm: delete x->tunnel as we delete x (bsc#1254959).
    - CVE-2025-40220: fuse: fix livelock in synchronous file put from fuseblk workers (bsc#1254520).
    - CVE-2025-40233: ocfs2: clear extent cache after moving/defragmenting extents (bsc#1254813).
    - CVE-2025-40258: mptcp: fix race condition in mptcp_schedule_work() (bsc#1254843).
    - CVE-2025-40277: drm/vmwgfx: Validate command header size against (bsc#1254894).
    - CVE-2025-40280: tipc: Fix use-after-free in tipc_mon_reinit_self() (bsc#1254847).
    - CVE-2025-40331: sctp: Prevent TOCTOU out-of-bounds write (bsc#1254615).
    - CVE-2025-68732: gpu: host1x: Fix race in syncpt alloc/free (bsc#1255688).

    The following non security issues were fixed:

    - ACPI/IORT: Fix memory leak in iort_rmr_alloc_sids() (git-fixes).
    - ACPI: PRM: Remove unnecessary strict handler address checks (git-fixes).
    - ACPI: property: Do not pass NULL handles to acpi_attach_data() (git-fixes).
    - ACPI: property: Fix buffer properties extraction for subnodes (git-fixes).
    - KVM: SVM: Fix TSC_AUX virtualization setup (git-fixes).
    - RDMA/cm: Rate limit destroy CM ID timeout error message (git-fixes).
    - RDMA/counter: Check CAP_NET_RAW check in user namespace for RDMA counters (git-fixes).
    - RDMA/hns: Fix the modification of max_send_sge (git-fixes).
    - RDMA/mlx5: Check CAP_NET_RAW in user namespace for anchor create (git-fixes).
    - RDMA/mlx5: Check CAP_NET_RAW in user namespace for devx create (git-fixes).
    - RDMA/mlx5: Check CAP_NET_RAW in user namespace for flow create (git-fixes).
    - RDMA/mlx5: Fix compilation warning when USER_ACCESS isn't set (git-fixes).
    - RDMA/nldev: Check CAP_NET_RAW in user namespace for QP modify (git-fixes).
    - RDMA/uverbs: Add empty rdma_uattrs_has_raw_cap() declaration (git-fixes).
    - RDMA/uverbs: Check CAP_NET_RAW in user namespace for QP create (git-fixes).
    - RDMA/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create (git-fixes).
    - RDMA/uverbs: Check CAP_NET_RAW in user namespace for flow create (git-fixes).
    - arch/idle: Change arch_cpu_idle() behavior: always exit with IRQs disabled (git-fixes).
    - cpuidle/poll: Ensure IRQs stay disabled after cpuidle_state::enter() calls (git-fixes).
    - cpuidle: Move IRQ state validation (git-fixes).
    - cpuidle: haltpoll: Do not enable interrupts when entering idle (git-fixes).
    - dm: free table mempools if not used in __bind (git-fixes).
    - padata: Honor the caller's alignment in case of chunk_size 0 (bsc#1237563).
    - platform/x86/intel-uncore-freq: Fail module load when plat_info is NULL (git-fixes).
    - x86/bugs: Fix RSB clearing in indirect_branch_prediction_barrier() (git-fixes).
    - x86/bugs: Use SBPB in write_ibpb() if applicable (git-fixes).
    - x86/paravirt: Move halt paravirt calls under CONFIG_PARAVIRT (git-fixes).
    - x86/tdx: Drop flags from __tdx_hypercall() (git-fixes).
    - x86/tdx: Dynamically disable SEPT violations from causing #VEs (git-fixes).
    - x86/tdx: Emit warning if IRQs are enabled during HLT #VE handling (git-fixes).
    - x86/tdx: Extend TDX_MODULE_CALL to support more TDCALL/SEAMCALL leafs (git-fixes).
    - x86/tdx: Fix __noreturn build warning around __tdx_hypercall_failed() (git-fixes).
    - x86/tdx: Fix arch_safe_halt() execution for TDX VMs (git-fixes).
    - x86/tdx: Introduce wrappers to read and write TD metadata (git-fixes).
    - x86/tdx: Make TDX_HYPERCALL asm similar to TDX_MODULE_CALL (git-fixes).
    - x86/tdx: Make macros of TDCALLs consistent with the spec (git-fixes).
    - x86/tdx: Pass TDCALL/SEAMCALL input/output registers via a structure (git-fixes).
    - x86/tdx: Reimplement __tdx_hypercall() using TDX_MODULE_CALL asm (git-fixes).
    - x86/tdx: Remove 'struct tdx_hypercall_args' (git-fixes).
    - x86/tdx: Remove TDX_HCALL_ISSUE_STI (git-fixes).
    - x86/tdx: Rename __tdx_module_call() to __tdcall() (git-fixes).
    - x86/tdx: Rename tdx_parse_tdinfo() to tdx_setup() (git-fixes).
    - x86/tdx: Retry partially-completed page conversion hypercalls (git-fixes).
    - x86/tdx: Skip saving output regs when SEAMCALL fails with VMFailInvalid (git-fixes).
    - x86/tdx: Zero out the missing RSI in TDX_HYPERCALL macro (git-fixes).
    - x86/virt/tdx: Make TDX_MODULE_CALL handle SEAMCALL #UD and #GP (git-fixes).
    - x86/virt/tdx: Wire up basic SEAMCALL functions (git-fixes).
    - xfs: fix sparse inode limits on runt AG (bsc#1254392).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
360579	AlmaLinux 9.2 [TuxCare] 安全性更新：bpftool / kernel / kernel-abi-stablelists / kernel-core / etc多個弱點（ALMALINUX9.2：CLSA-2026：1767864313）	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/1	high
277905	Linux Distros 未修補的弱點：CVE-2023-53816	Nessus	Misc.	2025/12/9	2026/11/5	high
360579	AlmaLinux 9.2 [TuxCare] 安全更新：bpftool / kernel / kernel-abi-stablelists / kernel-core / 等多个漏洞（ALMALINUX9.2：CLSA-2026：1767864313）	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/1	high
277905	Linux Distros 未修补的漏洞：CVE-2023-53816	Nessus	Misc.	2025/12/9	2026/11/5	high
297191	SUSE SLES15: Linux カーネルのセキュリティ更新 (SUSE-SU-2026:0317-1)	Nessus	SuSE Local Security Checks	2026/1/30	2026/9/29	high
303947	SUSE SLES12: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2026:1078-1)	Nessus	SuSE Local Security Checks	2026/3/27	2026/9/18	critical
360579	AlmaLinux 9.2 [TuxCare] セキュリティ更新プログラム:bpftool/kernel/kernel-abi-stablelists/kernel-core/etcの複数の脆弱性(ALMALINUX9.2:CLSA-2026:1767864313)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/1	high
277905	Linux Distros のパッチ未適用の脆弱性: CVE-2023-53816	Nessus	Misc.	2025/12/9	2026/11/5	high
303947	SUSE SLES12: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2026:1078-1)	Nessus	SuSE Local Security Checks	2026/3/27	2026/9/18	critical
360579	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1767864313)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/1	high
277905	Linux Distros Unpatched Vulnerability : CVE-2023-53816	Nessus	Misc.	2025/12/9	2026/11/5	high
370862	Unity Linux 20.1020e / 20.1050e / 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-142478)	Nessus	Unity Linux Local Security Checks	2026/10/22	2026/10/22	high
297191	SUSE SLES15 : Security update for the Linux Kernel (SUSE-SU-2026:0317-1)	Nessus	SuSE Local Security Checks	2026/1/30	2026/9/29	high

检测

插件搜索

high

high

high

high

high

critical

high

high

critical

high

high

high

high