In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Fix use-after-free in tb_dp_dprx_work The original code relies on cancel_delayed_work() in tb_dp_dprx_stop(), which does not ensure that the delayed work item tunnel->dprx_work has fully completed if it was already running. This leads to use-after-free scenarios where tb_tunnel is deallocated by tb_tunnel_put(), while tunnel->dprx_work remains active and attempts to dereference tb_tunnel in tb_dp_dprx_work(). A typical race condition is illustrated below: CPU 0 | CPU 1 tb_dp_tunnel_active() | tb_deactivate_and_free_tunnel()| tb_dp_dprx_start() tb_tunnel_deactivate() | queue_delayed_work() tb_dp_activate() | tb_dp_dprx_stop() | tb_dp_dprx_work() //delayed worker cancel_delayed_work() | tb_tunnel_put(tunnel); | | tunnel = container_of(...); //UAF | tunnel-> //UAF Replacing cancel_delayed_work() with cancel_delayed_work_sync() is not feasible as it would introduce a deadlock: both tb_dp_dprx_work() and the cleanup path acquire tb->lock, and cancel_delayed_work_sync() would wait indefinitely for the work item that cannot proceed. Instead, implement proper reference counting: - If cancel_delayed_work() returns true (work is pending), we release the reference in the stop function. - If it returns false (work is executing or already completed), the reference is released in delayed work function itself. This ensures the tb_tunnel remains valid during work item execution while preventing memory leaks. This bug was found by static analysis.

The remote CentOS Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the kernel-5.14.0-688.el9 build changelog.

  - In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: fix use-after-     free in nf_tables_addchain() nf_tables_addchain() publishes the chain to table->chains via     list_add_tail_rcu() (in nft_chain_add()) before registering hooks. If nf_tables_register_hook() then     fails, the error path calls nft_chain_del() (list_del_rcu()) followed by nf_tables_chain_destroy() with no     RCU grace period in between. This creates two use-after-free conditions: 1) Control-plane:
    nf_tables_dump_chains() traverses table->chains under rcu_read_lock(). A concurrent dump can still be     walking the chain when the error path frees it. 2) Packet path: for NFPROTO_INET, nf_register_net_hook()     briefly installs the IPv4 hook before IPv6 registration fails. Packets entering nft_do_chain() via the     transient IPv4 hook can still be dereferencing chain->blob_gen_X when the error path frees the chain. Add     synchronize_rcu() between nft_chain_del() and the chain destroy so that all RCU readers -- both dump     threads and in-flight packet evaluation -- have finished before the chain is freed. (CVE-2026-23231)

  - In the Linux kernel, the following vulnerability has been resolved: autofs: fix memory leak of waitqueues     in autofs_catatonic_mode Syzkaller reports a memory leak: BUG: memory leak unreferenced object     0xffff88810b279e00 (size 96): comm syz-executor399, pid 3631, jiffies 4294964921 (age 23.870s) hex dump     (first 32 bytes): 00 00 00 00 00 00 00 00 08 9e 27 0b 81 88 ff ff ..........'..... 08 9e 27 0b 81 88 ff ff     00 00 00 00 00 00 00 00 ..'............. backtrace: [<ffffffff814cfc90>] kmalloc_trace+0x20/0x90     mm/slab_common.c:1046 [<ffffffff81bb75ca>] kmalloc include/linux/slab.h:576 [inline] [<ffffffff81bb75ca>]     autofs_wait+0x3fa/0x9a0 fs/autofs/waitq.c:378 [<ffffffff81bb88a7>] autofs_do_expire_multi+0xa7/0x3e0     fs/autofs/expire.c:593 [<ffffffff81bb8c33>] autofs_expire_multi+0x53/0x80 fs/autofs/expire.c:619     [<ffffffff81bb6972>] autofs_root_ioctl_unlocked+0x322/0x3b0 fs/autofs/root.c:897 [<ffffffff81bb6a95>]     autofs_root_ioctl+0x25/0x30 fs/autofs/root.c:910 [<ffffffff81602a9c>] vfs_ioctl fs/ioctl.c:51 [inline]     [<ffffffff81602a9c>] __do_sys_ioctl fs/ioctl.c:870 [inline] [<ffffffff81602a9c>] __se_sys_ioctl     fs/ioctl.c:856 [inline] [<ffffffff81602a9c>] __x64_sys_ioctl+0xfc/0x140 fs/ioctl.c:856     [<ffffffff84608225>] do_syscall_x64 arch/x86/entry/common.c:50 [inline] [<ffffffff84608225>]     do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80 [<ffffffff84800087>]     entry_SYSCALL_64_after_hwframe+0x63/0xcd autofs_wait_queue structs should be freed if their wait_ctr     becomes zero. Otherwise they will be lost. In this case an AUTOFS_IOC_EXPIRE_MULTI ioctl is done, then a     new waitqueue struct is allocated in autofs_wait(), its initial wait_ctr equals 2. After that     wait_event_killable() is interrupted (it returns -ERESTARTSYS), so that 'wq->name.name == NULL' condition     may be not satisfied. Actually, this condition can be satisfied when autofs_wait_release() or     autofs_catatonic_mode() is called and, what is also important, wait_ctr is decremented in those places.
    Upon the exit of autofs_wait(), wait_ctr is decremented to 1. Then the unmounting process begins: kill_sb     calls autofs_catatonic_mode(), which should have freed the waitqueues, but it only decrements its usage     counter to zero which is not a correct behaviour. edit:imk This description is of course not correct. The     umount performed as a result of an expire is a umount of a mount that has been automounted, it's not the     autofs mount itself. They happen independently, usually after everything mounted within the autofs file     system has been expired away. If everything hasn't been expired away the automount daemon can still exit     leaving mounts in place. But expires done in both cases will result in a notification that calls     autofs_wait_release() with a result status. The problem case is the summary execution of of the automount     daemon. In this case any waiting processes won't be woken up until either they are terminated or the mount     is umounted. end edit: imk So in catatonic mode we should free waitqueues which counter becomes zero.
    edit: imk Initially I was concerned that the calling of autofs_wait_release() and autofs_catatonic_mode()     was not mutually exclusive but that can't be the case (obviously) because the queue entry (or entries) is     removed from the list when either of these two functions are called. Consequently the wait entry will be     freed by only one of these functions or by the woken process in autofs_wait() depending on the order of     the calls. end edit: imk (CVE-2023-54134)

  - In the Linux kernel, the following vulnerability has been resolved: mm: hugetlb: independent PMD page     table shared count The folio refcount may be increased unexpectly through try_get_folio() by caller such     as split_huge_pages. In huge_pmd_unshare(), we use refcount to check whether a pmd page table is shared.
    The check is incorrect if the refcount is increased by the above caller, and this can cause the page table     leaked: BUG: Bad page state in process sh pfn:109324 page: refcount:0 mapcount:0 mapping:0000000000000000     index:0x66 pfn:0x109324 flags: 0x17ffff800000000(node=0|zone=2|lastcpupid=0xfffff) page_type: f2(table)     raw: 017ffff800000000 0000000000000000 0000000000000000 0000000000000000 raw: 0000000000000066     0000000000000000 00000000f2000000 0000000000000000 page dumped because: nonzero mapcount ... CPU: 31 UID:
    0 PID: 7515 Comm: sh Kdump: loaded Tainted: G B 6.13.0-rc2master+ #7 Tainted: [B]=BAD_PAGE Hardware name:
    QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 Call trace: show_stack+0x20/0x38 (C)     dump_stack_lvl+0x80/0xf8 dump_stack+0x18/0x28 bad_page+0x8c/0x130 free_page_is_bad_report+0xa4/0xb0     free_unref_page+0x3cc/0x620 __folio_put+0xf4/0x158 split_huge_pages_all+0x1e0/0x3e8     split_huge_pages_write+0x25c/0x2d8 full_proxy_write+0x64/0xd8 vfs_write+0xcc/0x280 ksys_write+0x70/0x110
    __arm64_sys_write+0x24/0x38 invoke_syscall+0x50/0x120 el0_svc_common.constprop.0+0xc8/0xf0     do_el0_svc+0x24/0x38 el0_svc+0x34/0x128 el0t_64_sync_handler+0xc8/0xd0 el0t_64_sync+0x190/0x198 The issue     may be triggered by damon, offline_page, page_idle, etc, which will increase the refcount of page table.
    1. The page table itself will be discarded after reporting the nonzero mapcount. 2. The HugeTLB page     mapped by the page table miss freeing since we treat the page table as shared and a shared page table will     not be unmapped. Fix it by introducing independent PMD page table shared count. As described by comment,     pt_index/pt_mm/pt_frag_refcount are used for s390 gmap, x86 pgds and powerpc, pt_share_count is used for     x86/arm64/riscv pmds, so we can reuse the field as pt_share_count. (CVE-2024-57883)

  - In the Linux kernel, the following vulnerability has been resolved: net: atm: fix /proc/net/atm/lec     handling /proc/net/atm/lec must ensure safety against dev_lec[] changes. It appears it had dev_put() calls     without prior dev_hold(), leading to imbalance and UAF. (CVE-2025-38180)

  - In the Linux kernel, the following vulnerability has been resolved: HID: intel-thc-hid: intel-thc: Fix     incorrect pointer arithmetic in I2C regs save Improper use of secondary pointer (&dev->i2c_subip_regs)     caused kernel crash and out-of-bounds error: BUG: KASAN: slab-out-of-bounds in
    _regmap_bulk_read+0x449/0x510 Write of size 4 at addr ffff888136005dc0 by task kworker/u33:5/5107 CPU: 3     UID: 0 PID: 5107 Comm: kworker/u33:5 Not tainted 6.16.0+ #3 PREEMPT(voluntary) Workqueue: async     async_run_entry_fn Call Trace: <TASK> dump_stack_lvl+0x76/0xa0 print_report+0xd1/0x660 ?
    __pfx__raw_spin_lock_irqsave+0x10/0x10 ? kasan_complete_mode_report_info+0x26/0x200     kasan_report+0xe1/0x120 ? _regmap_bulk_read+0x449/0x510 ? _regmap_bulk_read+0x449/0x510
    __asan_report_store4_noabort+0x17/0x30 _regmap_bulk_read+0x449/0x510 ? __pfx__regmap_bulk_read+0x10/0x10     regmap_bulk_read+0x270/0x3d0 pio_complete+0x1ee/0x2c0 [intel_thc] ? __pfx_pio_complete+0x10/0x10     [intel_thc] ? __pfx_pio_wait+0x10/0x10 [intel_thc] ? regmap_update_bits_base+0x13b/0x1f0     thc_i2c_subip_pio_read+0x117/0x270 [intel_thc] thc_i2c_subip_regs_save+0xc2/0x140 [intel_thc] ?
    __pfx_thc_i2c_subip_regs_save+0x10/0x10 [intel_thc] [...] The buggy address belongs to the object at     ffff888136005d00 which belongs to the cache kmalloc-rnd-12-192 of size 192 The buggy address is located 0     bytes to the right of allocated 192-byte region [ffff888136005d00, ffff888136005dc0) Replaced with direct     array indexing (&dev->i2c_subip_regs[i]) to ensure safe memory access. (CVE-2025-39818)

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-8048-1 advisory.

    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:

    - ARM64 architecture;

    - MIPS architecture;

    - Nios II architecture;

    - PA-RISC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - Sun Sparc architecture;

    - x86 architecture;

    - Xtensa architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Compute Acceleration Framework;

    - ACPI drivers;

    - Drivers core;

    - Network block device driver;

    - Bluetooth drivers;

    - Bus devices;

    - Hardware random number generator core;

    - Character device driver;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - CPU frequency scaling framework;

    - Hardware crypto device drivers;

    - CXL (Compute Express Link) drivers;

    - Device frequency scaling framework;

    - ARM SCMI message protocol;

    - GPIO subsystem;

    - GPU drivers;

    - Hardware monitoring drivers;

    - HW tracing;

    - InfiniBand drivers;

    - Input Device (Miscellaneous) drivers;

    - IOMMU subsystem;

    - ISDN/mISDN subsystem;

    - Mailbox framework;

    - Multiple devices driver;

    - Media drivers;

    - Fastrpc Driver;

    - PCI Endpoint Test driver;

    - VMware Balloon Driver;

    - MOST (Media Oriented Systems Transport) drivers;

    - Network drivers;

    - Mellanox network drivers;

    - STMicroelectronics network drivers;

    - NVME drivers;

    - PCI subsystem;

    - Performance monitor drivers;

    - Pin controllers subsystem;

    - Mellanox platform drivers;

    - x86 platform drivers;

    - ARM PM domains;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - PWM drivers;

    - Remote Processor subsystem;

    - SCSI subsystem;

    - SPI subsystem;

    - Trusted Execution Environment drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - UFS subsystem;

    - Userspace I/O drivers;

    - Cadence USB3 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - vDPA drivers;

    - Virtio Host (VHOST) subsystem;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - EROFS file system;

    - Ext4 file system;

    - F2FS file system;

    - GFS2 file system;

    - JFS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - File system notification infrastructure;

    - NTFS3 file system;

    - Proc file system;

    - Diskquota system;

    - SMB network file system;

    - BPF subsystem;

    - Mellanox drivers;

    - Memory management;

    - Virtio network driver;

    - Bluetooth subsystem;

    - IP tunnels definitions;

    - io_uring subsystem;

    - Kernel crash support code;

    - Perf events;

    - Kernel futex primitives;

    - PID allocator;

    - Scheduler infrastructure;

    - Syscalls implementation;

    - Timer subsystem;

    - Tracing infrastructure;

    - 9P file system network protocol;

    - Ethernet bridge;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Network traffic control;

    - SCTP protocol;

    - SMC sockets;

    - Sun RPC protocol;

    - TIPC protocol;

    - TLS protocol;

    - VMware vSockets driver;

    - eXpress Data Path;

    - XFRM subsystem;

    - Integrity Measurement Architecture(IMA) framework;

    - ALSA framework;

    - HD-audio driver;

    - AMD SoC Alsa drivers;

    - WCD audio codecs;

    - Intel ASoC drivers;

    - USB sound devices;

    - KVM subsystem; (CVE-2025-40001, CVE-2025-40002, CVE-2025-40003, CVE-2025-40004, CVE-2025-40029,     CVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033, CVE-2025-40034, CVE-2025-40035,     CVE-2025-40036, CVE-2025-40037, CVE-2025-40038, CVE-2025-40039, CVE-2025-40040, CVE-2025-40041,     CVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40045, CVE-2025-40046, CVE-2025-40047,     CVE-2025-40048, CVE-2025-40049, CVE-2025-40050, CVE-2025-40051, CVE-2025-40052, CVE-2025-40053,     CVE-2025-40054, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057, CVE-2025-40058, CVE-2025-40059,     CVE-2025-40060, CVE-2025-40061, CVE-2025-40062, CVE-2025-40063, CVE-2025-40064, CVE-2025-40065,     CVE-2025-40066, CVE-2025-40067, CVE-2025-40068, CVE-2025-40069, CVE-2025-40070, CVE-2025-40071,     CVE-2025-40072, CVE-2025-40073, CVE-2025-40074, CVE-2025-40075, CVE-2025-40076, CVE-2025-40077,     CVE-2025-40078, CVE-2025-40079, CVE-2025-40080, CVE-2025-40081, CVE-2025-40082, CVE-2025-40084,     CVE-2025-40085, CVE-2025-40086, CVE-2025-40087, CVE-2025-40088, CVE-2025-40089, CVE-2025-40091,     CVE-2025-40092, CVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096, CVE-2025-40097,     CVE-2025-40098, CVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40102, CVE-2025-40103,     CVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,     CVE-2025-40113, CVE-2025-40115, CVE-2025-40116, CVE-2025-40117, CVE-2025-40118, CVE-2025-40119,     CVE-2025-40120, CVE-2025-40121, CVE-2025-40122, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,     CVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40130, CVE-2025-40131, CVE-2025-40132,     CVE-2025-40133, CVE-2025-40134, CVE-2025-40135, CVE-2025-40136, CVE-2025-40137, CVE-2025-40138,     CVE-2025-40139, CVE-2025-40140, CVE-2025-40141, CVE-2025-40142, CVE-2025-40143, CVE-2025-40145,     CVE-2025-40146, CVE-2025-40147, CVE-2025-40148, CVE-2025-40149, CVE-2025-40150, CVE-2025-40151,     CVE-2025-40152, CVE-2025-40153, CVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40158,     CVE-2025-40159, CVE-2025-40160, CVE-2025-40161, CVE-2025-40162, CVE-2025-40163, CVE-2025-40164,     CVE-2025-40165, CVE-2025-40166, CVE-2025-40167, CVE-2025-40168, CVE-2025-40169, CVE-2025-40170,     CVE-2025-40171, CVE-2025-40173, CVE-2025-40174, CVE-2025-40175, CVE-2025-40176, CVE-2025-40178,     CVE-2025-40179, CVE-2025-40180, CVE-2025-40181, CVE-2025-40182, CVE-2025-40183, CVE-2025-40184,     CVE-2025-40185, CVE-2025-40186, CVE-2025-40187, CVE-2025-40188, CVE-2025-40189, CVE-2025-40191,     CVE-2025-40192, CVE-2025-40193, CVE-2025-40194, CVE-2025-40195, CVE-2025-40196, CVE-2025-40198,     CVE-2025-40199, CVE-2025-40200, CVE-2025-40201, CVE-2025-40203, CVE-2025-40204, CVE-2025-40205,     CVE-2025-40206, CVE-2025-40207, CVE-2025-40208, CVE-2025-40209, CVE-2025-40210, CVE-2025-40211,     CVE-2025-40212, CVE-2025-40213, CVE-2025-40217, CVE-2025-40218, CVE-2025-40219, CVE-2025-40220,     CVE-2025-40221, CVE-2025-40222, CVE-2025-40223, CVE-2025-40224, CVE-2025-40225, CVE-2025-40226,     CVE-2025-40227, CVE-2025-40228, CVE-2025-40229, CVE-2025-40230, CVE-2025-40231, CVE-2025-40233,     CVE-2025-40234, CVE-2025-40235, CVE-2025-40236, CVE-2025-40237, CVE-2025-40238, CVE-2025-40239,     CVE-2025-40240, CVE-2025-40241, CVE-2025-40242, CVE-2025-40243, CVE-2025-40244, CVE-2025-40245,     CVE-2025-40256, CVE-2025-40267, CVE-2025-40268, CVE-2025-40269, CVE-2025-40270, CVE-2025-40271,     CVE-2025-40272, CVE-2025-40273, CVE-2025-40274, CVE-2025-40275, CVE-2025-40276, CVE-2025-40277,     CVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282, CVE-2025-40283,     CVE-2025-40284, CVE-2025-40285, CVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,     CVE-2025-40291, CVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40295, CVE-2025-40296,     CVE-2025-40297, CVE-2025-40298, CVE-2025-40299, CVE-2025-40301, CVE-2025-40302, CVE-2025-40303,     CVE-2025-40304, CVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308, CVE-2025-40309,     CVE-2025-40310, CVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314, CVE-2025-40315,     CVE-2025-40316, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320, CVE-2025-40321,     CVE-2025-40322, CVE-2025-40323, CVE-2025-40324, CVE-2025-40326, CVE-2025-40327, CVE-2025-40328,     CVE-2025-40329, CVE-2025-40330, CVE-2025-40331, CVE-2025-40332, CVE-2025-40333, CVE-2025-40334,     CVE-2025-40335, CVE-2025-40336, CVE-2025-40337, CVE-2025-40338, CVE-2025-40339, CVE-2025-40340,     CVE-2025-40341, CVE-2025-40342, CVE-2025-40343, CVE-2025-40344, CVE-2025-40346, CVE-2025-40347,     CVE-2025-40349, CVE-2025-40350, CVE-2025-40351, CVE-2025-40352, CVE-2025-40353, CVE-2025-40354,     CVE-2025-40355, CVE-2025-40356, CVE-2025-40357, CVE-2025-40358, CVE-2025-40359, CVE-2025-40360,     CVE-2025-40362, CVE-2025-40363, CVE-2025-68167, CVE-2025-68168, CVE-2025-68169, CVE-2025-68170,     CVE-2025-68171, CVE-2025-68172, CVE-2025-68173, CVE-2025-68174, CVE-2025-68175, CVE-2025-68176,     CVE-2025-68177, CVE-2025-68178, CVE-2025-68179, CVE-2025-68180, CVE-2025-68181, CVE-2025-68182,     CVE-2025-68183, CVE-2025-68184, CVE-2025-68185, CVE-2025-68186, CVE-2025-68187, CVE-2025-68188,     CVE-2025-68189, CVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68193, CVE-2025-68194,     CVE-2025-68196, CVE-2025-68197, CVE-2025-68198, CVE-2025-68199, CVE-2025-68200, CVE-2025-68201,     CVE-2025-68202, CVE-2025-68204, CVE-2025-68205, CVE-2025-68206, CVE-2025-68207, CVE-2025-68208,     CVE-2025-68209, CVE-2025-68210, CVE-2025-68211, CVE-2025-68239, CVE-2025-68240, CVE-2025-68241,     CVE-2025-68242, CVE-2025-68243, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246, CVE-2025-68247,     CVE-2025-68248, CVE-2025-68249, CVE-2025-68250, CVE-2025-68251, CVE-2025-68253, CVE-2025-68309,     CVE-2025-68310, CVE-2025-68311, CVE-2025-68312, CVE-2025-68313, CVE-2025-68314, CVE-2025-68315,     CVE-2025-68317, CVE-2025-68318, CVE-2025-68319, CVE-2025-68320, CVE-2025-68321, CVE-2025-68322,     CVE-2025-68734)

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.

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

    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:

    - ARM64 architecture;

    - MIPS architecture;

    - Nios II architecture;

    - PA-RISC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - Sun Sparc architecture;

    - x86 architecture;

    - Xtensa architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Compute Acceleration Framework;

    - ACPI drivers;

    - Drivers core;

    - Network block device driver;

    - Bluetooth drivers;

    - Bus devices;

    - Hardware random number generator core;

    - Character device driver;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - CPU frequency scaling framework;

    - Hardware crypto device drivers;

    - CXL (Compute Express Link) drivers;

    - Device frequency scaling framework;

    - ARM SCMI message protocol;

    - GPIO subsystem;

    - GPU drivers;

    - Hardware monitoring drivers;

    - HW tracing;

    - InfiniBand drivers;

    - Input Device (Miscellaneous) drivers;

    - IOMMU subsystem;

    - ISDN/mISDN subsystem;

    - Mailbox framework;

    - Multiple devices driver;

    - Media drivers;

    - Fastrpc Driver;

    - PCI Endpoint Test driver;

    - VMware Balloon Driver;

    - MOST (Media Oriented Systems Transport) drivers;

    - Network drivers;

    - Mellanox network drivers;

    - STMicroelectronics network drivers;

    - NVME drivers;

    - PCI subsystem;

    - Performance monitor drivers;

    - Pin controllers subsystem;

    - Mellanox platform drivers;

    - x86 platform drivers;

    - ARM PM domains;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - PWM drivers;

    - Remote Processor subsystem;

    - SCSI subsystem;

    - SPI subsystem;

    - Trusted Execution Environment drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - UFS subsystem;

    - Userspace I/O drivers;

    - Cadence USB3 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - vDPA drivers;

    - Virtio Host (VHOST) subsystem;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - EROFS file system;

    - Ext4 file system;

    - F2FS file system;

    - GFS2 file system;

    - JFS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - File system notification infrastructure;

    - NTFS3 file system;

    - Proc file system;

    - Diskquota system;

    - SMB network file system;

    - BPF subsystem;

    - Mellanox drivers;

    - Memory management;

    - Virtio network driver;

    - Bluetooth subsystem;

    - IP tunnels definitions;

    - io_uring subsystem;

    - Kernel crash support code;

    - Perf events;

    - Kernel futex primitives;

    - PID allocator;

    - Scheduler infrastructure;

    - Syscalls implementation;

    - Timer subsystem;

    - Tracing infrastructure;

    - 9P file system network protocol;

    - Ethernet bridge;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Network traffic control;

    - SCTP protocol;

    - SMC sockets;

    - Sun RPC protocol;

    - TIPC protocol;

    - TLS protocol;

    - VMware vSockets driver;

    - eXpress Data Path;

    - XFRM subsystem;

    - Integrity Measurement Architecture(IMA) framework;

    - ALSA framework;

    - HD-audio driver;

    - AMD SoC Alsa drivers;

    - WCD audio codecs;

    - Intel ASoC drivers;

    - USB sound devices;

    - KVM subsystem; (CVE-2025-40001, CVE-2025-40002, CVE-2025-40003, CVE-2025-40004, CVE-2025-40029,     CVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033, CVE-2025-40034, CVE-2025-40035,     CVE-2025-40036, CVE-2025-40037, CVE-2025-40038, CVE-2025-40039, CVE-2025-40040, CVE-2025-40042,     CVE-2025-40043, CVE-2025-40044, CVE-2025-40045, CVE-2025-40046, CVE-2025-40047, CVE-2025-40048,     CVE-2025-40049, CVE-2025-40050, CVE-2025-40051, CVE-2025-40052, CVE-2025-40053, CVE-2025-40054,     CVE-2025-40055, CVE-2025-40056, CVE-2025-40057, CVE-2025-40058, CVE-2025-40059, CVE-2025-40060,     CVE-2025-40061, CVE-2025-40062, CVE-2025-40063, CVE-2025-40064, CVE-2025-40065, CVE-2025-40066,     CVE-2025-40067, CVE-2025-40068, CVE-2025-40069, CVE-2025-40070, CVE-2025-40071, CVE-2025-40072,     CVE-2025-40073, CVE-2025-40074, CVE-2025-40075, CVE-2025-40076, CVE-2025-40077, CVE-2025-40078,     CVE-2025-40079, CVE-2025-40080, CVE-2025-40081, CVE-2025-40082, CVE-2025-40084, CVE-2025-40085,     CVE-2025-40086, CVE-2025-40087, CVE-2025-40088, CVE-2025-40089, CVE-2025-40091, CVE-2025-40092,     CVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096, CVE-2025-40097, CVE-2025-40098,     CVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40102, CVE-2025-40103, CVE-2025-40104,     CVE-2025-40105, CVE-2025-40106, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112, CVE-2025-40113,     CVE-2025-40115, CVE-2025-40116, CVE-2025-40117, CVE-2025-40118, CVE-2025-40119, CVE-2025-40120,     CVE-2025-40121, CVE-2025-40122, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125, CVE-2025-40126,     CVE-2025-40127, CVE-2025-40129, CVE-2025-40130, CVE-2025-40131, CVE-2025-40132, CVE-2025-40133,     CVE-2025-40134, CVE-2025-40135, CVE-2025-40136, CVE-2025-40137, CVE-2025-40138, CVE-2025-40139,     CVE-2025-40140, CVE-2025-40141, CVE-2025-40142, CVE-2025-40143, CVE-2025-40145, CVE-2025-40146,     CVE-2025-40147, CVE-2025-40148, CVE-2025-40149, CVE-2025-40150, CVE-2025-40152, CVE-2025-40153,     CVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40158, CVE-2025-40159, CVE-2025-40160,     CVE-2025-40161, CVE-2025-40162, CVE-2025-40163, CVE-2025-40164, CVE-2025-40165, CVE-2025-40166,     CVE-2025-40167, CVE-2025-40168, CVE-2025-40169, CVE-2025-40170, CVE-2025-40171, CVE-2025-40172,     CVE-2025-40173, CVE-2025-40174, CVE-2025-40175, CVE-2025-40176, CVE-2025-40177, CVE-2025-40178,     CVE-2025-40179, CVE-2025-40180, CVE-2025-40181, CVE-2025-40182, CVE-2025-40183, CVE-2025-40184,     CVE-2025-40185, CVE-2025-40186, CVE-2025-40187, CVE-2025-40188, CVE-2025-40189, CVE-2025-40191,     CVE-2025-40192, CVE-2025-40193, CVE-2025-40194, CVE-2025-40195, CVE-2025-40196, CVE-2025-40198,     CVE-2025-40199, CVE-2025-40200, CVE-2025-40201, CVE-2025-40203, CVE-2025-40204, CVE-2025-40205,     CVE-2025-40206, CVE-2025-40207, CVE-2025-40208, CVE-2025-40209, CVE-2025-40210, CVE-2025-40211,     CVE-2025-40212, CVE-2025-40213, CVE-2025-40217, CVE-2025-40218, CVE-2025-40219, CVE-2025-40220,     CVE-2025-40221, CVE-2025-40222, CVE-2025-40223, CVE-2025-40224, CVE-2025-40225, CVE-2025-40226,     CVE-2025-40227, CVE-2025-40228, CVE-2025-40229, CVE-2025-40230, CVE-2025-40231, CVE-2025-40233,     CVE-2025-40234, CVE-2025-40235, CVE-2025-40236, CVE-2025-40237, CVE-2025-40238, CVE-2025-40239,     CVE-2025-40240, CVE-2025-40241, CVE-2025-40242, CVE-2025-40243, CVE-2025-40244, CVE-2025-40245,     CVE-2025-40256, CVE-2025-40267, CVE-2025-40268, CVE-2025-40269, CVE-2025-40270, CVE-2025-40271,     CVE-2025-40272, CVE-2025-40273, CVE-2025-40274, CVE-2025-40275, CVE-2025-40276, CVE-2025-40277,     CVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282, CVE-2025-40283,     CVE-2025-40284, CVE-2025-40285, CVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,     CVE-2025-40291, CVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40295, CVE-2025-40296,     CVE-2025-40297, CVE-2025-40298, CVE-2025-40299, CVE-2025-40301, CVE-2025-40302, CVE-2025-40303,     CVE-2025-40304, CVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308, CVE-2025-40309,     CVE-2025-40310, CVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314, CVE-2025-40315,     CVE-2025-40316, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320, CVE-2025-40321,     CVE-2025-40322, CVE-2025-40323, CVE-2025-40324, CVE-2025-40326, CVE-2025-40327, CVE-2025-40328,     CVE-2025-40329, CVE-2025-40330, CVE-2025-40331, CVE-2025-40332, CVE-2025-40333, CVE-2025-40334,     CVE-2025-40335, CVE-2025-40336, CVE-2025-40337, CVE-2025-40338, CVE-2025-40339, CVE-2025-40340,     CVE-2025-40341, CVE-2025-40342, CVE-2025-40343, CVE-2025-40344, CVE-2025-40346, CVE-2025-40347,     CVE-2025-40349, CVE-2025-40350, CVE-2025-40351, CVE-2025-40352, CVE-2025-40353, CVE-2025-40354,     CVE-2025-40355, CVE-2025-40356, CVE-2025-40357, CVE-2025-40358, CVE-2025-40359, CVE-2025-40360,     CVE-2025-40362, CVE-2025-40363, CVE-2025-68167, CVE-2025-68168, CVE-2025-68169, CVE-2025-68170,     CVE-2025-68171, CVE-2025-68172, CVE-2025-68173, CVE-2025-68174, CVE-2025-68175, CVE-2025-68176,     CVE-2025-68177, CVE-2025-68178, CVE-2025-68179, CVE-2025-68180, CVE-2025-68181, CVE-2025-68182,     CVE-2025-68183, CVE-2025-68184, CVE-2025-68185, CVE-2025-68186, CVE-2025-68187, CVE-2025-68188,     CVE-2025-68189, CVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68193, CVE-2025-68194,     CVE-2025-68196, CVE-2025-68197, CVE-2025-68198, CVE-2025-68199, CVE-2025-68200, CVE-2025-68201,     CVE-2025-68202, CVE-2025-68204, CVE-2025-68205, CVE-2025-68206, CVE-2025-68207, CVE-2025-68208,     CVE-2025-68209, CVE-2025-68210, CVE-2025-68211, CVE-2025-68239, CVE-2025-68240, CVE-2025-68241,     CVE-2025-68242, CVE-2025-68243, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246, CVE-2025-68247,     CVE-2025-68248, CVE-2025-68249, CVE-2025-68250, CVE-2025-68251, CVE-2025-68253, CVE-2025-68309,     CVE-2025-68310, CVE-2025-68311, CVE-2025-68312, CVE-2025-68313, CVE-2025-68314, CVE-2025-68315,     CVE-2025-68316, CVE-2025-68317, CVE-2025-68318, CVE-2025-68319, CVE-2025-68320, CVE-2025-68321,     CVE-2025-68322, CVE-2025-68734)

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.

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

    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:

    - ARM64 architecture;

    - MIPS architecture;

    - Nios II architecture;

    - PA-RISC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - Sun Sparc architecture;

    - x86 architecture;

    - Xtensa architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Compute Acceleration Framework;

    - ACPI drivers;

    - Drivers core;

    - Network block device driver;

    - Bluetooth drivers;

    - Bus devices;

    - Hardware random number generator core;

    - Character device driver;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - CPU frequency scaling framework;

    - Hardware crypto device drivers;

    - CXL (Compute Express Link) drivers;

    - Device frequency scaling framework;

    - ARM SCMI message protocol;

    - GPIO subsystem;

    - GPU drivers;

    - Hardware monitoring drivers;

    - HW tracing;

    - InfiniBand drivers;

    - Input Device (Miscellaneous) drivers;

    - IOMMU subsystem;

    - ISDN/mISDN subsystem;

    - Mailbox framework;

    - Multiple devices driver;

    - Media drivers;

    - Fastrpc Driver;

    - PCI Endpoint Test driver;

    - VMware Balloon Driver;

    - MOST (Media Oriented Systems Transport) drivers;

    - Network drivers;

    - Mellanox network drivers;

    - STMicroelectronics network drivers;

    - NVME drivers;

    - PCI subsystem;

    - Performance monitor drivers;

    - Pin controllers subsystem;

    - Mellanox platform drivers;

    - x86 platform drivers;

    - ARM PM domains;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - PWM drivers;

    - Remote Processor subsystem;

    - SCSI subsystem;

    - SPI subsystem;

    - Trusted Execution Environment drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - UFS subsystem;

    - Userspace I/O drivers;

    - Cadence USB3 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - vDPA drivers;

    - Virtio Host (VHOST) subsystem;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - EROFS file system;

    - Ext4 file system;

    - F2FS file system;

    - GFS2 file system;

    - JFS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - File system notification infrastructure;

    - NTFS3 file system;

    - Proc file system;

    - Diskquota system;

    - SMB network file system;

    - BPF subsystem;

    - Mellanox drivers;

    - Memory management;

    - Virtio network driver;

    - Bluetooth subsystem;

    - IP tunnels definitions;

    - io_uring subsystem;

    - Kernel crash support code;

    - Perf events;

    - Kernel futex primitives;

    - PID allocator;

    - Scheduler infrastructure;

    - Syscalls implementation;

    - Timer subsystem;

    - Tracing infrastructure;

    - 9P file system network protocol;

    - Ethernet bridge;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Network traffic control;

    - SCTP protocol;

    - SMC sockets;

    - Sun RPC protocol;

    - TIPC protocol;

    - TLS protocol;

    - VMware vSockets driver;

    - eXpress Data Path;

    - XFRM subsystem;

    - Integrity Measurement Architecture(IMA) framework;

    - ALSA framework;

    - HD-audio driver;

    - AMD SoC Alsa drivers;

    - WCD audio codecs;

    - Intel ASoC drivers;

    - USB sound devices;

    - KVM subsystem; (CVE-2025-40001, CVE-2025-40002, CVE-2025-40003, CVE-2025-40004, CVE-2025-40029,     CVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033, CVE-2025-40034, CVE-2025-40035,     CVE-2025-40036, CVE-2025-40037, CVE-2025-40038, CVE-2025-40039, CVE-2025-40040, CVE-2025-40042,     CVE-2025-40043, CVE-2025-40044, CVE-2025-40045, CVE-2025-40046, CVE-2025-40047, CVE-2025-40048,     CVE-2025-40049, CVE-2025-40050, CVE-2025-40051, CVE-2025-40052, CVE-2025-40053, CVE-2025-40054,     CVE-2025-40055, CVE-2025-40056, CVE-2025-40057, CVE-2025-40058, CVE-2025-40059, CVE-2025-40060,     CVE-2025-40061, CVE-2025-40062, CVE-2025-40063, CVE-2025-40064, CVE-2025-40065, CVE-2025-40066,     CVE-2025-40067, CVE-2025-40068, CVE-2025-40069, CVE-2025-40070, CVE-2025-40071, CVE-2025-40072,     CVE-2025-40073, CVE-2025-40074, CVE-2025-40075, CVE-2025-40076, CVE-2025-40077, CVE-2025-40078,     CVE-2025-40079, CVE-2025-40080, CVE-2025-40081, CVE-2025-40082, CVE-2025-40084, CVE-2025-40085,     CVE-2025-40086, CVE-2025-40087, CVE-2025-40088, CVE-2025-40089, CVE-2025-40091, CVE-2025-40092,     CVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096, CVE-2025-40097, CVE-2025-40098,     CVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40102, CVE-2025-40103, CVE-2025-40104,     CVE-2025-40105, CVE-2025-40106, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112, CVE-2025-40113,     CVE-2025-40115, CVE-2025-40116, CVE-2025-40117, CVE-2025-40118, CVE-2025-40119, CVE-2025-40120,     CVE-2025-40121, CVE-2025-40122, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125, CVE-2025-40126,     CVE-2025-40127, CVE-2025-40129, CVE-2025-40130, CVE-2025-40131, CVE-2025-40132, CVE-2025-40133,     CVE-2025-40134, CVE-2025-40135, CVE-2025-40136, CVE-2025-40137, CVE-2025-40138, CVE-2025-40139,     CVE-2025-40140, CVE-2025-40141, CVE-2025-40142, CVE-2025-40143, CVE-2025-40145, CVE-2025-40146,     CVE-2025-40147, CVE-2025-40148, CVE-2025-40149, CVE-2025-40150, CVE-2025-40152, CVE-2025-40153,     CVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40158, CVE-2025-40159, CVE-2025-40160,     CVE-2025-40161, CVE-2025-40162, CVE-2025-40163, CVE-2025-40164, CVE-2025-40165, CVE-2025-40166,     CVE-2025-40167, CVE-2025-40168, CVE-2025-40169, CVE-2025-40170, CVE-2025-40171, CVE-2025-40172,     CVE-2025-40173, CVE-2025-40174, CVE-2025-40175, CVE-2025-40176, CVE-2025-40177, CVE-2025-40178,     CVE-2025-40179, CVE-2025-40180, CVE-2025-40182, CVE-2025-40183, CVE-2025-40184, CVE-2025-40185,     CVE-2025-40186, CVE-2025-40187, CVE-2025-40188, CVE-2025-40189, CVE-2025-40191, CVE-2025-40192,     CVE-2025-40193, CVE-2025-40194, CVE-2025-40195, CVE-2025-40196, CVE-2025-40198, CVE-2025-40199,     CVE-2025-40200, CVE-2025-40201, CVE-2025-40203, CVE-2025-40204, CVE-2025-40205, CVE-2025-40206,     CVE-2025-40207, CVE-2025-40208, CVE-2025-40209, CVE-2025-40210, CVE-2025-40211, CVE-2025-40212,     CVE-2025-40213, CVE-2025-40217, CVE-2025-40218, CVE-2025-40219, CVE-2025-40220, CVE-2025-40221,     CVE-2025-40222, CVE-2025-40223, CVE-2025-40224, CVE-2025-40225, CVE-2025-40226, CVE-2025-40227,     CVE-2025-40228, CVE-2025-40229, CVE-2025-40230, CVE-2025-40231, CVE-2025-40233, CVE-2025-40234,     CVE-2025-40235, CVE-2025-40236, CVE-2025-40237, CVE-2025-40238, CVE-2025-40239, CVE-2025-40240,     CVE-2025-40241, CVE-2025-40242, CVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40256,     CVE-2025-40267, CVE-2025-40268, CVE-2025-40269, CVE-2025-40270, CVE-2025-40271, CVE-2025-40272,     CVE-2025-40273, CVE-2025-40274, CVE-2025-40275, CVE-2025-40276, CVE-2025-40277, CVE-2025-40278,     CVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282, CVE-2025-40283, CVE-2025-40284,     CVE-2025-40285, CVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289, CVE-2025-40291,     CVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40295, CVE-2025-40296, CVE-2025-40297,     CVE-2025-40298, CVE-2025-40299, CVE-2025-40301, CVE-2025-40302, CVE-2025-40303, CVE-2025-40304,     CVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,     CVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40316,     CVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320, CVE-2025-40321, CVE-2025-40322,     CVE-2025-40323, CVE-2025-40324, CVE-2025-40326, CVE-2025-40327, CVE-2025-40328, CVE-2025-40329,     CVE-2025-40330, CVE-2025-40331, CVE-2025-40332, CVE-2025-40333, CVE-2025-40334, CVE-2025-40335,     CVE-2025-40336, CVE-2025-40337, CVE-2025-40338, CVE-2025-40339, CVE-2025-40340, CVE-2025-40341,     CVE-2025-40342, CVE-2025-40343, CVE-2025-40344, CVE-2025-40346, CVE-2025-40347, CVE-2025-40349,     CVE-2025-40350, CVE-2025-40351, CVE-2025-40352, CVE-2025-40353, CVE-2025-40354, CVE-2025-40355,     CVE-2025-40356, CVE-2025-40357, CVE-2025-40358, CVE-2025-40359, CVE-2025-40360, CVE-2025-40362,     CVE-2025-40363, CVE-2025-68167, CVE-2025-68168, CVE-2025-68169, CVE-2025-68170, CVE-2025-68171,     CVE-2025-68172, CVE-2025-68173, CVE-2025-68174, CVE-2025-68175, CVE-2025-68176, CVE-2025-68177,     CVE-2025-68178, CVE-2025-68179, CVE-2025-68180, CVE-2025-68181, CVE-2025-68182, CVE-2025-68183,     CVE-2025-68184, CVE-2025-68185, CVE-2025-68186, CVE-2025-68187, CVE-2025-68188, CVE-2025-68189,     CVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68193, CVE-2025-68194, CVE-2025-68196,     CVE-2025-68197, CVE-2025-68198, CVE-2025-68199, CVE-2025-68200, CVE-2025-68201, CVE-2025-68202,     CVE-2025-68204, CVE-2025-68205, CVE-2025-68206, CVE-2025-68207, CVE-2025-68208, CVE-2025-68209,     CVE-2025-68210, CVE-2025-68211, CVE-2025-68239, CVE-2025-68240, CVE-2025-68241, CVE-2025-68242,     CVE-2025-68243, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246, CVE-2025-68247, CVE-2025-68248,     CVE-2025-68249, CVE-2025-68250, CVE-2025-68251, CVE-2025-68253, CVE-2025-68309, CVE-2025-68310,     CVE-2025-68311, CVE-2025-68312, CVE-2025-68313, CVE-2025-68314, CVE-2025-68315, CVE-2025-68316,     CVE-2025-68317, CVE-2025-68318, CVE-2025-68319, CVE-2025-68320, CVE-2025-68321, CVE-2025-68322,     CVE-2025-68734)

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.

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

  - thunderbolt: Fix use-after-free in tb_dp_dprx_work The original code relies on cancel_delayed_work() in     tb_dp_dprx_stop(), which does not ensure that the delayed work item tunnel->dprx_work has fully completed     if it was already running. This leads to use-after-free scenarios where tb_tunnel is deallocated by     tb_tunnel_put(), while tunnel->dprx_work remains active and attempts to dereference tb_tunnel in     tb_dp_dprx_work(). A typical race condition is illustrated below: CPU 0 | CPU 1 tb_dp_tunnel_active() |     tb_deactivate_and_free_tunnel()| tb_dp_dprx_start() tb_tunnel_deactivate() | queue_delayed_work()     tb_dp_activate() | tb_dp_dprx_stop() | tb_dp_dprx_work() //delayed worker cancel_delayed_work() |     tb_tunnel_put(tunnel); | | tunnel = container_of(...); //UAF | tunnel-> //UAF Replacing     cancel_delayed_work() with cancel_delayed_work_sync() is not feasible as it would introduce a deadlock:
    both tb_dp_dprx_work() and the cleanup path acquire tb->lock, and cancel_delayed_work_sync() would wait     indefinitely for the work item that cannot proceed. Instead, implement proper reference counting: - If     cancel_delayed_work() returns true (work is pending), we release the reference in the stop function. - If     it returns false (work is executing or already completed), the reference is released in delayed work     function itself. This ensures the tb_tunnel remains valid during work item execution while preventing     memory leaks. This bug was found by static analysis. (CVE-2025-40002)

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

ID	Name	Product	Family	Severity
304415	CentOS 9 : kernel-5.14.0-688.el9	Nessus	CentOS Local Security Checks	high
299491	Ubuntu 24.04 LTS : Linux kernel (OEM) vulnerabilities (USN-8048-1)	Nessus	Ubuntu Local Security Checks	critical
298897	Ubuntu 25.10 : Linux kernel vulnerabilities (USN-8029-1)	Nessus	Ubuntu Local Security Checks	critical
298894	Ubuntu 25.10 : Linux kernel (GCP) vulnerabilities (USN-8030-1)	Nessus	Ubuntu Local Security Checks	critical
271678	Linux Distros Unpatched Vulnerability : CVE-2025-40002	Nessus	Misc.	medium

Detections

Analytics

CVE-2025-40002

medium

Tenable Plugins

high

critical

critical

critical

medium