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

  - 已解決 Linux 核心中的下列弱點：ethernet: hisilicon: hns:
    hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() The if statement: if (port >= DSAF_GE_NUM) return; limits the value of port less than DSAF_GE_NUM (i.e., 8). However, if the value of port is 6 or 7, an array overflow could occur: port_rst_off = dsaf_dev->mac_cb[port]->port_rst_off;
    because the length of dsaf_dev->mac_cb is DSAF_MAX_PORT_NUM (i.e., 6). To fix this possible array overflow, we first check port and if it is greater than or equal to DSAF_MAX_PORT_NUM, the function returns. (CVE-2021-47548)

  - 已解決 Linux 核心中的下列弱點：SUNRPC: Fix a suspicious RCU usage warning I received the following warning while running cthon against an ontap server running pNFS: [57.202521] ============================= [ 57.202522] WARNING: suspicious RCU usage [ 57.202523] 6.7.0-rc3-g2cc14f52aeb7 #41492 Not tainted [ 57.202525] ----------------------------- [ 57.202525] net/sunrpc/xprtmultipath.c:349 RCU-list traversed in non-reader section!! [ 57.202527] other info that might help us debug this: [ 57.202528] rcu_scheduler_active = 2, debug_locks = 1 [ 57.202529] no locks held by test5/3567. [ 57.202530] stack backtrace: [ 57.202532] CPU: 0 PID: 3567 Comm: test5 Not tainted 6.7.0-rc3-g2cc14f52aeb7 #41492 5b09971b4965c0aceba19f3eea324a4a806e227e [ 57.202534] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknown 2/2/2022 [ 57.202536] Call Trace: [ 57.202537] <TASK> [57.202540] dump_stack_lvl+0x77/0xb0 [ 57.202551] lockdep_rcu_suspicious+0x154/0x1a0 [ 57.202556] rpc_xprt_switch_has_addr+0x17c/0x190 [sunrpc ebe02571b9a8ceebf7d98e71675af20c19bdb1f6] [ 57.202596] rpc_clnt_setup_test_and_add_xprt+0x50/0x180 [sunrpc ebe02571b9a8ceebf7d98e71675af20c19bdb1f6] [ 57.202621] ? rpc_clnt_add_xprt+0x254/0x300 [sunrpc ebe02571b9a8ceebf7d98e71675af20c19bdb1f6] [ 57.202646] rpc_clnt_add_xprt+0x27a/0x300 [sunrpc ebe02571b9a8ceebf7d98e71675af20c19bdb1f6] [ 57.202671] ?
    __pfx_rpc_clnt_setup_test_and_add_xprt+0x10/0x10 [sunrpc ebe02571b9a8ceebf7d98e71675af20c19bdb1f6] [57.202696] nfs4_pnfs_ds_connect+0x345/0x760 [nfsv4 c716d88496ded0ea6d289bbea684fa996f9b57a9] [ 57.202728] ? __pfx_nfs4_test_session_trunk+0x10/0x10 [nfsv4 c716d88496ded0ea6d289bbea684fa996f9b57a9] [ 57.202754] nfs4_fl_prepare_ds+0x75/0xc0 [nfs_layout_nfsv41_files e3a4187f18ae8a27b630f9feae6831b584a9360a] [57.202760] filelayout_write_pagelist+0x4a/0x200 [nfs_layout_nfsv41_files e3a4187f18ae8a27b630f9feae6831b584a9360a] [ 57.202765] pnfs_generic_pg_writepages+0xbe/0x230 [nfsv4 c716d88496ded0ea6d289bbea684fa996f9b57a9] [ 57.202788] __nfs_pageio_add_request+0x3fd/0x520 [nfs 6c976fa593a7c2976f5a0aeb4965514a828e6902] [ 57.202813] nfs_pageio_add_request+0x18b/0x390 [nfs 6c976fa593a7c2976f5a0aeb4965514a828e6902] [ 57.202831] nfs_do_writepage+0x116/0x1e0 [nfs 6c976fa593a7c2976f5a0aeb4965514a828e6902] [ 57.202849] nfs_writepages_callback+0x13/0x30 [nfs 6c976fa593a7c2976f5a0aeb4965514a828e6902] [ 57.202866] write_cache_pages+0x265/0x450 [ 57.202870] ?
    __pfx_nfs_writepages_callback+0x10/0x10 [nfs 6c976fa593a7c2976f5a0aeb4965514a828e6902] [ 57.202891] nfs_writepages+0x141/0x230 [nfs 6c976fa593a7c2976f5a0aeb4965514a828e6902] [ 57.202913] do_writepages+0xd2/0x230 [ 57.202917] ? filemap_fdatawrite_wbc+0x5c/0x80 [ 57.202921] filemap_fdatawrite_wbc+0x67/0x80 [ 57.202924] filemap_write_and_wait_range+0xd9/0x170 [ 57.202930] nfs_wb_all+0x49/0x180 [nfs 6c976fa593a7c2976f5a0aeb4965514a828e6902] [ 57.202947] nfs4_file_flush+0x72/0xb0 [nfsv4 c716d88496ded0ea6d289bbea684fa996f9b57a9] [ 57.202969]
    __se_sys_close+0x46/0xd0 [ 57.202972] do_syscall_64+0x68/0x100 [ 57.202975] ? do_syscall_64+0x77/0x100 [57.202976] ? do_syscall_64+0x77/0x100 [ 57.202979] entry_SYSCALL_64_after_hwframe+0x6e/0x76 [ 57.202982] RIP: 0033:0x7fe2b12e4a94 [ 57.202985] Code: 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 80 3d d5 18 0e 00 00 74 13 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 44 c3 0f 1f 00 48 83 ec 18 89 7c 24 0c e8 c3 [ 57.202987] RSP: 002b:00007ffe857ddb38 EFLAGS: 00000202 ORIG_RAX:
    0000000000000003 [ 57.202989] RAX: ffffffffffffffda RBX: 00007ffe857dfd68 RCX: 00007fe2b12e4a94 [57.202991] RDX: 0000000000002000 RSI: 00007ffe857ddc40 RDI: 0000000000000003 [ 57.202992] RBP:
    00007ffe857dfc50 R08: 7fffffffffffffff R09: 0000000065650f49 [ 57.202993] R10: 00007f ---truncated--- (CVE-2023-52623)

  - 已解決 Linux 核心中的下列弱點：dm: call the resume method on internal suspend There is this reported crash when experimenting with the lvm2 testsuite. The list corruption is caused by the fact that the postsuspend and resume methods were not paired correctly; there were two consecutive calls to the origin_postsuspend function. The second call attempts to remove the hash_list entry from a list, while it was already removed by the first call. Fix __dm_internal_resume so that it calls the preresume and resume methods of the table's targets. If a preresume method of some target fails, we are in a tricky situation. We can't return an error because dm_internal_resume isn't supposed to return errors. We can't return success, because then the resume and postsuspend methods would not be paired correctly. So, we set the DMF_SUSPENDED flag and we fake normal suspend - it may confuse userspace tools, but it won't cause a kernel crash. ------------[ cut here ]------------ kernel BUG at lib/list_debug.c:56! invalid opcode: 0000 [#1] PREEMPT SMP CPU: 1 PID: 8343 Comm: dmsetup Not tainted 6.8.0-rc6 #4 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 RIP:
    0010:__list_del_entry_valid_or_report+0x77/0xc0 <snip> RSP: 0018:ffff8881b831bcc0 EFLAGS: 00010282 RAX:
    000000000000004e RBX: ffff888143b6eb80 RCX: 0000000000000000 RDX: 0000000000000001 RSI: ffffffff819053d0 RDI: 00000000ffffffff RBP: ffff8881b83a3400 R08: 00000000fffeffff R09: 0000000000000058 R10:
    0000000000000000 R11: ffffffff81a24080 R12: 0000000000000001 R13: ffff88814538e000 R14: ffff888143bc6dc0 R15: ffffffffa02e4bb0 FS: 00000000f7c0f780(0000) GS:ffff8893f0a40000(0000) knlGS:0000000000000000 CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033 CR2: 0000000057fb5000 CR3: 0000000143474000 CR4: 00000000000006b0 Call Trace: <TASK> ? die+0x2d/0x80 ? do_trap+0xeb/0xf0 ? __list_del_entry_valid_or_report+0x77/0xc0 ? do_error_trap+0x60/0x80 ? __list_del_entry_valid_or_report+0x77/0xc0 ? exc_invalid_op+0x49/0x60 ?
    __list_del_entry_valid_or_report+0x77/0xc0 ? asm_exc_invalid_op+0x16/0x20 ? table_deps+0x1b0/0x1b0 [dm_mod] ? __list_del_entry_valid_or_report+0x77/0xc0 origin_postsuspend+0x1a/0x50 [dm_snapshot] dm_table_postsuspend_targets+0x34/0x50 [dm_mod] dm_suspend+0xd8/0xf0 [dm_mod] dev_suspend+0x1f2/0x2f0 [dm_mod] ? table_deps+0x1b0/0x1b0 [dm_mod] ctl_ioctl+0x300/0x5f0 [dm_mod] dm_compat_ctl_ioctl+0x7/0x10 [dm_mod] __x64_compat_sys_ioctl+0x104/0x170 do_syscall_64+0x184/0x1b0 entry_SYSCALL_64_after_hwframe+0x46/0x4e RIP: 0033:0xf7e6aead <snip> ---[ end trace 0000000000000000 ]--- (CVE-2024-26880)

  - 已解決 Linux 核心中的下列弱點：netfilter: nf_tables: flush pending destroy work before exit_net release Similar to 2c9f0293280e (netfilter: nf_tables: flush pending destroy work before netlink notifier) to address a race between exit_net and the destroy workqueue. The trace below shows an element to be released via destroy workqueue while exit_net path (triggered via module removal) has already released the set that is used in such transaction. [ 1360.547789] BUG: KASAN: slab-use-after-free in nf_tables_trans_destroy_work+0x3f5/0x590 [nf_tables] [ 1360.547861] Read of size 8 at addr ffff888140500cc0 by task kworker/4:1/152465 [ 1360.547870] CPU: 4 PID: 152465 Comm: kworker/4:1 Not tainted 6.8.0+ #359 [ 1360.547882] Workqueue: events nf_tables_trans_destroy_work [nf_tables] [1360.547984] Call Trace: [ 1360.547991] <TASK> [ 1360.547998] dump_stack_lvl+0x53/0x70 [ 1360.548014] print_report+0xc4/0x610 [ 1360.548026] ? __virt_addr_valid+0xba/0x160 [ 1360.548040] ?
    __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 1360.548054] ? nf_tables_trans_destroy_work+0x3f5/0x590 [nf_tables] [ 1360.548176] kasan_report+0xae/0xe0 [ 1360.548189] ? nf_tables_trans_destroy_work+0x3f5/0x590 [nf_tables] [ 1360.548312] nf_tables_trans_destroy_work+0x3f5/0x590 [nf_tables] [ 1360.548447] ?
    __pfx_nf_tables_trans_destroy_work+0x10/0x10 [nf_tables] [ 1360.548577] ? _raw_spin_unlock_irq+0x18/0x30 [1360.548591] process_one_work+0x2f1/0x670 [ 1360.548610] worker_thread+0x4d3/0x760 [ 1360.548627] ?
    __pfx_worker_thread+0x10/0x10 [ 1360.548640] kthread+0x16b/0x1b0 [ 1360.548653] ? __pfx_kthread+0x10/0x10 [ 1360.548665] ret_from_fork+0x2f/0x50 [ 1360.548679] ? __pfx_kthread+0x10/0x10 [ 1360.548690] ret_from_fork_asm+0x1a/0x30 [ 1360.548707] </TASK> [ 1360.548719] Allocated by task 192061: [ 1360.548726] kasan_save_stack+0x20/0x40 [ 1360.548739] kasan_save_track+0x14/0x30 [ 1360.548750]
    __kasan_kmalloc+0x8f/0xa0 [ 1360.548760] __kmalloc_node+0x1f1/0x450 [ 1360.548771] nf_tables_newset+0x10c7/0x1b50 [nf_tables] [ 1360.548883] nfnetlink_rcv_batch+0xbc4/0xdc0 [nfnetlink] [1360.548909] nfnetlink_rcv+0x1a8/0x1e0 [nfnetlink] [ 1360.548927] netlink_unicast+0x367/0x4f0 [1360.548935] netlink_sendmsg+0x34b/0x610 [ 1360.548944] ____sys_sendmsg+0x4d4/0x510 [ 1360.548953]
    ___sys_sendmsg+0xc9/0x120 [ 1360.548961] __sys_sendmsg+0xbe/0x140 [ 1360.548971] do_syscall_64+0x55/0x120 [ 1360.548982] entry_SYSCALL_64_after_hwframe+0x55/0x5d [ 1360.548994] Freed by task 192222: [1360.548999] kasan_save_stack+0x20/0x40 [ 1360.549009] kasan_save_track+0x14/0x30 [ 1360.549019] kasan_save_free_info+0x3b/0x60 [ 1360.549028] poison_slab_object+0x100/0x180 [ 1360.549036]
    __kasan_slab_free+0x14/0x30 [ 1360.549042] kfree+0xb6/0x260 [ 1360.549049] __nft_release_table+0x473/0x6a0 [nf_tables] [ 1360.549131] nf_tables_exit_net+0x170/0x240 [nf_tables] [ 1360.549221] ops_exit_list+0x50/0xa0 [ 1360.549229] free_exit_list+0x101/0x140 [ 1360.549236] unregister_pernet_operations+0x107/0x160 [ 1360.549245] unregister_pernet_subsys+0x1c/0x30 [ 1360.549254] nf_tables_module_exit+0x43/0x80 [nf_tables] [ 1360.549345] __do_sys_delete_module+0x253/0x370 [1360.549352] do_syscall_64+0x55/0x120 [ 1360.549360] entry_SYSCALL_64_after_hwframe+0x55/0x5d (gdb) list
    *__nft_release_table+0x473 0x1e033 is in __nft_release_table (net/netfilter/nf_tables_api.c:11354). 11349 list_for_each_entry_safe(flowtable, nf, &table->flowtables, list) { 11350 list_del(&flowtable->list);
    11351 nft_use_dec(&table->use); 11352 nf_tables_flowtable_destroy(flowtable); 11353 } 11354 list_for_each_entry_safe(set, ns, &table->sets, list) { 11355 list_del(&set->list); 11356 nft_use_dec(&table->use); 11357 if (set->flags & (NFT_SET_MAP | NFT_SET_OBJECT)) 11358 nft_map_deactivat
    ---truncated--- (CVE-2024-35899)

  - 已解決 Linux 核心中的下列弱點：drm/client: Fully protect modes[] with dev->mode_config.mutex The modes[] array contains pointers to modes on the connectors' mode lists, which are protected by dev->mode_config.mutex. Thus we need to extend modes[] the same protection or by the time we use it the elements may already be pointing to freed/reused memory. (CVE-2024-35950)

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

Rocky Linux 9.6 主機已安裝的套件會受到 TuxCare ALMALINUX9.6：CLSA-2026：1792445930 公告中提及的多個弱點影響。

  - 已解決 Linux 核心中的下列弱點：virt: tdx-guest: Just leak decrypted memory on unrecoverable errors In CoCo VMs it is possible for the untrusted host to cause set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to handle these errors to avoid returning decrypted (shared) memory to the page allocator, which could lead to functional or security issues. Leak the decrypted memory when set_memory_decrypted() fails, and don't need to print an error since set_memory_decrypted() will call WARN_ONCE(). (CVE-2024-57793)

  - 已解決 Linux 核心中的下列弱點：crypto: af_alg - zero initialize memory allocated via sock_kmalloc Several crypto user API contexts and requests allocated with sock_kmalloc() were left uninitialized, relying on callers to set fields explicitly. This resulted in the use of uninitialized data in certain error paths or when new fields are added in the future. The ACVP patches also contain two user-space interface files: algif_kpp.c and algif_akcipher.c. These too rely on proper initialization of their context structures. A particular issue has been observed with the newly added 'inflight' variable introduced in af_alg_ctx by commit: 67b164a871af (crypto: af_alg - Disallow multiple in-flight AIO requests) Because the context is not memset to zero after allocation, the inflight variable has contained garbage values. As a result, af_alg_alloc_areq() has incorrectly returned -EBUSY randomly when the garbage value was interpreted as true:
    https://github.com/gregkh/linux/blame/master/crypto/af_alg.c#L1209 The check directly tests ctx->inflight without explicitly comparing against true/false. Since inflight is only ever set to true or false later, an uninitialized value has triggered -EBUSY failures. Zero-initializing memory allocated with sock_kmalloc() ensures inflight and other fields start in a known state, removing random issues caused by uninitialized data. (CVE-2025-71113)

  - 已解決 Linux 核心中的下列弱點：rxrpc: proc: size address buffers for %pISpc output The AF_RXRPC procfs helpers format local and remote socket addresses into fixed 50-byte stack buffers with %pISpc. That is too small for the longest current-tree IPv6-with-port form the formatter can produce. In lib/vsprintf.c, the compressed IPv6 path uses a dotted-quad tail not only for v4mapped addresses, but also for ISATAP addresses via ipv6_addr_is_isatap(). As a result, a case such as [ffff:ffff:ffff:ffff:0:5efe:255.255.255.255]:65535 is possible with the current formatter. That is 50 visible characters, so 51 bytes including the trailing NUL, which does not fit in the existing char[50] buffers used by net/rxrpc/proc.c. Size the buffers from the formatter's maximum textual form and switch the call sites to scnprintf(). Changes since v1: - correct the changelog to cite the actual maximum current-tree case explicitly - frame the proof around the ISATAP formatting path instead of the earlier mapped-v4 example (CVE-2026-31630)

  - 已解決 Linux 核心中的下列弱點：netfilter: nft_set_rbtree: check for partial overlaps in anonymous sets Userspace provides an optimized representation in case intervals are adjacent, where the end element is omitted. The existing partial overlap detection logic skips anonymous set checks on start elements for this reason. However, it is possible to add intervals that overlap to this anonymous where two start elements with the same, eg. A-B, A-C where C < B. start end A B start end A C Restore the check on overlapping start elements to report an overlap. (CVE-2026-45873)

  - 已解決 Linux 核心中的下列弱點：drm/amd/display: Bound VBIOS record-chain walk loops [Why & How] All record-chain walk loops in bios_parser.c and bios_parser2.c use for(;;) and only terminate on a 0xFF record_type sentinel or zero record_size. A malformed VBIOS image missing the terminator record causes unbounded iteration at probe time, potentially hundreds of thousands of iterations with record_size=1. In the final iterations near the BIOS image boundary, struct casts beyond the 2-byte header validated by GET_IMAGE can also read out of bounds. Cap all 14 record-chain walk loops to BIOS_MAX_NUM_RECORD (256) iterations. The atombios.h defines up to 22 distinct record types and atomfirmware.h has 13. Assuming an average of less than 10 records per type (which is reasonable since most are connector- based) 256 is a generous upper bound. (cherry picked from commit 95700a3d660287ed657d6892f7be9ffc0e294a93) (CVE-2026-53138)

請注意，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 架構 ;

    - 使用者模式 Linux (UML) ;

    - x86 架構;

    - 密碼編譯 API;

    - 英特爾 NPU 驅動程式;

    - 計算加速架構;

    - ACPI 驅動程式；

    - 驅動程式核心；

    - DRBD 分散式複制區塊裝置驅動程式；

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

    - Ublk 使用者空間區塊驅動程式；

    - 壓縮 RAM 區塊裝置驅動程式；

    - 藍牙驅動程式;

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

    - CXL (Compute Express Link) 驅動程式；

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

    - EFI 核心；

    - FPGA 架構；

    - GPU 驅動程式；

    - HID 子系統 ;

    - 硬體監控驅動程式 ;

    - I2C 子系統 ;

    - I3C 子系統 ;

    - InfiniBand 驅動程式 ;

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

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

    - IOMMU 子系統;

    - 多個裝置驅動程式；

    - 媒體驅動程式 ;

    - Fastrpc 驅動程式；

    - 網路驅動程式；

    - Mellanox 網路驅動程式 ;

    - Microsoft Azure 網路介面卡 (MANA) 驅動程式；

    - MediaTek 網路驅動程式；

    - NVME 驅動程式；

    - 作業效能值 (OPP) 驅動程式;

    - PCI 子系統；

    - PTP 時鐘架構；

    - RPMSG 子系統；

    - SCSI 子系統；

    - SoundWire 子系統；

    - SPI 子系統；

    - Greybus lights staging 驅動程式；

    - 媒體演示驅動程式；

    - NVIDIA Tegra 嵌入式控制器 （NVEC） 暫存驅動程式;

    - Realtek RTL8723BS SDIO 驅動程式；

    - TCM 子系統；

    - 受信任執行環境驅動程式；

    - Thunderbolt 和 USB4 驅動程式 ;

    - TTY 驅動程式；

    - USB Gadget 驅動程式；

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

    - USB 序列驅動程式；

    - vDPA 驅動程式;

    - VFIO 驅動程式 ;

    - Virtio Host (VHOST) 子系統;

    - Virtio 驅動程式；

    - Xen Hypervisor 驅動程式；

    - 9P 分散式檔案系統 ;

    - AFS 檔案系統;

    - 檔案系統基礎架構；

    - BTRFS 檔案系統 ;

    - Ceph 分散式檔案系統；

    - AexFAT 檔案系統；

    - F2FS 檔案系統；

    - GFS2 檔案系統；

    - HFS 檔案系統；

    - HFS+ 檔案系統；

    - JFS 檔案系統；

    - 網路檔案系統程式庫；

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

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

    - NTFS3 檔案系統；

    - OCFS2 檔案系統；

    - OrangeFS 檔案系統；

    - SMB 網路檔案系統；

    - BPF 子系統；

    - 檔案系統加密 （fscrypt）;

    - 軟體節點和裝置屬性;

    - IPv4 網路；

    - KVM 子系統;

    - Mellanox 驅動程式；

    - 記憶體管理；

    - 網路核心；

    - Netfilter；

    - 通訊端訊息基礎架構 ;

    - MediaTek SoC 驅動程式；

    - Sun RPC 通訊協定；

    - 網路流量控制；

    - IPv6 網路；

    - Amateur Radio 驅動程式；

    - 藍牙子系統；

    - IP 通道定義；

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

    - 多重通訊協定標籤交換驅動程式；

    - 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-52956CVE-2026-53000CVE-2026-52991CVE-2026-53005CVE-2026-53009CVE-2026-53024CVE-2026-53025CVE-2026-53053CVE-2026-52941CVE-2026-53078CVE-2026-53070CVE-2026-53089CVE-2026-53090CVE-2026-53091CVE-2026-53109CVE-2026-53118CVE-2026-52934CVE-2026-53129CVE-2026-53120CVE-2026-53131CVE-2026-53132CVE-2026-53133CVE-2026-53148CVE-2026-53221CVE-2026-53217CVE-2026-53230CVE-2026-53216CVE-2026-53198CVE-2026-53196CVE-2026-53232CVE-2026-53186CVE-2026-53185CVE-2026-53183CVE-2026-53239CVE-2026-53182CVE-2026-52926CVE-2026-52922CVE-2026-52921CVE-2026-53275CVE-2026-53262CVE-2026-53264CVE-2026-53266CVE-2026-53256CVE-2026-53270CVE-2026-53281CVE-2026-53269CVE-2026-53250CVE-2026-53254CVE-2026-53273CVE-2026-52919CVE-2026-52918CVE-2026-52916CVE-2026-52915、 、 、 、 CVE-2026-63906CVE-2026-63795CVE-2026-53399CVE-2026-63797CVE-2026-63796CVE-2026-63800CVE-2026-63801CVE-2026-63804CVE-2026-63807CVE-2026-63808CVE-2026-53398CVE-2026-63818CVE-2026-63815CVE-2026-63825CVE-2026-63828CVE-2026-63829CVE-2026-63830CVE-2026-63831CVE-2026-53384CVE-2026-63858CVE-2026-63853CVE-2026-63886CVE-2026-63887CVE-2026-63888CVE-2026-63893CVE-2026-63924CVE-2026-63922CVE-2026-63926CVE-2026-63921CVE-2026-63919CVE-2026-63917CVE-2026-63940CVE-2026-63916CVE-2026-63915CVE-2026-63914CVE-2026-63944CVE-2026-63912CVE-2026-53368CVE-2026-53361CVE-2026-53358CVE-2026-63979CVE-2026-63948CVE-2026-63952CVE-2026-63974CVE-2026-63947CVE-2026-63976CVE-2026-63980CVE-2026-63975CVE-2026-63945CVE-2026-63946CVE-2026-63978CVE-2026-53357CVE-2026-53355CVE-2026-53354CVE-2026-53284、 、 、 、 CVE-2026-64087CVE-2026-64025CVE-2026-64018CVE-2026-64032CVE-2026-64029CVE-2026-64033CVE-2026-64034CVE-2026-64039CVE-2026-64046CVE-2026-64047CVE-2026-64015CVE-2026-64051CVE-2026-64048CVE-2026-64055CVE-2026-64056CVE-2026-64064CVE-2026-64073CVE-2026-64076CVE-2026-64011CVE-2026-64082CVE-2026-64077CVE-2026-64083CVE-2026-64084CVE-2026-64085CVE-2026-64086CVE-2026-64099CVE-2026-64098CVE-2026-64102CVE-2026-64097CVE-2026-64096CVE-2026-64093CVE-2026-64103CVE-2026-64092CVE-2026-64091CVE-2026-64089CVE-2026-64106CVE-2026-64088CVE-2026-64010CVE-2026-64007CVE-2026-64000CVE-2026-64118CVE-2026-64112CVE-2026-64113CVE-2026-64114CVE-2026-64111CVE-2026-64116CVE-2026-64121CVE-2026-64115CVE-2026-64108CVE-2026-64109CVE-2026-64117CVE-2026-63994CVE-2026-63993CVE-2026-63992CVE-2026-63984、 、 、 、 CVE-2026-64191CVE-2026-64144CVE-2026-64138CVE-2026-64148CVE-2026-64147CVE-2026-64153CVE-2026-64155CVE-2026-64160CVE-2026-64163CVE-2026-64165CVE-2026-64137CVE-2026-64168CVE-2026-64166CVE-2026-64170CVE-2026-64173CVE-2026-64174CVE-2026-64177CVE-2026-64178CVE-2026-64136CVE-2026-64180CVE-2026-64179CVE-2026-64182CVE-2026-64183CVE-2026-64184CVE-2026-64185CVE-2026-64231CVE-2026-64225CVE-2026-64237CVE-2026-64221CVE-2026-64220CVE-2026-64219CVE-2026-64247CVE-2026-64218CVE-2026-64217CVE-2026-64214CVE-2026-64249CVE-2026-64206CVE-2026-64135CVE-2026-64134CVE-2026-64133CVE-2026-64361CVE-2026-64303CVE-2026-64313CVE-2026-64315CVE-2026-64280CVE-2026-64320CVE-2026-64364CVE-2026-64319CVE-2026-64268CVE-2026-64269CVE-2026-64355CVE-2026-64128CVE-2026-64127CVE-2026-64126CVE-2026-64125、 、 、 、 CVE-2026-64552CVE-2026-64394CVE-2026-64393CVE-2026-64397CVE-2026-64396CVE-2026-64399CVE-2026-64400CVE-2026-64408CVE-2026-64438CVE-2026-64441CVE-2026-64392CVE-2026-64450CVE-2026-64445CVE-2026-64475CVE-2026-64510CVE-2026-64518CVE-2026-64523CVE-2026-64529CVE-2026-64391CVE-2026-64534CVE-2026-64530CVE-2026-64535CVE-2026-64541CVE-2026-64548CVE-2026-64551CVE-2026-64598CVE-2026-64597CVE-2026-68082CVE-2026-64586CVE-2026-64564CVE-2026-64562CVE-2026-68083CVE-2026-64561CVE-2026-64557CVE-2026-64555CVE-2026-68117CVE-2026-64554CVE-2026-64390CVE-2026-64387CVE-2026-64386CVE-2026-68154CVE-2026-68136CVE-2026-68137CVE-2026-68138CVE-2026-68127CVE-2026-68147CVE-2026-68156CVE-2026-68144CVE-2026-68123CVE-2026-68124CVE-2026-68152CVE-2026-64385CVE-2026-64384CVE-2026-64383CVE-2026-64382、 、 、 、 CVE-2026-72083CVE-2026-68228CVE-2026-68213CVE-2026-68300CVE-2026-68229CVE-2026-68302CVE-2026-68343CVE-2026-68381CVE-2026-68388CVE-2026-68426CVE-2026-68210CVE-2026-68457CVE-2026-68431CVE-2026-68461CVE-2026-68470CVE-2026-68476CVE-2026-68477CVE-2026-72014CVE-2026-68209CVE-2026-72033CVE-2026-72020CVE-2026-72041CVE-2026-72065CVE-2026-72069CVE-2026-72071CVE-2026-72130CVE-2026-72129CVE-2026-72191CVE-2026-72126CVE-2026-72125CVE-2026-72124CVE-2026-72192CVE-2026-72111CVE-2026-72098CVE-2026-72085CVE-2026-72194CVE-2026-72084CVE-2026-68206CVE-2026-68198CVE-2026-68162CVE-2026-72289CVE-2026-72222CVE-2026-72226CVE-2026-72234CVE-2026-72221CVE-2026-72255CVE-2026-72296CVE-2026-72251CVE-2026-72200CVE-2026-72217CVE-2026-72288CVE-2026-68161CVE-2026-68160CVE-2026-68159CVE-2026-68158、 、 、 、 CVE-2026-72499CVE-2026-72351CVE-2026-72348CVE-2026-72383CVE-2026-72380CVE-2026-72398CVE-2026-72399CVE-2026-72421CVE-2026-72422CVE-2026-72434CVE-2026-72339CVE-2026-72451CVE-2026-72436CVE-2026-72454CVE-2026-72466CVE-2026-72472CVE-2026-72473CVE-2026-72487CVE-2026-72329CVE-2026-72489CVE-2026-72488CVE-2026-72491CVE-2026-72494CVE-2026-72495CVE-2026-72496CVE-2026-74302CVE-2026-74287CVE-2026-74305CVE-2026-74280CVE-2026-74279CVE-2026-74269CVE-2026-74310CVE-2026-74268CVE-2026-74267CVE-2026-74264CVE-2026-74345CVE-2026-74255CVE-2026-72323CVE-2026-72322CVE-2026-72320CVE-2026-74408CVE-2026-74394CVE-2026-74398CVE-2026-74401CVE-2026-74384CVE-2026-74406CVE-2026-74410CVE-2026-74405CVE-2026-74350CVE-2026-74376CVE-2026-74407CVE-2026-72319CVE-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 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

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

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

    - ARM64 架構;

    - S390 架構;

    - x86 架構；

    - DRBD 分散式複制區塊裝置驅動程式；

    - InfiniBand 驅動程式；

    - IOMMU 子系統；

    - 多個裝置驅動程式；

    - 網路驅動程式；

    - Microsoft Azure 網路介面卡 (MANA) 驅動程式；

    - NVME 驅動程式；

    - TCM 子系統；

    - Virtio Host (VHOST) 子系統;

    - Xen Hypervisor 驅動程式；

    - AFS 檔案系統；

    - 檔案系統基礎架構；

    - 網路檔案系統程式庫；

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

    - NTFS3 檔案系統；

    - OCFS2 檔案系統；

    - OrangeFS 檔案系統；

    - SMB 網路檔案系統；

    - IPv4 網路；

    - Sun RPC 通訊協定；

    - IPv6 網路；

    - IP 通道定義；

    - Netfilter；

    - TCP 網路通訊協定；

    - 鎖定基元 ;

    - 9P 檔案系統網路通訊協定；

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

    - 網路核心；

    - IFE 協議;

    - RxRPC 工作階段通訊端；

    - 網路流量控制 ;

    - SCTP 通訊協定；

    - SMC 通訊端;

    - TIPC 通訊協定;

    - XFRM 子系統;（CVE-2026-64530 ， ， ， CVE-2026-64535， CVE-2026-64541CVE-2026-72277CVE-2026-72137CVE-2026-72139CVE-2026-72064CVE-2026-72065CVE-2026-72046CVE-2026-72083CVE-2026-72069CVE-2026-72084CVE-2026-72085CVE-2026-72098CVE-2026-72129CVE-2026-72130CVE-2026-72041CVE-2026-72192CVE-2026-72191CVE-2026-72194CVE-2026-72217CVE-2026-72220CVE-2026-72221CVE-2026-72222CVE-2026-72033CVE-2026-72234CVE-2026-72226CVE-2026-72248CVE-2026-72249CVE-2026-72251CVE-2026-72278CVE-2026-72279CVE-2026-72020CVE-2026-72288CVE-2026-72287CVE-2026-72323CVE-2026-72322CVE-2026-72329CVE-2026-72320CVE-2026-72319CVE-2026-72318CVE-2026-72339CVE-2026-72317CVE-2026-72299CVE-2026-72296CVE-2026-72348CVE-2026-72289CVE-2026-72014CVE-2026-72351CVE-2026-72393CVE-2026-72381CVE-2026-72398CVE-2026-72366CVE-2026-72399CVE-2026-72412CVE-2026-64551CVE-2026-68457CVE-2026-72417CVE-2026-68083CVE-2026-68476CVE-2026-68477CVE-2026-72355CVE-2026-64534CVE-2026-72422， CVE-2026-72429CVE-2026-72436CVE-2026-72442CVE-2026-72451CVE-2026-72463CVE-2026-72466CVE-2026-72472CVE-2026-72473CVE-2026-72477CVE-2026-72491CVE-2026-72493CVE-2026-72494CVE-2026-72495CVE-2026-72496CVE-2026-72501CVE-2026-74255CVE-2026-74267CVE-2026-74268CVE-2026-74269CVE-2026-74287CVE-2026-74310CVE-2026-74345CVE-2026-74350CVE-2026-74361CVE-2026-74376CVE-2026-74384CVE-2026-74394CVE-2026-74398CVE-2026-74401CVE-2026-74406CVE-2026-74427CVE-2026-74428CVE-2026-74433CVE-2026-74434CVE-2026-74436CVE-2026-74439CVE-2026-80665

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

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

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

  - RDMA/siw：修正端點/通訊端關聯處理 透過 siw_socket_disassoc（） 取消通訊端與端點的關聯，可能會釋放該端點上的最後一個參照並將其釋放。因此，請勿在呼叫該函式之後清除端點通訊端指標，而是在內部清除。此修正了一個： 錯誤：KASAN：siw_cm_work_handler （drivers/infiniband/sw/siw/siw_cm.c：1053 drivers/infiniband/sw/siw/siw_cm.c：1075） 中的 slab-use-after-free （drivers/infiniband/sw/siw/.c：1075） 在建立連線期間處理格式錯誤的 MPA 要求之後，導致新端點關閉。（CVE-2026-74345）

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

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

  - 已解決 Linux 核心中的下列弱點：virt: tdx-guest: Just leak decrypted memory on unrecoverable errors In CoCo VMs it is possible for the untrusted host to cause set_memory_decrypted() to fail such that an error is returned and the resulting memory is shared. Callers need to take care to handle these errors to avoid returning decrypted (shared) memory to the page allocator, which could lead to functional or security issues. Leak the decrypted memory when set_memory_decrypted() fails, and don't need to print an error since set_memory_decrypted() will call WARN_ONCE(). (CVE-2024-57793)

  - 已解決 Linux 核心中的下列弱點：crypto: af_alg - zero initialize memory allocated via sock_kmalloc Several crypto user API contexts and requests allocated with sock_kmalloc() were left uninitialized, relying on callers to set fields explicitly. This resulted in the use of uninitialized data in certain error paths or when new fields are added in the future. The ACVP patches also contain two user-space interface files: algif_kpp.c and algif_akcipher.c. These too rely on proper initialization of their context structures. A particular issue has been observed with the newly added 'inflight' variable introduced in af_alg_ctx by commit: 67b164a871af (crypto: af_alg - Disallow multiple in-flight AIO requests) Because the context is not memset to zero after allocation, the inflight variable has contained garbage values. As a result, af_alg_alloc_areq() has incorrectly returned -EBUSY randomly when the garbage value was interpreted as true:
    https://github.com/gregkh/linux/blame/master/crypto/af_alg.c#L1209 The check directly tests ctx->inflight without explicitly comparing against true/false. Since inflight is only ever set to true or false later, an uninitialized value has triggered -EBUSY failures. Zero-initializing memory allocated with sock_kmalloc() ensures inflight and other fields start in a known state, removing random issues caused by uninitialized data. (CVE-2025-71113)

  - 已解決 Linux 核心中的下列弱點：rxrpc: proc: size address buffers for %pISpc output The AF_RXRPC procfs helpers format local and remote socket addresses into fixed 50-byte stack buffers with %pISpc. That is too small for the longest current-tree IPv6-with-port form the formatter can produce. In lib/vsprintf.c, the compressed IPv6 path uses a dotted-quad tail not only for v4mapped addresses, but also for ISATAP addresses via ipv6_addr_is_isatap(). As a result, a case such as [ffff:ffff:ffff:ffff:0:5efe:255.255.255.255]:65535 is possible with the current formatter. That is 50 visible characters, so 51 bytes including the trailing NUL, which does not fit in the existing char[50] buffers used by net/rxrpc/proc.c. Size the buffers from the formatter's maximum textual form and switch the call sites to scnprintf(). Changes since v1: - correct the changelog to cite the actual maximum current-tree case explicitly - frame the proof around the ISATAP formatting path instead of the earlier mapped-v4 example (CVE-2026-31630)

  - 已解決 Linux 核心中的下列弱點：netfilter: nft_set_rbtree: check for partial overlaps in anonymous sets Userspace provides an optimized representation in case intervals are adjacent, where the end element is omitted. The existing partial overlap detection logic skips anonymous set checks on start elements for this reason. However, it is possible to add intervals that overlap to this anonymous where two start elements with the same, eg. A-B, A-C where C < B. start end A B start end A C Restore the check on overlapping start elements to report an overlap. (CVE-2026-45873)

  - 已解決 Linux 核心中的下列弱點：drm/amd/display: Bound VBIOS record-chain walk loops [Why & How] All record-chain walk loops in bios_parser.c and bios_parser2.c use for(;;) and only terminate on a 0xFF record_type sentinel or zero record_size. A malformed VBIOS image missing the terminator record causes unbounded iteration at probe time, potentially hundreds of thousands of iterations with record_size=1. In the final iterations near the BIOS image boundary, struct casts beyond the 2-byte header validated by GET_IMAGE can also read out of bounds. Cap all 14 record-chain walk loops to BIOS_MAX_NUM_RECORD (256) iterations. The atombios.h defines up to 22 distinct record types and atomfirmware.h has 13. Assuming an average of less than 10 records per type (which is reasonable since most are connector- based) 256 is a generous upper bound. (cherry picked from commit 95700a3d660287ed657d6892f7be9ffc0e294a93) (CVE-2026-53138)

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

CentOS Linux 8.5 主機已安裝的套件會受到 TuxCare CENTOS8.5：CLSA-2026：1792979985 公告中提及的多個弱點影響。

  - 已解決 Linux 核心中的下列弱點：net: bridge: fix vlan tunnel dst refcnt when egressing The egress tunnel code uses dst_clone() and directly sets the result which is wrong because the entry might have 0 refcnt or be already deleted, causing number of problems. It also triggers the WARN_ON() in dst_hold()[1] when a refcnt couldn't be taken. Fix it by using dst_hold_safe() and checking if a reference was actually taken before setting the dst. [1] dmesg WARN_ON log and following refcnt errors WARNING: CPU: 5 PID: 38 at include/net/dst.h:230 br_handle_egress_vlan_tunnel+0x10b/0x134 [bridge] Modules linked in: 8021q garp mrp bridge stp llc bonding ipv6 virtio_net CPU: 5 PID: 38 Comm:
    ksoftirqd/5 Kdump: loaded Tainted: G W 5.13.0-rc3+ #360 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014 RIP: 0010:br_handle_egress_vlan_tunnel+0x10b/0x134 [bridge] Code: e8 85 bc 01 e1 45 84 f6 74 90 45 31 f6 85 db 48 c7 c7 a0 02 19 a0 41 0f 94 c6 31 c9 31 d2 44 89 f6 e8 64 bc 01 e1 85 db 75 02 <0f> 0b 31 c9 31 d2 44 89 f6 48 c7 c7 70 02 19 a0 e8 4b bc 01 e1 49 RSP:
    0018:ffff8881003d39e8 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffffffffa01902a0 RBP: ffff8881040c6700 R08:
    0000000000000000 R09: 0000000000000001 R10: 2ce93d0054fe0d00 R11: 54fe0d00000e0000 R12: ffff888109515000 R13: 0000000000000000 R14: 0000000000000001 R15: 0000000000000401 FS: 0000000000000000(0000) GS:ffff88822bf40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2:
    00007f42ba70f030 CR3: 0000000109926000 CR4: 00000000000006e0 Call Trace: br_handle_vlan+0xbc/0xca [bridge]
    __br_forward+0x23/0x164 [bridge] deliver_clone+0x41/0x48 [bridge] br_handle_frame_finish+0x36f/0x3aa [bridge] ? skb_dst+0x2e/0x38 [bridge] ? br_handle_ingress_vlan_tunnel+0x3e/0x1c8 [bridge] ? br_handle_frame_finish+0x3aa/0x3aa [bridge] br_handle_frame+0x2c3/0x377 [bridge] ? __skb_pull+0x33/0x51 ? vlan_do_receive+0x4f/0x36a ? br_handle_frame_finish+0x3aa/0x3aa [bridge]
    __netif_receive_skb_core+0x539/0x7c6 ? __list_del_entry_valid+0x16e/0x1c2
    __netif_receive_skb_list_core+0x6d/0xd6 netif_receive_skb_list_internal+0x1d9/0x1fa gro_normal_list+0x22/0x3e dev_gro_receive+0x55b/0x600 ? detach_buf_split+0x58/0x140 napi_gro_receive+0x94/0x12e virtnet_poll+0x15d/0x315 [virtio_net] __napi_poll+0x2c/0x1c9 net_rx_action+0xe6/0x1fb __do_softirq+0x115/0x2d8 run_ksoftirqd+0x18/0x20 smpboot_thread_fn+0x183/0x19c ? smpboot_unregister_percpu_thread+0x66/0x66 kthread+0x10a/0x10f ? kthread_mod_delayed_work+0xb6/0xb6 ret_from_fork+0x22/0x30 ---[ end trace 49f61b07f775fd2b ]--- dst_release: dst:00000000c02d677a refcnt:-1 dst_release underflow (CVE-2021-47222)

  - 已解決 Linux 核心中的下列弱點：net: bridge: fix vlan tunnel dst null pointer dereference This patch fixes a tunnel_dst null pointer dereference due to lockless access in the tunnel egress path. When deleting a vlan tunnel the tunnel_dst pointer is set to NULL without waiting a grace period (i.e. while it's still usable) and packets egressing are dereferencing it without checking.
    Use READ/WRITE_ONCE to annotate the lockless use of tunnel_id, use RCU for accessing tunnel_dst and make sure it is read only once and checked in the egress path. The dst is already properly RCU protected so we don't need to do anything fancy than to make sure tunnel_id and tunnel_dst are read only once and checked in the egress path. (CVE-2021-47223)

  - 已解決 Linux 核心中的下列弱點：bpf: Guard stack limits against 32bit overflow This patch promotes the arithmetic around checking stack bounds to be done in the 64-bit domain, instead of the current 32bit. The arithmetic implies adding together a 64-bit register with a int offset.
    The register was checked to be below 1<<29 when it was variable, but not when it was fixed. The offset either comes from an instruction (in which case it is 16 bit), from another register (in which case the caller checked it to be below 1<<29 [1]), or from the size of an argument to a kfunc (in which case it can be a u32 [2]). Between the register being inconsistently checked to be below 1<<29, and the offset being up to an u32, it appears that we were open to overflowing the `int`s which were currently used for arithmetic. [1] https://github.com/torvalds/linux/blob/815fb87b753055df2d9e50f6cd80eb10235fe3e9/kernel/bpf/verifier.c#L7494-L7498 [2] https://github.com/torvalds/linux/blob/815fb87b753055df2d9e50f6cd80eb10235fe3e9/kernel/bpf/verifier.c#L11904 (CVE-2023-52676)

  - 已解決 Linux 核心中的下列弱點：cifs: fix session state check in reconnect to avoid use-after-free issue Don't collect exiting session in smb2_reconnect_server(), because it will be released soon. Note that the exiting session will stay in server->smb_ses_list until it complete the cifs_free_ipc() and logoff() and then delete itself from the list. (CVE-2023-53794)

  - 已解決 Linux 核心中的下列弱點：ubi: Fix use-after-free when volume resizing failed There is an use-after-free problem reported by KASAN:
    ================================================================== BUG: KASAN: use-after-free in ubi_eba_copy_table+0x11f/0x1c0 [ubi] Read of size 8 at addr ffff888101eec008 by task ubirsvol/4735 CPU: 2 PID: 4735 Comm: ubirsvol Not tainted 6.1.0-rc1-00003-g84fa3304a7fc-dirty #14 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x34/0x44 print_report+0x171/0x472 kasan_report+0xad/0x130 ubi_eba_copy_table+0x11f/0x1c0 [ubi] ubi_resize_volume+0x4f9/0xbc0 [ubi] ubi_cdev_ioctl+0x701/0x1850 [ubi] __x64_sys_ioctl+0x11d/0x170 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 </TASK> When ubi_change_vtbl_record() returns an error in ubi_resize_volume(), new_eba_tbl will be freed on error handing path, but it is holded by vol->eba_tbl in ubi_eba_replace_table(). It means that the liftcycle of vol->eba_tbl and vol are different, so when resizing volume in next time, it causing an use-after-free fault. Fix it by not freeing new_eba_tbl after it replaced in ubi_eba_replace_table(), while will be freed in next volume resizing. (CVE-2023-53800)

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

ID	名稱	產品	系列	已發布	已更新	嚴重性
366778	AlmaLinux 9.2 [TuxCare] 安全性更新：bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc 多個弱點（ALMALINUX9.2：CLSA-2026：1792243434）	Nessus	Alma Linux Local Security Checks	2026/10/17	2026/10/27	medium
369491	Rocky Linux 9.6 [TuxCare] 安全性更新：kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc 多個漏洞（ALMALINUX9.6：CLSA-2026：1792445930）	Nessus	Rocky Linux Local Security Checks	2026/10/21	2026/10/21	high
348386	Ubuntu 24.04 LTS / Pro 即時 24.04 LTS：Linux 核心（NVIDIA Tegra）弱點（USN-8781-1）	Nessus	Ubuntu Local Security Checks	2026/9/21	2026/9/21	high
365768	Ubuntu 26.04 LTS：Linux 核心 (Azure) 弱點 (USN-8888-1)	Nessus	Ubuntu Local Security Checks	2026/10/14	2026/10/14	medium
350177	Ubuntu 24.04 LTS/26.04 LTS：Linux 核心弱點 (USN-8816-1)	Nessus	Ubuntu Local Security Checks	2026/9/25	2026/9/30	critical
365525	Ubuntu 24.04 LTS：Linux 核心 (Azure) 弱點 (USN-8918-1)	Nessus	Ubuntu Local Security Checks	2026/10/14	2026/10/14	medium
335600	Linux Distros 未修補弱點：CVE-2026-74345	Nessus	Misc.	2026/8/15	2026/11/7	critical
365522	Ubuntu 24.04 LTS : Linux 核心弱點 (USN-8917-1)	Nessus	Ubuntu Local Security Checks	2026/10/14	2026/10/14	medium
369490	AlmaLinux 9.6 [TuxCare] 安全性更新：kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc 多個弱點（ALMALINUX9.6：CLSA-2026：1792445930）	Nessus	Alma Linux Local Security Checks	2026/10/21	2026/10/21	high
371988	CentOS Linux 8.5 [TuxCare] 安全性更新：bpftool / kernel / kernel-core / kernel-cross-headers / etc多個弱點（CENTOS8.5：CLSA-2026：1792979985）	Nessus	CentOS Local Security Checks	2026/10/26	2026/11/2	high

偵測

搜尋 Plugin

medium

high

high

medium

critical

medium

critical

medium

high

high