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

  - In the Linux kernel, the following vulnerability has been resolved: net: bcmgenet: Use stronger register     read/writes to assure ordering GCC12 appears to be much smarter about its dependency tracking and is aware     that the relaxed variants are just normal loads and stores and this is causing problems like: [     210.074549] ------------[ cut here ]------------ [ 210.079223] NETDEV WATCHDOG: enabcm6e4ei0 (bcmgenet):
    transmit queue 1 timed out [ 210.086717] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:529     dev_watchdog+0x234/0x240 [ 210.095044] Modules linked in: genet(E) nft_fib_inet nft_fib_ipv4 nft_fib_ipv6     nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat] [ 210.146561] ACPI     CPPC: PCC check channel failed for ss: 0. ret=-110 [ 210.146927] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G     E 5.17.0-rc7G12+ #58 [ 210.153226] CPPC Cpufreq:cppc_scale_freq_workfn: failed to read perf counters [     210.161349] Hardware name: Raspberry Pi Foundation Raspberry Pi 4 Model B/Raspberry Pi 4 Model B, BIOS     EDK2-DEV 02/08/2022 [ 210.161353] pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [     210.161358] pc : dev_watchdog+0x234/0x240 [ 210.161364] lr : dev_watchdog+0x234/0x240 [ 210.161368] sp :
    ffff8000080a3a40 [ 210.161370] x29: ffff8000080a3a40 x28: ffffcd425af87000 x27: ffff8000080a3b20 [     210.205150] x26: ffffcd425aa00000 x25: 0000000000000001 x24: ffffcd425af8ec08 [ 210.212321] x23:
    0000000000000100 x22: ffffcd425af87000 x21: ffff55b142688000 [ 210.219491] x20: 0000000000000001 x19:
    ffff55b1426884c8 x18: ffffffffffffffff [ 210.226661] x17: 64656d6974203120 x16: 0000000000000001 x15:
    6d736e617274203a [ 210.233831] x14: 2974656e65676d63 x13: ffffcd4259c300d8 x12: ffffcd425b07d5f0 [     210.241001] x11: 00000000ffffffff x10: ffffcd425b07d5f0 x9 : ffffcd4258bdad9c [ 210.248171] x8 :
    00000000ffffdfff x7 : 000000000000003f x6 : 0000000000000000 [ 210.255341] x5 : 0000000000000000 x4 :
    0000000000000000 x3 : 0000000000001000 [ 210.262511] x2 : 0000000000001000 x1 : 0000000000000005 x0 :
    0000000000000044 [ 210.269682] Call trace: [ 210.272133] dev_watchdog+0x234/0x240 [ 210.275811]     call_timer_fn+0x3c/0x15c [ 210.279489] __run_timers.part.0+0x288/0x310 [ 210.283777]     run_timer_softirq+0x48/0x80 [ 210.287716] __do_softirq+0x128/0x360 [ 210.291392]
    __irq_exit_rcu+0x138/0x140 [ 210.295243] irq_exit_rcu+0x1c/0x30 [ 210.298745] el1_interrupt+0x38/0x54 [     210.302334] el1h_64_irq_handler+0x18/0x24 [ 210.306445] el1h_64_irq+0x7c/0x80 [ 210.309857]     arch_cpu_idle+0x18/0x2c [ 210.313445] default_idle_call+0x4c/0x140 [ 210.317470]     cpuidle_idle_call+0x14c/0x1a0 [ 210.321584] do_idle+0xb0/0x100 [ 210.324737] cpu_startup_entry+0x30/0x8c [     210.328675] secondary_start_kernel+0xe4/0x110 [ 210.333138] __secondary_switched+0x94/0x98 The assumption     when these were relaxed seems to be that device memory would be mapped non reordering, and that other     constructs (spinlocks/etc) would provide the barriers to assure that packet data and in memory     rings/queues were ordered with respect to device register reads/writes. This itself seems a bit sketchy,     but the real problem with GCC12 is that it is moving the actual reads/writes around at will as though they     were independent operations when in truth they are not, but the compiler can't know that. When looking at     the assembly dumps for many of these routines its possible to see very clean, but not strictly in program     order operations occurring as the compiler would be free to do if these weren't actually register     reads/write operations. Its possible to suppress the timeout with a liberal bit of dma_mb()'s sprinkled     around but the device still seems unable to reliably send/receive data. A better plan is to use the safer     readl/writel everywhere. Since this partially reverts an older commit, which notes the use of the relaxed     variants for performance reasons. I would suggest that any performance problems ---truncated---     (CVE-2022-49194)

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: sanitize CAN ID checks in     isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached     with a compliant CAN ID address configuration. The provided address information consisted of CAN ID     0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving. Sanitize the     SFF/EFF CAN ID values before performing the address checks. (CVE-2022-49269)

  - In the Linux kernel, the following vulnerability has been resolved: net/smc: Reset connection when trying     to use SMCRv2 fails. We found a crash when using SMCRv2 with 2 Mellanox ConnectX-4. It can be reproduced     by: - smc_run nginx - smc_run wrk -t 32 -c 500 -d 30 http://<ip>:<port> BUG: kernel NULL pointer     dereference, address: 0000000000000014 #PF: supervisor read access in kernel mode #PF: error_code(0x0000)
    - not-present page PGD 8000000108713067 P4D 8000000108713067 PUD 151127067 PMD 0 Oops: 0000 [#1] PREEMPT     SMP PTI CPU: 4 PID: 2441 Comm: kworker/4:249 Kdump: loaded Tainted: G W E 6.4.0-rc1+ #42 Workqueue:
    smc_hs_wq smc_listen_work [smc] RIP: 0010:smc_clc_send_confirm_accept+0x284/0x580 [smc] RSP:
    0018:ffffb8294b2d7c78 EFLAGS: 00010a06 RAX: ffff8f1873238880 RBX: ffffb8294b2d7dc8 RCX: 0000000000000000     RDX: 00000000000000b4 RSI: 0000000000000001 RDI: 0000000000b40c00 RBP: ffffb8294b2d7db8 R08:
    ffff8f1815c5860c R09: 0000000000000000 R10: 0000000000000400 R11: 0000000000000000 R12: ffff8f1846f56180     R13: ffff8f1815c5860c R14: 0000000000000001 R15: 0000000000000001 FS: 0000000000000000(0000)     GS:ffff8f1aefd00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2:
    0000000000000014 CR3: 00000001027a0001 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000     DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK>     ? mlx5_ib_map_mr_sg+0xa1/0xd0 [mlx5_ib] ? smcr_buf_map_link+0x24b/0x290 [smc] ?
    __smc_buf_create+0x4ee/0x9b0 [smc] smc_clc_send_accept+0x4c/0xb0 [smc] smc_listen_work+0x346/0x650 [smc] ?
    __schedule+0x279/0x820 process_one_work+0x1e5/0x3f0 worker_thread+0x4d/0x2f0 ?
    __pfx_worker_thread+0x10/0x10 kthread+0xe5/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2c/0x50 </TASK>     During the CLC handshake, server sequentially tries available SMCRv2 and SMCRv1 devices in     smc_listen_work(). If an SMCRv2 device is found. SMCv2 based link group and link will be assigned to the     connection. Then assumed that some buffer assignment errors happen later in the CLC handshake, such as RMB     registration failure, server will give up SMCRv2 and try SMCRv1 device instead. But the resources assigned     to the connection won't be reset. When server tries SMCRv1 device, the connection creation process will be     executed again. Since conn->lnk has been assigned when trying SMCRv2, it will not be set to the correct     SMCRv1 link in smcr_lgr_conn_assign_link(). So in such situation, conn->lgr points to correct SMCRv1 link     group but conn->lnk points to the SMCRv2 link mistakenly. Then in smc_clc_send_confirm_accept(),     conn->rmb_desc->mr[link->link_idx] will be accessed. Since the link->link_idx is not correct, the related     MR may not have been initialized, so crash happens. | Try SMCRv2 device first | |-> conn->lgr: assign     existed SMCRv2 link group; | |-> conn->link: assign existed SMCRv2 link (link_idx may be 1 in     SMC_LGR_SYMMETRIC); | |-> sndbuf & RMB creation fails, quit; | | Try SMCRv1 device then | |-> conn->lgr:
    create SMCRv1 link group and assign; | |-> conn->link: keep SMCRv2 link mistakenly; | |-> sndbuf & RMB     creation succeed, only RMB->mr[link_idx = 0] | initialized. | | Then smc_clc_send_confirm_accept()     accesses | conn->rmb_desc->mr[conn->link->link_idx, which is 1], then crash. v This patch tries to fix     this by cleaning conn->lnk before assigning link. In addition, it is better to reset the connection and     clean the resources assigned if trying SMCRv2 failed in buffer creation or registration. (CVE-2023-53382)

  - In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Cap MSIX used to online     CPUs + 1 The irdma driver can use a maximum number of msix vectors equal to num_online_cpus() + 1 and the     kernel warning stack below is shown if that number is exceeded. The kernel throws a warning as the driver     tries to update the affinity hint with a CPU mask greater than the max CPU IDs. Fix this by capping the     MSIX vectors to num_online_cpus() + 1. WARNING: CPU: 7 PID: 23655 at include/linux/cpumask.h:106     irdma_cfg_ceq_vector+0x34c/0x3f0 [irdma] RIP: 0010:irdma_cfg_ceq_vector+0x34c/0x3f0 [irdma] Call Trace:
    irdma_rt_init_hw+0xa62/0x1290 [irdma] ? irdma_alloc_local_mac_entry+0x1a0/0x1a0 [irdma] ?
    __is_kernel_percpu_address+0x63/0x310 ? rcu_read_lock_held_common+0xe/0xb0 ?     irdma_lan_unregister_qset+0x280/0x280 [irdma] ? irdma_request_reset+0x80/0x80 [irdma] ?     ice_get_qos_params+0x84/0x390 [ice] irdma_probe+0xa40/0xfc0 [irdma] ? rcu_read_lock_bh_held+0xd0/0xd0 ?     irdma_remove+0x140/0x140 [irdma] ? rcu_read_lock_sched_held+0x62/0xe0 ? down_write+0x187/0x3d0 ?     auxiliary_match_id+0xf0/0x1a0 ? irdma_remove+0x140/0x140 [irdma] auxiliary_bus_probe+0xa6/0x100
    __driver_probe_device+0x4a4/0xd50 ? __device_attach_driver+0x2c0/0x2c0 driver_probe_device+0x4a/0x110
    __driver_attach+0x1aa/0x350 bus_for_each_dev+0x11d/0x1b0 ? subsys_dev_iter_init+0xe0/0xe0     bus_add_driver+0x3b1/0x610 driver_register+0x18e/0x410 ? 0xffffffffc0b88000 irdma_init_module+0x50/0xaa     [irdma] do_one_initcall+0x103/0x5f0 ? perf_trace_initcall_level+0x420/0x420 ? do_init_module+0x4e/0x700 ?
    __kasan_kmalloc+0x7d/0xa0 ? kmem_cache_alloc_trace+0x188/0x2b0 ? kasan_unpoison+0x21/0x50     do_init_module+0x1d1/0x700 load_module+0x3867/0x5260 ? layout_and_allocate+0x3990/0x3990 ?     rcu_read_lock_held_common+0xe/0xb0 ? rcu_read_lock_sched_held+0x62/0xe0 ? rcu_read_lock_bh_held+0xd0/0xd0     ? __vmalloc_node_range+0x46b/0x890 ? lock_release+0x5c8/0xba0 ? alloc_vm_area+0x120/0x120 ?     selinux_kernel_module_from_file+0x2a5/0x300 ? __inode_security_revalidate+0xf0/0xf0 ?
    __do_sys_init_module+0x1db/0x260 __do_sys_init_module+0x1db/0x260 ? load_module+0x5260/0x5260 ?     do_syscall_64+0x22/0x450 do_syscall_64+0xa5/0x450 entry_SYSCALL_64_after_hwframe+0x66/0xdb     (CVE-2023-53811)

  - In the Linux kernel, the following vulnerability has been resolved: i2c: smbus: fix NULL function pointer     dereference Baruch reported an OOPS when using the designware controller as target only. Target-only modes     break the assumption of one transfer function always being available. Fix this by always checking the     pointer in __i2c_transfer. [wsa: dropped the simplification in core-smbus to avoid theoretical     regressions] (CVE-2024-35984)

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 22.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-8275-1 advisory.

    Stonejiajia, Shir Tamari and Sagi Tzadik discovered that the OverlayFS implementation in the Ubuntu Linux     kernel did not properly perform permission checks in certain situations. A local attacker could possibly     use this to gain elevated privileges. (CVE-2023-2640)

    Shir Tamari and Sagi Tzadik discovered that the OverlayFS implementation in the Ubuntu Linux kernel did     not properly perform permission checks in certain situations. A local attacker could possibly use this to     gain elevated privileges. (CVE-2023-32629)

    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;

    - Block layer subsystem;

    - Drivers core;

    - Bluetooth drivers;

    - DMA engine subsystem;

    - GPU drivers;

    - HID subsystem;

    - Intel Trace Hub HW tracing drivers;

    - IIO ADC drivers;

    - IRQ chip drivers;

    - Modular ISDN driver;

    - LED subsystem;

    - UACCE accelerator framework;

    - Ethernet bonding driver;

    - Network drivers;

    - STMicroelectronics network drivers;

    - Ethernet team driver;

    - NVME drivers;

    - PHY drivers;

    - SLIMbus drivers;

    - W1 Dallas's 1-wire bus driver;

    - Xen hypervisor drivers;

    - BTRFS file system;

    - Ext4 file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NTFS3 file system;

    - SMB network file system;

    - NFC subsystem;

    - BPF subsystem;

    - IRQ subsystem;

    - Memory management;

    - Bluetooth subsystem;

    - CAN network layer;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - L2TP protocol;

    - NET/ROM layer;

    - Network traffic control;

    - SCTP protocol;

    - TLS protocol;

    - XFRM subsystem;

    - Creative Sound Blaster X-Fi driver;

    - USB sound devices; (CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207, CVE-2025-38057,     CVE-2025-38125, CVE-2025-38232, CVE-2025-38408, CVE-2025-38591, CVE-2025-40149, CVE-2025-40164,     CVE-2025-68211, CVE-2025-68340, CVE-2025-68365, CVE-2025-68725, CVE-2025-68817, CVE-2025-71162,     CVE-2025-71163, CVE-2025-71185, CVE-2025-71186, CVE-2025-71188, CVE-2025-71190, CVE-2025-71191,     CVE-2025-71194, CVE-2025-71196, CVE-2025-71197, CVE-2025-71199, CVE-2026-22997, CVE-2026-22998,     CVE-2026-22999, CVE-2026-23001, CVE-2026-23003, CVE-2026-23011, CVE-2026-23026, CVE-2026-23033,     CVE-2026-23037, CVE-2026-23038, CVE-2026-23049, CVE-2026-23056, CVE-2026-23058, CVE-2026-23061,     CVE-2026-23063, CVE-2026-23064, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076,     CVE-2026-23078, CVE-2026-23080, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085, CVE-2026-23087,     CVE-2026-23089, CVE-2026-23090, CVE-2026-23091, CVE-2026-23093, CVE-2026-23095, CVE-2026-23096,     CVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101, CVE-2026-23103, CVE-2026-23105,     CVE-2026-23108, CVE-2026-23112, CVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23124,     CVE-2026-23125, CVE-2026-23128, CVE-2026-23133, CVE-2026-23145, CVE-2026-23146, CVE-2026-23150,     CVE-2026-23164, CVE-2026-23167, CVE-2026-23170, CVE-2026-23209, CVE-2026-23273)

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 20.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-8297-1 advisory.

    Stonejiajia, Shir Tamari and Sagi Tzadik discovered that the OverlayFS implementation in the Ubuntu Linux     kernel did not properly perform permission checks in certain situations. A local attacker could possibly     use this to gain elevated privileges. (CVE-2023-2640)

    Shir Tamari and Sagi Tzadik discovered that the OverlayFS implementation in the Ubuntu Linux kernel did     not properly perform permission checks in certain situations. A local attacker could possibly use this to     gain elevated privileges. (CVE-2023-32629)

    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;

    - Block layer subsystem;

    - Drivers core;

    - Bluetooth drivers;

    - DMA engine subsystem;

    - GPU drivers;

    - HID subsystem;

    - Intel Trace Hub HW tracing drivers;

    - IIO ADC drivers;

    - IRQ chip drivers;

    - Modular ISDN driver;

    - LED subsystem;

    - UACCE accelerator framework;

    - Ethernet bonding driver;

    - Network drivers;

    - STMicroelectronics network drivers;

    - Ethernet team driver;

    - NVME drivers;

    - PHY drivers;

    - SLIMbus drivers;

    - W1 Dallas's 1-wire bus driver;

    - Xen hypervisor drivers;

    - BTRFS file system;

    - Ext4 file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NTFS3 file system;

    - SMB network file system;

    - NFC subsystem;

    - BPF subsystem;

    - IRQ subsystem;

    - Memory management;

    - Bluetooth subsystem;

    - CAN network layer;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - L2TP protocol;

    - NET/ROM layer;

    - Network traffic control;

    - SCTP protocol;

    - TLS protocol;

    - XFRM subsystem;

    - Creative Sound Blaster X-Fi driver;

    - USB sound devices; (CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207, CVE-2025-38057,     CVE-2025-38125, CVE-2025-38232, CVE-2025-38408, CVE-2025-38591, CVE-2025-40149, CVE-2025-40164,     CVE-2025-68211, CVE-2025-68340, CVE-2025-68365, CVE-2025-68725, CVE-2025-68817, CVE-2025-71162,     CVE-2025-71163, CVE-2025-71185, CVE-2025-71186, CVE-2025-71188, CVE-2025-71190, CVE-2025-71191,     CVE-2025-71194, CVE-2025-71196, CVE-2025-71197, CVE-2025-71199, CVE-2026-22997, CVE-2026-22998,     CVE-2026-22999, CVE-2026-23001, CVE-2026-23003, CVE-2026-23011, CVE-2026-23026, CVE-2026-23033,     CVE-2026-23037, CVE-2026-23038, CVE-2026-23049, CVE-2026-23056, CVE-2026-23058, CVE-2026-23061,     CVE-2026-23063, CVE-2026-23064, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076,     CVE-2026-23078, CVE-2026-23080, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085, CVE-2026-23087,     CVE-2026-23089, CVE-2026-23090, CVE-2026-23091, CVE-2026-23093, CVE-2026-23095, CVE-2026-23096,     CVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101, CVE-2026-23103, CVE-2026-23105,     CVE-2026-23108, CVE-2026-23112, CVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23124,     CVE-2026-23125, CVE-2026-23128, CVE-2026-23133, CVE-2026-23145, CVE-2026-23146, CVE-2026-23150,     CVE-2026-23164, CVE-2026-23167, CVE-2026-23170, CVE-2026-23209)

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 Oracle Linux 10 / 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2026-50006 advisory.

    - xfrm: delete x->tunnel as we delete x (Sabrina Dubroca)   {CVE-2025-40215}

Tenable has extracted the preceding description block directly from the Oracle Linux 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 Pro Realtime 22.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-8186-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;

    - Block layer subsystem;

    - Drivers core;

    - Bluetooth drivers;

    - DMA engine subsystem;

    - GPU drivers;

    - HID subsystem;

    - Intel Trace Hub HW tracing drivers;

    - IIO ADC drivers;

    - IRQ chip drivers;

    - Modular ISDN driver;

    - LED subsystem;

    - UACCE accelerator framework;

    - Ethernet bonding driver;

    - Network drivers;

    - STMicroelectronics network drivers;

    - Ethernet team driver;

    - NVME drivers;

    - PHY drivers;

    - SLIMbus drivers;

    - W1 Dallas's 1-wire bus driver;

    - Xen hypervisor drivers;

    - BTRFS file system;

    - Ext4 file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NTFS3 file system;

    - SMB network file system;

    - NFC subsystem;

    - BPF subsystem;

    - IRQ subsystem;

    - Memory management;

    - Bluetooth subsystem;

    - CAN network layer;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - L2TP protocol;

    - NET/ROM layer;

    - Network traffic control;

    - SCTP protocol;

    - TLS protocol;

    - XFRM subsystem;

    - Creative Sound Blaster X-Fi driver;

    - USB sound devices; (CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207, CVE-2025-38057,     CVE-2025-38125, CVE-2025-38232, CVE-2025-38408, CVE-2025-38591, CVE-2025-40149, CVE-2025-40164,     CVE-2025-68211, CVE-2025-68340, CVE-2025-68365, CVE-2025-68725, CVE-2025-68817, CVE-2025-71080,     CVE-2025-71162, CVE-2025-71163, CVE-2025-71185, CVE-2025-71186, CVE-2025-71188, CVE-2025-71190,     CVE-2025-71191, CVE-2025-71194, CVE-2025-71196, CVE-2025-71197, CVE-2025-71199, CVE-2026-22997,     CVE-2026-22998, CVE-2026-22999, CVE-2026-23001, CVE-2026-23003, CVE-2026-23011, CVE-2026-23026,     CVE-2026-23033, CVE-2026-23037, CVE-2026-23038, CVE-2026-23049, CVE-2026-23056, CVE-2026-23058,     CVE-2026-23061, CVE-2026-23063, CVE-2026-23064, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,     CVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,     CVE-2026-23087, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091, CVE-2026-23093, CVE-2026-23095,     CVE-2026-23096, CVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101, CVE-2026-23103,     CVE-2026-23105, CVE-2026-23108, CVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23124,     CVE-2026-23125, CVE-2026-23128, CVE-2026-23133, CVE-2026-23145, CVE-2026-23146, CVE-2026-23150,     CVE-2026-23164, CVE-2026-23167, CVE-2026-23170, CVE-2026-23209)

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 Debian 12 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-6127 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6127-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     February 09, 2026                     https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : linux     CVE ID         : CVE-2023-52658 CVE-2023-53421 CVE-2023-54285 CVE-2024-42079                      CVE-2024-46786 CVE-2024-49968 CVE-2025-21946 CVE-2025-22022                      CVE-2025-22083 CVE-2025-22090 CVE-2025-22107 CVE-2025-22111                      CVE-2025-22121 CVE-2025-37926 CVE-2025-38022 CVE-2025-38104                      CVE-2025-38125 CVE-2025-38129 CVE-2025-38232 CVE-2025-38361                      CVE-2025-38408 CVE-2025-38591 CVE-2025-38718 CVE-2025-39721                      CVE-2025-39871 CVE-2025-40039 CVE-2025-40110 CVE-2025-40149                      CVE-2025-40164 CVE-2025-40215 CVE-2025-68211 CVE-2025-68223                      CVE-2025-68254 CVE-2025-68255 CVE-2025-68256 CVE-2025-68257                      CVE-2025-68258 CVE-2025-68259 CVE-2025-68261 CVE-2025-68263                      CVE-2025-68264 CVE-2025-68266 CVE-2025-68291 CVE-2025-68325                      CVE-2025-68332 CVE-2025-68335 CVE-2025-68336 CVE-2025-68337                      CVE-2025-68340 CVE-2025-68344 CVE-2025-68345 CVE-2025-68346                      CVE-2025-68347 CVE-2025-68349 CVE-2025-68354 CVE-2025-68362                      CVE-2025-68363 CVE-2025-68364 CVE-2025-68365 CVE-2025-68366                      CVE-2025-68367 CVE-2025-68369 CVE-2025-68371 CVE-2025-68372                      CVE-2025-68380 CVE-2025-68724 CVE-2025-68725 CVE-2025-68727                      CVE-2025-68728 CVE-2025-68732 CVE-2025-68733 CVE-2025-68740                      CVE-2025-68742 CVE-2025-68746 CVE-2025-68753 CVE-2025-68757                      CVE-2025-68758 CVE-2025-68759 CVE-2025-68764 CVE-2025-68765                      CVE-2025-68766 CVE-2025-68767 CVE-2025-68769 CVE-2025-68771                      CVE-2025-68772 CVE-2025-68773 CVE-2025-68774 CVE-2025-68776                      CVE-2025-68777 CVE-2025-68778 CVE-2025-68780 CVE-2025-68781                      CVE-2025-68782 CVE-2025-68783 CVE-2025-68785 CVE-2025-68786                      CVE-2025-68787 CVE-2025-68788 CVE-2025-68789 CVE-2025-68795                      CVE-2025-68796 CVE-2025-68797 CVE-2025-68798 CVE-2025-68799                      CVE-2025-68800 CVE-2025-68801 CVE-2025-68803 CVE-2025-68804                      CVE-2025-68806 CVE-2025-68808 CVE-2025-68813 CVE-2025-68814                      CVE-2025-68815 CVE-2025-68816 CVE-2025-68817 CVE-2025-68818                      CVE-2025-68819 CVE-2025-68820 CVE-2025-68821 CVE-2025-71064                      CVE-2025-71066 CVE-2025-71069 CVE-2025-71071 CVE-2025-71075                      CVE-2025-71077 CVE-2025-71078 CVE-2025-71079 CVE-2025-71081                      CVE-2025-71082 CVE-2025-71083 CVE-2025-71084 CVE-2025-71085                      CVE-2025-71086 CVE-2025-71087 CVE-2025-71088 CVE-2025-71091                      CVE-2025-71093 CVE-2025-71094 CVE-2025-71095 CVE-2025-71096                      CVE-2025-71097 CVE-2025-71098 CVE-2025-71102 CVE-2025-71104                      CVE-2025-71105 CVE-2025-71108 CVE-2025-71111 CVE-2025-71112                      CVE-2025-71113 CVE-2025-71114 CVE-2025-71116 CVE-2025-71118                      CVE-2025-71119 CVE-2025-71120 CVE-2025-71121 CVE-2025-71123                      CVE-2025-71125 CVE-2025-71126 CVE-2025-71127 CVE-2025-71130                      CVE-2025-71131 CVE-2025-71132 CVE-2025-71133 CVE-2025-71136                      CVE-2025-71137 CVE-2025-71147 CVE-2025-71149 CVE-2025-71150                      CVE-2025-71154 CVE-2025-71162 CVE-2025-71163 CVE-2025-71180                      CVE-2025-71182 CVE-2025-71183 CVE-2025-71185 CVE-2025-71186                      CVE-2025-71189 CVE-2025-71190 CVE-2025-71191 CVE-2025-71192                      CVE-2025-71194 CVE-2025-71196 CVE-2025-71197 CVE-2025-71199                      CVE-2026-22976 CVE-2026-22977 CVE-2026-22978 CVE-2026-22979                      CVE-2026-22980 CVE-2026-22982 CVE-2026-22984 CVE-2026-22990                      CVE-2026-22991 CVE-2026-22992 CVE-2026-22994 CVE-2026-22997                      CVE-2026-22998 CVE-2026-22999 CVE-2026-23001 CVE-2026-23003                      CVE-2026-23005 CVE-2026-23006 CVE-2026-23010 CVE-2026-23011                      CVE-2026-23019 CVE-2026-23020 CVE-2026-23021 CVE-2026-23025                      CVE-2026-23026 CVE-2026-23030 CVE-2026-23031 CVE-2026-23033                      CVE-2026-23037 CVE-2026-23038 CVE-2026-23047 CVE-2026-23049                      CVE-2026-23054 CVE-2026-23056 CVE-2026-23058 CVE-2026-23060                      CVE-2026-23061 CVE-2026-23063 CVE-2026-23064 CVE-2026-23068                      CVE-2026-23069 CVE-2026-23071 CVE-2026-23073 CVE-2026-23074                      CVE-2026-23075 CVE-2026-23076 CVE-2026-23078 CVE-2026-23080                      CVE-2026-23083 CVE-2026-23084 CVE-2026-23085 CVE-2026-23086                      CVE-2026-23087 CVE-2026-23089 CVE-2026-23090 CVE-2026-23091                      CVE-2026-23093 CVE-2026-23095 CVE-2026-23096 CVE-2026-23097                      CVE-2026-23098 CVE-2026-23099 CVE-2026-23101 CVE-2026-23102                      CVE-2026-23103 CVE-2026-23105 CVE-2026-23107 CVE-2026-23108                      CVE-2026-23110

    Several vulnerabilities have been discovered in the Linux kernel that     may lead to a privilege escalation, denial of service or information     leaks.

    For the oldstable distribution (bookworm), these problems have been fixed     in version 6.1.162-1.

    We recommend that you upgrade your linux packages.

    For the detailed security status of linux please refer to its security     tracker page at:
    https://security-tracker.debian.org/tracker/linux

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian 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 AlmaLinux 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2026:49211 advisory.

    * kernel: ksm: use range-walk function to jump over holes in scan_get_next_rmap_item (CVE-2025-68211)
      * kernel: isofs: validate Rock Ridge CE continuation extent against volume size (CVE-2026-46303)
      * kernel: net: sched: UAF via missing handler for TC_ACT_CONSUMED in tcf_qevent_handle ()


    Bug Fix(es) and Enhancement(s):

      * [DELL 10.2 FEAT] [LATE-ADD] - Include support for Ghostrider PTL mini config SKU with Realtek IC     Solution [almalinux-10.2.z] (JIRA:AlmaLinux-185669)
      * dpll: fix NULL pointer dereference in dpll_msg_add_pin_ref_sync() [almalinux-10.2.z]     (JIRA:AlmaLinux-212063)

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

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

An update of the linux package has been released.

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2026:59723 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * kernel: ksm: use range-walk function to jump over holes in scan_get_next_rmap_item (CVE-2025-68211)

    * kernel: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (CVE-2026-23003)

    * kernel: netfilter: nft_set_pipapo_avx2: don't return non-matching entry on expiry (CVE-2026-43114)

    * kernel: sctp: purge outqueue on stale COOKIE-ECHO handling (CVE-2026-52924)

    * kernel: netfilter: xt_policy: fix strict mode inbound policy matching (CVE-2026-52920)

    * kernel: zram: fix use-after-free in zram_bvec_write_partial() (CVE-2026-53185)

    * kernel: netfilter: require Ethernet MAC header before using eth_hdr() (CVE-2026-53131)

    * kernel: netfilter: conntrack_irc: fix possible out-of-bounds read (CVE-2026-53268)

    * kernel: i2c: stub: Reject I2C block transfers with invalid length (CVE-2026-64191)

    * kernel: netfilter: ipset: fix race between dump and ip_set_list resize (CVE-2026-64189)

    * kernel: Input: synaptics-rmi4 - bound the F3A keymap to the GPIO count (CVE-2026-64277)

    * kernel: Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count (CVE-2026-64276)

    * kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res->rt6 pointer (CVE-2026-74581)

    Bug Fix(es) and Enhancement(s):

    * [RHEL-9.8.z] Intel CWF: CPU is unable to obtain cstate1 on idle system (JIRA:RHEL-166118)

    * ss core dumped when there is an SCTP session [rhel-9.8.z] (JIRA:RHEL-212398)

    * [IBM 9.9 FEAT] zcrypt driver overwrite  function - kernel part [rhel-9.8.z] (JIRA:RHEL-245333)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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 MiracleLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the AXSA:2026-1969:91 advisory.

    * kernel: ksm: use range-walk function to jump over holes in scan_get_next_rmap_item (CVE-2025-68211)
      * kernel: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (CVE-2026-23003)
      * kernel: netfilter: nft_set_pipapo_avx2: don't return non-matching entry on expiry (CVE-2026-43114)
      * kernel: sctp: purge outqueue on stale COOKIE-ECHO handling (CVE-2026-52924)
      * kernel: netfilter: xt_policy: fix strict mode inbound policy matching (CVE-2026-52920)
      * kernel: zram: fix use-after-free in zram_bvec_write_partial() (CVE-2026-53185)
      * kernel: netfilter: require Ethernet MAC header before using eth_hdr() (CVE-2026-53131)
      * kernel: netfilter: conntrack_irc: fix possible out-of-bounds read (CVE-2026-53268)
      * kernel: i2c: stub: Reject I2C block transfers with invalid length (CVE-2026-64191)
      * kernel: netfilter: ipset: fix race between dump and ip_set_list resize (CVE-2026-64189)
      * kernel: Input: synaptics-rmi4 - bound the F3A keymap to the GPIO count (CVE-2026-64277)
      * kernel: Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count (CVE-2026-64276)
      * kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res->rt6 pointer (CVE-2026-74581)

Tenable has extracted the preceding description block directly from the MiracleLinux 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	名称	产品	系列	发布时间	最近更新时间	严重程度
360243	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1783091784)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/1	medium
315743	Ubuntu 22.04 LTS : Linux kernel (Xilinx ZynqMP) vulnerabilities (USN-8275-1)	Nessus	Ubuntu Local Security Checks	2026/5/20	2026/5/21	critical
316637	Ubuntu 20.04 LTS : Linux kernel (GCP) vulnerabilities (USN-8297-1)	Nessus	Ubuntu Local Security Checks	2026/5/25	2026/5/26	critical
284515	Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2026-50006)	Nessus	Oracle Linux Local Security Checks	2026/1/14	2026/2/9	high
307553	Ubuntu Pro Realtime 22.04 LTS : Linux kernel (Real-time) vulnerabilities (USN-8186-1)	Nessus	Ubuntu Local Security Checks	2026/4/20	2026/4/20	high
298404	Debian dsa-6127 : affs-modules-6.1.0-37-4kc-malta-di - security update	Nessus	Debian Local Security Checks	2026/2/9	2026/3/24	high
333107	AlmaLinux 10 : kernel (ALSA-2026:49211)	Nessus	Alma Linux Local Security Checks	2026/8/6	2026/8/6	medium
333941	Photon OS 5.0: Linux PHSA-2026-5.0-92-0926	Nessus	PhotonOS Local Security Checks	2026/8/10	2026/9/19	high
339925	RHEL 9 : kernel (RHSA-2026:59723)	Nessus	Red Hat Local Security Checks	2026/8/26	2026/8/26	medium
363025	MiracleLinux 9 : kernel-5.14.0-687.42.1.el9_8 (AXSA:2026-1969:91)	Nessus	Miracle Linux Local Security Checks	2026/10/5	2026/10/5	medium

检测

插件搜索

medium

critical

critical

high

high

high

medium

high

medium

medium