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

  - lockd， nfsd：RCU 保護nlmsvc_ops分派nlmsvc_ops由 nfsd_lockd_init（） 發布，並由 nfsd_lockd_shutdown（） 使用普通儲存區清除，而 lockd 則從 fs/lockd/svcsubs.c 中的分派網站解除參照。指標以 nfsd 的 .rodata 為目標，而 fopen/fclose 回呼位於 nfsd 的 .text 中，因此 rmmod nfsd 之後的過時載入會導致 NULL 解除參照或模組文字釋放後使用。
    將nlmsvc_ops宣告為__rcu，透過 rcu_assign_pointer（） 發布，透過 RCU_INIT_POINTER（） + synchronize_rcu（） 清除。將結構模組 *owner 欄位新增至nlmsvc_binding，並使用 try_module_get/module_put 將模組釘選到間接呼叫中。當綁定被拆除時，請回歸到 fput（） 以避免洩漏結構檔案參照。（CVE-2026-89709）

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

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

  - lockd、nfsd：RCU-protect nlmsvc_ops分派nlmsvc_ops由 nfsd_lockd_init（） 发布，并由 nfsd_lockd_shutdown（） 使用普通存储进行清除，而 lockd 会取消引用 fs/lockd/svcsubs.c 中的分派站点对其进行取消引用。指针以 nfsd 的 .rodata 为目标，而 fopen/fclose 回调存在于 nfsd 的 .text 中，因此 rmmod nfsd 后的过时加载会导致空指针取消引用或模块文本释放后使用。
    将nlmsvc_ops声明为 __rcu，通过 rcu_assign_pointer（） 发布，通过 RCU_INIT_POINTER（） + synchronize_rcu（） 清除。向nlmsvc_binding添加结构模块 *owner 字段，并通过 try_module_get/module_put 将模块固定在间接调用中。拆散绑定后，回退到 fput（） 以避免泄漏结构文件引用。（CVE-2026-89709）

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

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

  - lockd、nfsd:RCU-protect nlmsvc_ops ディスパッチnlmsvc_opsは、nfsd_lockd_init() によって公開され、プレーンストアで nfsd_lockd_shutdown() によってクリアされますが、lockd は、fs/lockd/svcsubs.c のディスパッチサイトから無防備に逆参照します。ポインターは nfsd の .rodata をターゲットとし、fopen/fclose コールバックは nfsd の .text 内に存在するため、rmmod nfsd の後のロードが古くなると、NULL デリファレンスまたはモジュールテキストの use-after-free エラーが発生します。
    nlmsvc_ops を __rcu として宣言し、rcu_assign_pointer() を通じて公開し、RCU_INIT_POINTER() + synchronize_rcu() を通じて消去します。struct module *owner フィールドを追加して、try_module_get/module_put の間接呼び出し間でモジュールをnlmsvc_bindingおよび固定します。バインドが破棄されたら、fput() にフォールバックして、構造体ファイル参照の漏洩を回避してください。(CVE-2026-89709)

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

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

  - lockd, nfsd: RCU-protect nlmsvc_ops dispatch nlmsvc_ops is published by nfsd_lockd_init() and cleared by     nfsd_lockd_shutdown() with plain stores, while lockd dereferences it unguarded from dispatch sites in     fs/lockd/svcsubs.c. The pointer targets nfsd's .rodata and the fopen/fclose callbacks live in nfsd's     .text, so a stale load after rmmod nfsd results in either a NULL deref or a module-text use-after-free.
    Declare nlmsvc_ops as __rcu, publish via rcu_assign_pointer(), clear via RCU_INIT_POINTER() +     synchronize_rcu(). Add a struct module *owner field to nlmsvc_binding and pin the module across indirect     calls with try_module_get/module_put. When the binding is torn down, fall back to fput() to avoid leaking     struct file references. (CVE-2026-89709)

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

The CentOS Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS7:CLSA-2026:1793321383 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix premature hw access     after PCI error After a recoverable PCI error has been detected and recovered, qla driver needs to check     to see if the error condition still persist and/or wait for the OS to give the resume signal. Sep 8     22:26:03 localhost kernel: WARNING: CPU: 9 PID: 124606 at qla_tmpl.c:440 qla27xx_fwdt_entry_t266+0x55/0x60     [qla2xxx] Sep 8 22:26:03 localhost kernel: RIP: 0010:qla27xx_fwdt_entry_t266+0x55/0x60 [qla2xxx] Sep 8     22:26:03 localhost kernel: Call Trace: Sep 8 22:26:03 localhost kernel: ? qla27xx_walk_template+0xb1/0x1b0     [qla2xxx] Sep 8 22:26:03 localhost kernel: ? qla27xx_execute_fwdt_template+0x12a/0x160 [qla2xxx] Sep 8     22:26:03 localhost kernel: ? qla27xx_fwdump+0xa0/0x1c0 [qla2xxx] Sep 8 22:26:03 localhost kernel: ?     qla2xxx_pci_mmio_enabled+0xfb/0x120 [qla2xxx] Sep 8 22:26:03 localhost kernel: ?     report_mmio_enabled+0x44/0x80 Sep 8 22:26:03 localhost kernel: ? report_slot_reset+0x80/0x80 Sep 8     22:26:03 localhost kernel: ? pci_walk_bus+0x70/0x90 Sep 8 22:26:03 localhost kernel: ?     aer_dev_correctable_show+0xc0/0xc0 Sep 8 22:26:03 localhost kernel: ? pcie_do_recovery+0x1bb/0x240 Sep 8     22:26:03 localhost kernel: ? aer_recover_work_func+0xaa/0xd0 Sep 8 22:26:03 localhost kernel: ?     process_one_work+0x1a7/0x360 .. Sep 8 22:26:03 localhost kernel: qla2xxx [0000:42:00.2]-8041:22: detected     PCI disconnect. Sep 8 22:26:03 localhost kernel: qla2xxx [0000:42:00.2]-107ff:22: qla27xx_fwdt_entry_t262:
    dump ram MB failed. Area 5h start 198013h end 198013h Sep 8 22:26:03 localhost kernel: qla2xxx     [0000:42:00.2]-107ff:22: Unable to capture FW dump Sep 8 22:26:03 localhost kernel: qla2xxx     [0000:42:00.2]-1015:22: cmd=0x0, waited 5221 msecs Sep 8 22:26:03 localhost kernel: qla2xxx     [0000:42:00.2]-680d:22: mmio enabled returning. Sep 8 22:26:03 localhost kernel: qla2xxx     [0000:42:00.2]-d04c:22: MBX Command timeout for cmd 0, iocontrol=ffffffff jiffies=10140f2e5     mb[0-3]=[0xffff 0xffff 0xffff 0xffff] (CVE-2022-49157)

  - In the Linux kernel, the following vulnerability has been resolved: mrp: introduce active flags to prevent     UAF when applicant uninit The caller of del_timer_sync must prevent restarting of the timer, If we have no     this synchronization, there is a small probability that the cancellation will not be successful. And     syzbot report the fellowing crash: ================================================================== BUG:
    KASAN: use-after-free in hlist_add_head include/linux/list.h:929 [inline] BUG: KASAN: use-after-free in     enqueue_timer+0x18/0xa4 kernel/time/timer.c:605 Write at addr f9ff000024df6058 by task syz-fuzzer/2256     Pointer tag: [f9], memory tag: [fe] CPU: 1 PID: 2256 Comm: syz-fuzzer Not tainted     6.1.0-rc5-syzkaller-00008- ge01d50cbd6ee #0 Hardware name: linux,dummy-virt (DT) Call trace:
    dump_backtrace.part.0+0xe0/0xf0 arch/arm64/kernel/stacktrace.c:156 dump_backtrace     arch/arm64/kernel/stacktrace.c:162 [inline] show_stack+0x18/0x40 arch/arm64/kernel/stacktrace.c:163
    __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x68/0x84 lib/dump_stack.c:106     print_address_description mm/kasan/report.c:284 [inline] print_report+0x1a8/0x4a0 mm/kasan/report.c:395     kasan_report+0x94/0xb4 mm/kasan/report.c:495 __do_kernel_fault+0x164/0x1e0 arch/arm64/mm/fault.c:320     do_bad_area arch/arm64/mm/fault.c:473 [inline] do_tag_check_fault+0x78/0x8c arch/arm64/mm/fault.c:749     do_mem_abort+0x44/0x94 arch/arm64/mm/fault.c:825 el1_abort+0x40/0x60 arch/arm64/kernel/entry-common.c:367     el1h_64_sync_handler+0xd8/0xe4 arch/arm64/kernel/entry-common.c:427 el1h_64_sync+0x64/0x68     arch/arm64/kernel/entry.S:576 hlist_add_head include/linux/list.h:929 [inline] enqueue_timer+0x18/0xa4     kernel/time/timer.c:605 mod_timer+0x14/0x20 kernel/time/timer.c:1161 mrp_periodic_timer_arm     net/802/mrp.c:614 [inline] mrp_periodic_timer+0xa0/0xc0 net/802/mrp.c:627     call_timer_fn.constprop.0+0x24/0x80 kernel/time/timer.c:1474 expire_timers+0x98/0xc4     kernel/time/timer.c:1519 To fix it, we can introduce a new active flags to make sure the timer will not     restart. (CVE-2022-50697)

  - In the Linux kernel, the following vulnerability has been resolved: crypto: qat - fix DMA transfer     direction When CONFIG_DMA_API_DEBUG is selected, while running the crypto self test on the QAT crypto     algorithms, the function add_dma_entry() reports a warning similar to the one below, saying that     overlapping mappings are not supported. This occurs in tests where the input and the output scatter list     point to the same buffers (i.e. two different scatter lists which point to the same chunks of memory). The     logic that implements the mapping uses the flag DMA_BIDIRECTIONAL for both the input and the output     scatter lists which leads to overlapped write mappings. These are not supported by the DMA layer. Fix by     specifying the correct DMA transfer directions when mapping buffers. For in-place operations where the     input scatter list matches the output scatter list, buffers are mapped once with DMA_BIDIRECTIONAL,     otherwise input buffers are mapped using the flag DMA_TO_DEVICE and output buffers are mapped with     DMA_FROM_DEVICE. Overlapping a read mapping with a write mapping is a valid case in dma-coherent devices     like QAT. The function that frees and unmaps the buffers, qat_alg_free_bufl() has been changed accordingly     to the changes to the mapping function. DMA-API: 4xxx 0000:06:00.0: cacheline tracking EEXIST, overlapping     mappings aren't supported WARNING: CPU: 53 PID: 4362 at kernel/dma/debug.c:570 add_dma_entry+0x1e9/0x270     ... Call Trace: dma_map_page_attrs+0x82/0x2d0 ? preempt_count_add+0x6a/0xa0     qat_alg_sgl_to_bufl+0x45b/0x990 [intel_qat] qat_alg_aead_dec+0x71/0x250 [intel_qat]     crypto_aead_decrypt+0x3d/0x70 test_aead_vec_cfg+0x649/0x810 ? number+0x310/0x3a0 ? vsnprintf+0x2a3/0x550 ?     scnprintf+0x42/0x70 ? valid_sg_divisions.constprop.0+0x86/0xa0 ? test_aead_vec+0xdf/0x120     test_aead_vec+0xdf/0x120 alg_test_aead+0x185/0x400 alg_test+0x3d8/0x500 ?     crypto_acomp_scomp_free_ctx+0x30/0x30 ? __schedule+0x32a/0x12a0 ? ttwu_queue_wakelist+0xbf/0x110 ?
    _raw_spin_unlock_irqrestore+0x23/0x40 ? try_to_wake_up+0x83/0x570 ? _raw_spin_unlock_irqrestore+0x23/0x40     ? __set_cpus_allowed_ptr_locked+0xea/0x1b0 ? crypto_acomp_scomp_free_ctx+0x30/0x30     cryptomgr_test+0x27/0x50 kthread+0xe6/0x110 ? kthread_complete_and_exit+0x20/0x20 ret_from_fork+0x1f/0x30     (CVE-2022-50774)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: cfg80211: Pass the PMK     in binary instead of hex Apparently the hex passphrase mechanism does not work on newer chips/firmware     (e.g. BCM4387). It seems there was a simple way of passing it in binary all along, so use that and avoid     the hexification. OpenBSD has been doing it like this from the beginning, so this should work on all     chips. Also clear the structure before setting the PMK. This was leaking uninitialized stack contents to     the device. (CVE-2023-53715)

  - In the Linux kernel, the following vulnerability has been resolved: posix-timers: Ensure timer ID search-     loop limit is valid posix_timer_add() tries to allocate a posix timer ID by starting from the cached ID     which was stored by the last successful allocation. This is done in a loop searching the ID space for a     free slot one by one. The loop has to terminate when the search wrapped around to the starting point. But     that's racy vs. establishing the starting point. That is read out lockless, which leads to the following     problem: CPU0 CPU1 posix_timer_add() start = sig->posix_timer_id; lock(hash_lock); ... posix_timer_add()     if (++sig->posix_timer_id < 0) start = sig->posix_timer_id; sig->posix_timer_id = 0; So CPU1 can observe a     negative start value, i.e. -1, and the loop break never happens because the condition can never be true:
    if (sig->posix_timer_id == start) break; While this is unlikely to ever turn into an endless loop as the     ID space is huge (INT_MAX), the racy read of the start value caught the attention of KCSAN and Dmitry     unearthed that incorrectness. Rewrite it so that all id operations are under the hash lock.
    (CVE-2023-53728)

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

The remote Ubuntu 24.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-9002-1 advisory.

    It was discovered that the io_uring subsystem in the Linux kernel did not properly handle canceled task     work when processing certain wait operations, leading to the operation being performed in the wrong task     context. A local attacker could possibly use this to cause a denial of service (system crash).
    (CVE-2026-81010)

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - ARM32 architecture;

    - ARM64 architecture;

    - MIPS architecture;

    - OpenRISC architecture;

    - PowerPC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - x86 architecture;

    - Intel NPU Driver;

    - ACPI drivers;

    - Serial ATA and Parallel ATA drivers;

    - Auxiliary display drivers;

    - Ublk userspace block driver;

    - Bluetooth drivers;

    - Character device driver;

    - CPU idle management framework;

    - Hardware crypto device drivers;

    - CXL (Compute Express Link) drivers;

    - ARM SCMI message protocol;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - HSI subsystem;

    - Hardware monitoring drivers;

    - I2C subsystem;

    - I3C subsystem;

    - IIO subsystem;

    - InfiniBand drivers;

    - Input Device core drivers;

    - On-Chip Interconnect management framework;

    - IOMMU subsystem;

    - Multiple devices driver;

    - Media drivers;

    - Fastrpc Driver;

    - Amazon Nitro Secure Module driver;

    - MMC subsystem;

    - MTD block device drivers;

    - Ethernet bonding driver;

    - Network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - Texas Instruments network drivers;

    - MediaTek network drivers;

    - NTB driver;

    - NVDIMM (Non-Volatile Memory Device) drivers;

    - NVME drivers;

    - NVMEM (Non Volatile Memory) drivers;

    - PCI subsystem;

    - Chrome hardware platform drivers;

    - x86 platform drivers;

    - Power supply drivers;

    - RapidIO drivers;

    - Voltage and Current Regulator drivers;

    - S/390 drivers;

    - SCSI subsystem;

    - SLIMbus drivers;

    - NVIDIA Tegra SoC drivers;

    - Realtek RTL8723BS SDIO drivers;

    - TCM subsystem;

    - Trusted Execution Environment drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - USB Device Class drivers;

    - Faraday FOTG210 USB2 dual-role controller driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - Siemens ID Mouse USB driver;

    - IOWarrior USB driver;

    - LD Didactic USB driver;

    - LEGO USB Tower driver;

    - USB Serial drivers;

    - USB Type-C support driver;

    - USB Type-C Port Controller Manager driver;

    - USB Type-C Connector System Software Interface driver;

    - USB over IP driver;

    - VFIO drivers;

    - Framebuffer layer;

    - W1 Dallas's 1-wire bus driver;

    - AFS file system;

    - BTRFS file system;

    - Ceph distributed file system;

    - eCrypt file system;

    - File systems infrastructure;

    - Ext4 file system;

    - F2FS file system;

    - FUSE (File system in Userspace);

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - NTFS3 file system;

    - OCFS2 file system;

    - OrangeFS file system;

    - SMB network file system;

    - UBI file system;

    - Drivers core;

    - Tracing infrastructure;

    - KProbes tracing;

    - Networking core;

    - Netfilter;

    - Sun RPC protocol;

    - IPv6 networking;

    - Bluetooth subsystem;

    - IPv4 networking;

    - IP tunnels definitions;

    - SCTP protocol;

    - User-space API (UAPI);

    - IPC subsystem;

    - Audit subsystem;

    - BPF subsystem;

    - DMA mapping infrastructure;

    - Kernel futex primitives;

    - Scheduler infrastructure;

    - Signal handling mechanism;

    - Memory management;

    - 6LoWPAN network protocol;

    - IEEE 802 network protocols;

    - B.A.T.M.A.N. meshing protocol;

    - Ethernet bridge;

    - CAN network layer;

    - Ceph Core library;

    - Devlink API;

    - HSR network protocol;

    - IEEE802154.4 network protocol;

    - IUCV driver;

    - MAC80211 subsystem;

    - Management Component Transport Protocol (MCTP);

    - MultiProtocol Label Switching driver;

    - Multipath TCP;

    - NetLabel subsystem;

    - Open vSwitch;

    - Packet sockets;

    - RDS protocol;

    - Network traffic control;

    - SMC sockets;

    - Network sockets;

    - VMware vSockets driver;

    - XFRM subsystem;

    - AppArmor security module;

    - Key management;

    - Landlock security;

    - Simplified Mandatory Access Control Kernel framework;

    - ALSA framework;

    - Digigram PCXHR ALSA driver;

    - Wolfson Microelectronics audio codecs;

    - USB sound devices;

    - KVM subsystem; (CVE-2024-40954, CVE-2025-38261, CVE-2025-68296, CVE-2025-68730, CVE-2025-68768,     CVE-2026-23346, CVE-2026-43219, CVE-2026-43240, CVE-2026-43311, CVE-2026-43331, CVE-2026-45930,     CVE-2026-52913, CVE-2026-52930, CVE-2026-52939, CVE-2026-52944, CVE-2026-52948, CVE-2026-52953,     CVE-2026-53080, CVE-2026-53134, CVE-2026-53135, CVE-2026-53140, CVE-2026-53144, CVE-2026-53150,     CVE-2026-53154, CVE-2026-53158, CVE-2026-53168, CVE-2026-53177, CVE-2026-53178, CVE-2026-53179,     CVE-2026-53181, CVE-2026-53190, CVE-2026-53208, CVE-2026-53210, CVE-2026-53213, CVE-2026-53214,     CVE-2026-53218, CVE-2026-53219, CVE-2026-53220, CVE-2026-53227, CVE-2026-53236, CVE-2026-53237,     CVE-2026-53238, CVE-2026-53242, CVE-2026-53245, CVE-2026-53249, CVE-2026-53251, CVE-2026-53252,     CVE-2026-53261, CVE-2026-53263, CVE-2026-53265, CVE-2026-53274, CVE-2026-53331, CVE-2026-53332,     CVE-2026-53336, CVE-2026-53337, CVE-2026-53339, CVE-2026-53343, CVE-2026-53345, CVE-2026-53347,     CVE-2026-53349, CVE-2026-53350, CVE-2026-53352, CVE-2026-53353, CVE-2026-63868, CVE-2026-63871,     CVE-2026-63876, CVE-2026-63877, CVE-2026-63882, CVE-2026-63883, CVE-2026-63890, CVE-2026-63891,     CVE-2026-63892, CVE-2026-63895, CVE-2026-63896, CVE-2026-63897, CVE-2026-63898, CVE-2026-63899,     CVE-2026-63900, CVE-2026-63901, CVE-2026-63902, CVE-2026-63903, CVE-2026-63904, CVE-2026-63905,     CVE-2026-63908, CVE-2026-63928, CVE-2026-63931, CVE-2026-63933, CVE-2026-63934, CVE-2026-63943,     CVE-2026-63949, CVE-2026-63956, CVE-2026-63957, CVE-2026-63958, CVE-2026-63959, CVE-2026-63960,     CVE-2026-63961, CVE-2026-63964, CVE-2026-63967, CVE-2026-63969, CVE-2026-63973, CVE-2026-63990,     CVE-2026-63991, CVE-2026-64001, CVE-2026-64006, CVE-2026-64012, CVE-2026-64014, CVE-2026-64078,     CVE-2026-64090, CVE-2026-64094, CVE-2026-64131, CVE-2026-64233, CVE-2026-64234, CVE-2026-64240,     CVE-2026-64305, CVE-2026-64329, CVE-2026-64330, CVE-2026-64340, CVE-2026-64341, CVE-2026-64342,     CVE-2026-64343, CVE-2026-64344, CVE-2026-64346, CVE-2026-64348, CVE-2026-64352, CVE-2026-64362,     CVE-2026-64363, CVE-2026-64365, CVE-2026-64407, CVE-2026-64421, CVE-2026-64424, CVE-2026-64433,     CVE-2026-64446, CVE-2026-64525, CVE-2026-64527, CVE-2026-64528, CVE-2026-74506, CVE-2026-80590,     CVE-2026-80591, CVE-2026-80593, CVE-2026-80598, CVE-2026-80599, CVE-2026-80600, CVE-2026-80601,     CVE-2026-80603, CVE-2026-80609, CVE-2026-80613, CVE-2026-80619, CVE-2026-80622, CVE-2026-80628,     CVE-2026-80630, CVE-2026-80631, CVE-2026-80634, CVE-2026-80635, CVE-2026-80637, CVE-2026-80644,     CVE-2026-80645, CVE-2026-80646, CVE-2026-80649, CVE-2026-80653, CVE-2026-80662, CVE-2026-80663,     CVE-2026-80664, CVE-2026-80668, CVE-2026-80677, CVE-2026-80678, CVE-2026-80680, CVE-2026-80681,     CVE-2026-80684, CVE-2026-80691, CVE-2026-80692, CVE-2026-80693, CVE-2026-80694, CVE-2026-80700,     CVE-2026-80702, CVE-2026-80706, CVE-2026-80707, CVE-2026-80709, CVE-2026-80710, CVE-2026-80714,     CVE-2026-80716, CVE-2026-80717, CVE-2026-80718, CVE-2026-80722, CVE-2026-80725, CVE-2026-80731,     CVE-2026-80732, CVE-2026-80737, CVE-2026-80738, CVE-2026-80747, CVE-2026-80752, CVE-2026-80754,     CVE-2026-80840, CVE-2026-80928, CVE-2026-80931, CVE-2026-80932, CVE-2026-80933, CVE-2026-80935,     CVE-2026-80937, CVE-2026-80944, CVE-2026-80945, CVE-2026-80947, CVE-2026-80952, CVE-2026-80967,     CVE-2026-80971, CVE-2026-80976, CVE-2026-80977, CVE-2026-80978, CVE-2026-80980, CVE-2026-80982,     CVE-2026-80987, CVE-2026-80989, CVE-2026-80990, CVE-2026-80991, CVE-2026-80992, CVE-2026-80994,     CVE-2026-81000, CVE-2026-81001, CVE-2026-81002, CVE-2026-81003, CVE-2026-81007, CVE-2026-81008,     CVE-2026-81011, CVE-2026-81012, CVE-2026-81016, CVE-2026-81017, CVE-2026-89440, CVE-2026-89441,     CVE-2026-89442, CVE-2026-89443, CVE-2026-89448, CVE-2026-89452, CVE-2026-89456, CVE-2026-89465,     CVE-2026-89466, CVE-2026-89469, CVE-2026-89470, CVE-2026-89471, CVE-2026-89472, CVE-2026-89476,     CVE-2026-89477, CVE-2026-89478, CVE-2026-89479, CVE-2026-89480, CVE-2026-89481, CVE-2026-89482,     CVE-2026-89483, CVE-2026-89485, CVE-2026-89487, CVE-2026-89488, CVE-2026-89489, CVE-2026-89492,     CVE-2026-89493, CVE-2026-89494, CVE-2026-89495, CVE-2026-89497, CVE-2026-89500, CVE-2026-89501,     CVE-2026-89502, CVE-2026-89503, CVE-2026-89504, CVE-2026-89508, CVE-2026-89510, CVE-2026-89511,     CVE-2026-89520, CVE-2026-89524, CVE-2026-89526, CVE-2026-89528, CVE-2026-89530, CVE-2026-89532,     CVE-2026-89533, CVE-2026-89536, CVE-2026-89537, CVE-2026-89538, CVE-2026-89540, CVE-2026-89541,     CVE-2026-89542, CVE-2026-89544, CVE-2026-89545, CVE-2026-89547, CVE-2026-89548, CVE-2026-89549,     CVE-2026-89550, CVE-2026-89551, CVE-2026-89553, CVE-2026-89554, CVE-2026-89555, CVE-2026-89557,     CVE-2026-89559, CVE-2026-89560, CVE-2026-89561, CVE-2026-89562, CVE-2026-89563, CVE-2026-89564,     CVE-2026-89569, CVE-2026-89573, CVE-2026-89574, CVE-2026-89579, CVE-2026-89580, CVE-2026-89583,     CVE-2026-89585, CVE-2026-89586, CVE-2026-89587, CVE-2026-89594, CVE-2026-89596, CVE-2026-89597,     CVE-2026-89599, CVE-2026-89601, CVE-2026-89605, CVE-2026-89606, CVE-2026-89607, CVE-2026-89608,     CVE-2026-89609, CVE-2026-89615, CVE-2026-89616, CVE-2026-89617, CVE-2026-89622, CVE-2026-89626,     CVE-2026-89631, CVE-2026-89633, CVE-2026-89634, CVE-2026-89636, CVE-2026-89637, CVE-2026-89638,     CVE-2026-89640, CVE-2026-89643, CVE-2026-89647, CVE-2026-89648, CVE-2026-89649, CVE-2026-89650,     CVE-2026-89652, CVE-2026-89653, CVE-2026-89654, CVE-2026-89655, CVE-2026-89656, CVE-2026-89657,     CVE-2026-89659, CVE-2026-89662, CVE-2026-89663, CVE-2026-89665, CVE-2026-89669, CVE-2026-89671,     CVE-2026-89672, CVE-2026-89674, CVE-2026-89676, CVE-2026-89680, CVE-2026-89682, CVE-2026-89684,     CVE-2026-89685, CVE-2026-89686, CVE-2026-89690, CVE-2026-89691, CVE-2026-89694, CVE-2026-89696,     CVE-2026-89697, CVE-2026-89699, CVE-2026-89702, CVE-2026-89704, CVE-2026-89705, CVE-2026-89706,     CVE-2026-89707, CVE-2026-89708, CVE-2026-89709, CVE-2026-89711, CVE-2026-89712, CVE-2026-89713,     CVE-2026-89720, CVE-2026-89723, CVE-2026-89724, CVE-2026-89725, CVE-2026-89729, CVE-2026-89731,     CVE-2026-89733, CVE-2026-89736, CVE-2026-89738, CVE-2026-89742, CVE-2026-89743, CVE-2026-89747,     CVE-2026-89750, CVE-2026-89755, CVE-2026-89761, CVE-2026-89762, CVE-2026-89763, CVE-2026-89774,     CVE-2026-89777, CVE-2026-89778, CVE-2026-89779, CVE-2026-89781, CVE-2026-89782, CVE-2026-89783,     CVE-2026-89786, CVE-2026-89788, CVE-2026-89789, CVE-2026-89792, CVE-2026-89793, CVE-2026-89795,     CVE-2026-89799, CVE-2026-89801, CVE-2026-89803, CVE-2026-89806, CVE-2026-89808, CVE-2026-89810,     CVE-2026-89811, CVE-2026-89819, CVE-2026-89823, CVE-2026-89832, CVE-2026-89838, CVE-2026-89840,     CVE-2026-89844, CVE-2026-89846, CVE-2026-89847, CVE-2026-89848, CVE-2026-89849, CVE-2026-89854,     CVE-2026-89856, CVE-2026-89857, CVE-2026-89860, CVE-2026-89861, CVE-2026-89863, CVE-2026-89870,     CVE-2026-89877, CVE-2026-89880, CVE-2026-89883, CVE-2026-89887, CVE-2026-89888, CVE-2026-89890,     CVE-2026-89893, CVE-2026-89894, CVE-2026-89897, CVE-2026-89899, CVE-2026-89902, CVE-2026-89903,     CVE-2026-89908, CVE-2026-89912, CVE-2026-89920, CVE-2026-89922, CVE-2026-89927, CVE-2026-89929,     CVE-2026-89930, CVE-2026-89932, CVE-2026-89938, CVE-2026-89951, CVE-2026-89954, CVE-2026-89957,     CVE-2026-89959, CVE-2026-89960, CVE-2026-89961, CVE-2026-89965, CVE-2026-89968, CVE-2026-89969,     CVE-2026-89970, CVE-2026-89972, CVE-2026-89973, CVE-2026-89979, CVE-2026-89988, CVE-2026-89992,     CVE-2026-89995, CVE-2026-89997, CVE-2026-89998, CVE-2026-89999, CVE-2026-90000, CVE-2026-90002,     CVE-2026-90003, CVE-2026-90007, CVE-2026-90011, CVE-2026-90013, CVE-2026-90016, CVE-2026-90017,     CVE-2026-90018, CVE-2026-90022, CVE-2026-90025, CVE-2026-90026, CVE-2026-90027, CVE-2026-90032,     CVE-2026-90036, CVE-2026-90037, CVE-2026-90041, CVE-2026-90042, CVE-2026-90044, CVE-2026-90045,     CVE-2026-90048, CVE-2026-90049, CVE-2026-90170, CVE-2026-92502, CVE-2026-93221)

Tenable has extracted the preceding description block directly from the Ubuntu 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	Name	Product	Family	Published	Updated	Severity
345244	Linux Distros 未修補弱點：CVE-2026-89709	Nessus	Misc.	9/12/2026	11/11/2026	high
345244	Linux Distros 未修补的漏洞：CVE-2026-89709	Nessus	Misc.	9/12/2026	11/11/2026	high
345244	Linux Distros のパッチ未適用の脆弱性: CVE-2026-89709	Nessus	Misc.	9/12/2026	11/11/2026	high
345244	Linux Distros Unpatched Vulnerability : CVE-2026-89709	Nessus	Misc.	9/12/2026	11/11/2026	high
375672	CentOS Linux 7 [TuxCare] Security Update: bpftool / kernel / kernel-debug / kernel-debug-devel / kernel-devel / etc Multiple Vulnerabilities (CENTOS7:CLSA-2026:1793321383)	Nessus	CentOS Local Security Checks	11/3/2026	11/3/2026	high
377900	Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2026-3402)	Nessus	Amazon Linux Local Security Checks	11/9/2026	11/11/2026	high
376443	Ubuntu 24.04 LTS / 26.04 LTS : Linux kernel vulnerabilities (USN-8959-1)	Nessus	Ubuntu Local Security Checks	11/5/2026	11/5/2026	high
377600	Ubuntu 24.04 LTS : Linux kernel (NVIDIA Tegra) vulnerabilities (USN-9002-1)	Nessus	Ubuntu Local Security Checks	11/9/2026	11/9/2026	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

high

high