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

  - ice: change XDP RxQ frag_size from DMA write length to xdp.frame_sz The only user of frag_size field in     XDP RxQ info is bpf_xdp_frags_increase_tail(). It clearly expects whole buff size instead of DMA write     size. Different assumptions in ice driver configuration lead to negative tailroom. This allows to trigger     kernel panic, when using XDP_ADJUST_TAIL_GROW_MULTI_BUFF xskxceiver test and changing packet size to 6912     and the requested offset to a huge value, e.g. XSK_UMEM__MAX_FRAME_SIZE * 100. Due to other quirks of the     ZC configuration in ice, panic is not observed in ZC mode, but tailroom growing still fails when it should     not. Use fill queue buffer truesize instead of DMA write size in XDP RxQ info. Fix ZC mode too by using     the new helper. (CVE-2026-23377)

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

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

  - In the Linux kernel, the following vulnerability has been resolved: CDC-NCM: avoid overflow in sanity     checking A broken device may give an extreme offset like 0xFFF0 and a reasonable length for a fragment. In     the sanity check as formulated now, this will create an integer overflow, defeating the sanity check. Both     offset and offset + len need to be checked in such a manner that no overflow can occur. And those     quantities should be unsigned. (CVE-2022-48938)

  - In the Linux kernel, the following vulnerability has been resolved: pinctrl: devicetree: fix null pointer     dereferencing in pinctrl_dt_to_map Here is the BUG report by KASAN about null pointer dereference: BUG:
    KASAN: null-ptr-deref in strcmp+0x2e/0x50 Read of size 1 at addr 0000000000000000 by task python3/2640     Call Trace: strcmp __of_find_property of_find_property pinctrl_dt_to_map kasprintf() would return NULL     pointer when kmalloc() fail to allocate. So directly return ENOMEM, if kasprintf() return NULL pointer.
    (CVE-2022-49832)

  - In the Linux kernel, the following vulnerability has been resolved: hugetlbfs: fix null-ptr-deref in     hugetlbfs_parse_param() Syzkaller reports a null-ptr-deref bug as follows:
    ====================================================== KASAN: null-ptr-deref in range     [0x0000000000000000-0x0000000000000007] RIP: 0010:hugetlbfs_parse_param+0x1dd/0x8e0     fs/hugetlbfs/inode.c:1380 [...] Call Trace: <TASK> vfs_parse_fs_param fs/fs_context.c:148 [inline]     vfs_parse_fs_param+0x1f9/0x3c0 fs/fs_context.c:129 vfs_parse_fs_string+0xdb/0x170 fs/fs_context.c:191     generic_parse_monolithic+0x16f/0x1f0 fs/fs_context.c:231 do_new_mount fs/namespace.c:3036 [inline]     path_mount+0x12de/0x1e20 fs/namespace.c:3370 do_mount fs/namespace.c:3383 [inline] __do_sys_mount     fs/namespace.c:3591 [inline] __se_sys_mount fs/namespace.c:3568 [inline] __x64_sys_mount+0x27f/0x300     fs/namespace.c:3568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd [...] </TASK>     ====================================================== According to commit vfs: parse: deal with zero     length string value, kernel will set the param->string to null pointer in vfs_parse_fs_string() if fs     string has zero length. Yet the problem is that, hugetlbfs_parse_param() will dereference the     param->string, without checking whether it is a null pointer. To be more specific, if     hugetlbfs_parse_param() parses an illegal mount parameter, such as size=,, kernel will constructs struct     fs_parameter with null pointer in vfs_parse_fs_string(), then passes this struct fs_parameter to     hugetlbfs_parse_param(), which triggers the above null-ptr-deref bug. This patch solves it by adding     sanity check on param->string in hugetlbfs_parse_param(). (CVE-2022-50334)

  - In the Linux kernel, the following vulnerability has been resolved: Input: cyapa - add missing input core     locking to suspend/resume functions Grab input->mutex during suspend/resume functions like it is done in     other input drivers. This fixes the following warning during system suspend/resume cycle on Samsung     Exynos5250-based Snow Chromebook: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 1680 at     drivers/input/input.c:2291 input_device_enabled+0x68/0x6c Modules linked in: ... CPU: 1 PID: 1680 Comm:
    kworker/u4:12 Tainted: G W 6.6.0-rc5-next-20231009 #14109 Hardware name: Samsung Exynos (Flattened Device     Tree) Workqueue: events_unbound async_run_entry_fn unwind_backtrace from show_stack+0x10/0x14 show_stack     from dump_stack_lvl+0x58/0x70 dump_stack_lvl from __warn+0x1a8/0x1cc __warn from     warn_slowpath_fmt+0x18c/0x1b4 warn_slowpath_fmt from input_device_enabled+0x68/0x6c input_device_enabled     from cyapa_gen3_set_power_mode+0x13c/0x1dc cyapa_gen3_set_power_mode from cyapa_reinitialize+0x10c/0x15c     cyapa_reinitialize from cyapa_resume+0x48/0x98 cyapa_resume from dpm_run_callback+0x90/0x298     dpm_run_callback from device_resume+0xb4/0x258 device_resume from async_resume+0x20/0x64 async_resume from     async_run_entry_fn+0x40/0x15c async_run_entry_fn from process_scheduled_works+0xbc/0x6a8     process_scheduled_works from worker_thread+0x188/0x454 worker_thread from kthread+0x108/0x140 kthread from     ret_from_fork+0x14/0x28 Exception stack(0xf1625fb0 to 0xf1625ff8) ... ---[ end trace 0000000000000000 ]---     ... ------------[ cut here ]------------ WARNING: CPU: 1 PID: 1680 at drivers/input/input.c:2291     input_device_enabled+0x68/0x6c Modules linked in: ... CPU: 1 PID: 1680 Comm: kworker/u4:12 Tainted: G W     6.6.0-rc5-next-20231009 #14109 Hardware name: Samsung Exynos (Flattened Device Tree) Workqueue:
    events_unbound async_run_entry_fn unwind_backtrace from show_stack+0x10/0x14 show_stack from     dump_stack_lvl+0x58/0x70 dump_stack_lvl from __warn+0x1a8/0x1cc __warn from warn_slowpath_fmt+0x18c/0x1b4     warn_slowpath_fmt from input_device_enabled+0x68/0x6c input_device_enabled from     cyapa_gen3_set_power_mode+0x13c/0x1dc cyapa_gen3_set_power_mode from cyapa_reinitialize+0x10c/0x15c     cyapa_reinitialize from cyapa_resume+0x48/0x98 cyapa_resume from dpm_run_callback+0x90/0x298     dpm_run_callback from device_resume+0xb4/0x258 device_resume from async_resume+0x20/0x64 async_resume from     async_run_entry_fn+0x40/0x15c async_run_entry_fn from process_scheduled_works+0xbc/0x6a8     process_scheduled_works from worker_thread+0x188/0x454 worker_thread from kthread+0x108/0x140 kthread from     ret_from_fork+0x14/0x28 Exception stack(0xf1625fb0 to 0xf1625ff8) ... ---[ end trace 0000000000000000 ]---     (CVE-2023-52884)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Do not let histogram values     have some modifiers Histogram values can not be strings, stacktraces, graphs, symbols, syscalls, or     grouped in buckets or log. Give an error if a value is set to do so. Note, the histogram code was not     prepared to handle these modifiers for histograms and caused a bug. Mark Rutland reported: # echo     'p:copy_to_user __arch_copy_to_user n=$arg2' >> /sys/kernel/tracing/kprobe_events # echo     'hist:keys=n:vals=hitcount.buckets=8:sort=hitcount' >     /sys/kernel/tracing/events/kprobes/copy_to_user/trigger # cat     /sys/kernel/tracing/events/kprobes/copy_to_user/hist [ 143.694628] Unable to handle kernel NULL pointer     dereference at virtual address 0000000000000000 [ 143.695190] Mem abort info: [ 143.695362] ESR =     0x0000000096000004 [ 143.695604] EC = 0x25: DABT (current EL), IL = 32 bits [ 143.695889] SET = 0, FnV = 0     [ 143.696077] EA = 0, S1PTW = 0 [ 143.696302] FSC = 0x04: level 0 translation fault [ 143.702381] Data     abort info: [ 143.702614] ISV = 0, ISS = 0x00000004 [ 143.702832] CM = 0, WnR = 0 [ 143.703087] user     pgtable: 4k pages, 48-bit VAs, pgdp=00000000448f9000 [ 143.703407] [0000000000000000]     pgd=0000000000000000, p4d=0000000000000000 [ 143.704137] Internal error: Oops: 0000000096000004 [#1]     PREEMPT SMP [ 143.704714] Modules linked in: [ 143.705273] CPU: 0 PID: 133 Comm: cat Not tainted     6.2.0-00003-g6fc512c10a7c #3 [ 143.706138] Hardware name: linux,dummy-virt (DT) [ 143.706723] pstate:
    80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 143.707120] pc :
    hist_field_name.part.0+0x14/0x140 [ 143.707504] lr : hist_field_name.part.0+0x104/0x140 [ 143.707774] sp :
    ffff800008333a30 [ 143.707952] x29: ffff800008333a30 x28: 0000000000000001 x27: 0000000000400cc0 [     143.708429] x26: ffffd7a653b20260 x25: 0000000000000000 x24: ffff10d303ee5800 [ 143.708776] x23:
    ffffd7a6539b27b0 x22: ffff10d303fb8c00 x21: 0000000000000001 [ 143.709127] x20: ffff10d303ec2000 x19:
    0000000000000000 x18: 0000000000000000 [ 143.709478] x17: 0000000000000000 x16: 0000000000000000 x15:
    0000000000000000 [ 143.709824] x14: 0000000000000000 x13: 203a6f666e692072 x12: 6567676972742023 [     143.710179] x11: 0a230a6d6172676f x10: 000000000000002c x9 : ffffd7a6521e018c [ 143.710584] x8 :
    000000000000002c x7 : 7f7f7f7f7f7f7f7f x6 : 000000000000002c [ 143.710915] x5 : ffff10d303b0103e x4 :
    ffffd7a653b20261 x3 : 000000000000003d [ 143.711239] x2 : 0000000000020001 x1 : 0000000000000001 x0 :
    0000000000000000 [ 143.711746] Call trace: [ 143.712115] hist_field_name.part.0+0x14/0x140 [ 143.712642]     hist_field_name.part.0+0x104/0x140 [ 143.712925] hist_field_print+0x28/0x140 [ 143.713125]     event_hist_trigger_print+0x174/0x4d0 [ 143.713348] hist_show+0xf8/0x980 [ 143.713521]     seq_read_iter+0x1bc/0x4b0 [ 143.713711] seq_read+0x8c/0xc4 [ 143.713876] vfs_read+0xc8/0x2a4 [ 143.714043]     ksys_read+0x70/0xfc [ 143.714218] __arm64_sys_read+0x24/0x30 [ 143.714400] invoke_syscall+0x50/0x120 [     143.714587] el0_svc_common.constprop.0+0x4c/0x100 [ 143.714807] do_el0_svc+0x44/0xd0 [ 143.714970]     el0_svc+0x2c/0x84 [ 143.715134] el0t_64_sync_handler+0xbc/0x140 [ 143.715334] el0t_64_sync+0x190/0x194 [     143.715742] Code: a9bd7bfd 910003fd a90153f3 aa0003f3 (f9400000) [ 143.716510] ---[ end trace     0000000000000000 ]--- Segmentation fault (CVE-2023-53093)

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

According to the versions of the kernel packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    crypto: algif_aead - Revert to operating out-of-place(CVE-2026-31431)

    bpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN(CVE-2026-31525)

    can: bcm: fix locking for bcm_op runtime updates(CVE-2026-23362)

    media: mediatek: vcodec: Use spinlock for context list protection lock(CVE-2025-71140)

    smb: client: Don#39;t log plaintext credentials in cifs_set_cifscreds(CVE-2026-23303)

    media: mc, v4l2: serialize REINIT and REQBUFS with req_queue_mutex(CVE-2026-31473)

    regmap: maple: free entry on mas_store_gfp() failure(CVE-2026-23260)

    ACPI: EC: clean up handlers on probe failure in acpi_ec_setup()(CVE-2026-31426)

    apparmor: replace recursive profile removal with iterative approach(CVE-2026-23404)

    tls: Fix race condition in tls_sw_cancel_work_tx()(CVE-2026-23240)

    macvlan: observe an RCU grace period in macvlan_common_newlink() error path(CVE-2026-23273)

    i40e: Fix preempt count leak in napi poll tracepoint(CVE-2026-23313)

    PM: runtime: Fix a race condition related to device removal(CVE-2026-23452)

    net: bridge: fix nd_tbl NULL dereference when IPv6 is disabled(CVE-2026-23381)

    p data-testid='vuln-description'Rejected reason: This CVE ID has been rejected or withdrawn by its     CVE Numbering Authority./pbr/(CVE-2026-23473)

    net: phy: register phy led_triggers during probe to avoid AB-BA deadlock(CVE-2026-23368)

    net: add proper RCU protection to /proc/net/ptype(CVE-2026-23255)

    ice: Fix memory leak in ice_set_ringparam()(CVE-2026-23389)

    ipv6: add NULL checks for idev in SRv6 paths(CVE-2026-23442)

    tracing: Fix potential deadlock in cpu hotplug with osnoise(CVE-2026-31480)

    ice: change XDP RxQ frag_size from DMA write length to xdp.frame_sz(CVE-2026-23377)

    tls: Purge async_hold in tls_decrypt_async_wait()(CVE-2026-23414)

    icmp: fix NULL pointer dereference in icmp_tag_validation()(CVE-2026-23398)

    apparmor: fix memory leak in verify_header(CVE-2026-23403)

    x86/efi: defer freeing of boot services memory(CVE-2026-23352)

    netfilter: nf_tables: always walk all pending catchall elements(CVE-2026-23278)

    nvme: fix admin queue leak on controller reset(CVE-2026-23360)

    media: dvb-net: fix OOB access in ULE extension header tables(CVE-2026-31405)

    netfilter: xt_IDLETIMER: reject rev0 reuse of ALARM timer labels(CVE-2026-23274)

    net: vxlan: fix nd_tbl NULL dereference when IPv6 is disabled(CVE-2026-23293)

    media: dvb-core: fix wrong reinitialization of ringbuffer on reopen(CVE-2026-23253)

    nvme-fc: release admin tagset if init fails(CVE-2026-23261)

    tcp: secure_seq: add back ports to TS offset(CVE-2026-23247)

    KVM: x86/mmu: Drop/zap existing present SPTE even when creating an MMIO SPTE(CVE-2026-23401)

    netfilter: bpf: defer hook memory release until rcu readers are done(CVE-2026-23412)

    apparmor: fix missing bounds check on DEFAULT table in verify_dfa()(CVE-2026-23407)

    ipv6: fix NULL pointer deref in ip6_rt_get_dev_rcu()(CVE-2026-23304)

    ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref(CVE-2026-23145)

    net: gro: fix outer network offset(CVE-2026-23254)

    netfilter: nf_tables: release flowtable after rcu grace period on error(CVE-2026-23392)

    perf: Fix __perf_event_overflow() vs perf_remove_from_context() race(CVE-2026-23271)

    sunrpc: fix cache_request leak in cache_release(CVE-2026-31400)

    RDMA/umad: Reject negative data_len in ib_umad_write(CVE-2026-23243)

    af_unix: Give up GC if MSG_PEEK intervened.(CVE-2026-23394)

    clsact: Fix use-after-free in init/destroy rollback asymmetry(CVE-2026-23413)

    net: ipv6: fix panic when IPv4 route references loopback IPv6 nexthop(CVE-2026-23300)

    apparmor: fix unprivileged local user can do privileged policy management(CVE-2026-23268)

    blktrace: fix __this_cpu_read/write in preemptible context(CVE-2026-23374)

    arm64: io: Extract user memory type in ioremap_prot()(CVE-2026-23346)

    xdp: produce a warning when calculated tailroom is negative(CVE-2026-23343)

    mm: thp: deny THP for files on anonymous inodes(CVE-2026-23375)

    drm/vmwgfx: Return the correct value in vmw_translate_ptr functions(CVE-2026-23317)

    netfilter: nft_set_pipapo: split gc into unlink and reclaim phase(CVE-2026-23351)

    Squashfs: check metadata block offset is within range(CVE-2026-23388)

    net: add xmit recursion limit to tunnel xmit functions(CVE-2026-23276)

    net: sched: avoid qdisc_reset_all_tx_gt() vs dequeue race for lockless qdiscs(CVE-2026-23340)

    scsi: target: Fix recursive locking in __configfs_open_file()(CVE-2026-23292)

    netfilter: nf_tables: unconditionally bump set-gt;nelems before insertion(CVE-2026-23272)

    apparmor: fix differential encoding verification(CVE-2026-23409)

    dmaengine: idxd: Fix leaking event log memory(CVE-2026-31440)

    bpf/bonding: reject vlan+srcmac xmit_hash_policy change when XDP is loaded(CVE-2026-23310)

    apparmor: fix: limit the number of levels of policy namespaces(CVE-2026-23405)

    net: annotate data-races around sk-gt;sk_{data_ready,write_space}(CVE-2026-23302)

    nfnetlink_osf: validate individual option lengths in fingerprints(CVE-2026-23397)

    erofs: add GFP_NOIO in the bio completion if needed(CVE-2026-31467)

    nvme: fix memory allocation in nvme_pr_read_keys()(CVE-2026-23244)

    arm64: Set __nocfi on swsusp_arch_resume()(CVE-2026-23128)

    nf_tables: nft_dynset: fix possible stateful expression memleak in error path(CVE-2026-23399)

    apparmor: fix side-effect bug in match_char() macro usage(CVE-2026-23406)

    NFSD: Defer sub-object cleanup in export put callbacks(CVE-2026-31404)

    audit: add fchmodat2() to change attributes class(CVE-2025-71239)

    netfilter: xt_CT: drop pending enqueued packets on template removal(CVE-2026-23391)

    bpf: Fix a UAF issue in bpf_trampoline_link_cgroup_shim(CVE-2026-23319)

    apparmor: validate DFA start states are in bounds in unpack_pdb(CVE-2026-23269)

    bpf: Fix stack-out-of-bounds write in devmap(CVE-2026-23359)

    spi: fix use-after-free on controller registration failure(CVE-2026-31389)

    apparmor: Fix double free of ns_name in aa_replace_profiles()(CVE-2026-23408)

    spi: fix statistics allocation(CVE-2026-23475)

    smb: client: fix krb5 mount with username option(CVE-2026-31392)

    NFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd(CVE-2026-31403)

    apparmor: fix race between freeing data and fs accessing it(CVE-2026-23411)

    apparmor: fix race on rawdata dereference(CVE-2026-23410)

    sched/deadline: Fix missing ENQUEUE_REPLENISH during PI de-boosting(CVE-2026-23371)

    dmaengine: idxd: Fix memory leak when a wq is reset(CVE-2026-31441)

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

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

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

  - In the Linux kernel, the following vulnerability has been resolved: CDC-NCM: avoid overflow in sanity     checking A broken device may give an extreme offset like 0xFFF0 and a reasonable length for a fragment. In     the sanity check as formulated now, this will create an integer overflow, defeating the sanity check. Both     offset and offset + len need to be checked in such a manner that no overflow can occur. And those     quantities should be unsigned. (CVE-2022-48938)

  - In the Linux kernel, the following vulnerability has been resolved: pinctrl: devicetree: fix null pointer     dereferencing in pinctrl_dt_to_map Here is the BUG report by KASAN about null pointer dereference: BUG:
    KASAN: null-ptr-deref in strcmp+0x2e/0x50 Read of size 1 at addr 0000000000000000 by task python3/2640     Call Trace: strcmp __of_find_property of_find_property pinctrl_dt_to_map kasprintf() would return NULL     pointer when kmalloc() fail to allocate. So directly return ENOMEM, if kasprintf() return NULL pointer.
    (CVE-2022-49832)

  - In the Linux kernel, the following vulnerability has been resolved: hugetlbfs: fix null-ptr-deref in     hugetlbfs_parse_param() Syzkaller reports a null-ptr-deref bug as follows:
    ====================================================== KASAN: null-ptr-deref in range     [0x0000000000000000-0x0000000000000007] RIP: 0010:hugetlbfs_parse_param+0x1dd/0x8e0     fs/hugetlbfs/inode.c:1380 [...] Call Trace: <TASK> vfs_parse_fs_param fs/fs_context.c:148 [inline]     vfs_parse_fs_param+0x1f9/0x3c0 fs/fs_context.c:129 vfs_parse_fs_string+0xdb/0x170 fs/fs_context.c:191     generic_parse_monolithic+0x16f/0x1f0 fs/fs_context.c:231 do_new_mount fs/namespace.c:3036 [inline]     path_mount+0x12de/0x1e20 fs/namespace.c:3370 do_mount fs/namespace.c:3383 [inline] __do_sys_mount     fs/namespace.c:3591 [inline] __se_sys_mount fs/namespace.c:3568 [inline] __x64_sys_mount+0x27f/0x300     fs/namespace.c:3568 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x35/0xb0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd [...] </TASK>     ====================================================== According to commit vfs: parse: deal with zero     length string value, kernel will set the param->string to null pointer in vfs_parse_fs_string() if fs     string has zero length. Yet the problem is that, hugetlbfs_parse_param() will dereference the     param->string, without checking whether it is a null pointer. To be more specific, if     hugetlbfs_parse_param() parses an illegal mount parameter, such as size=,, kernel will constructs struct     fs_parameter with null pointer in vfs_parse_fs_string(), then passes this struct fs_parameter to     hugetlbfs_parse_param(), which triggers the above null-ptr-deref bug. This patch solves it by adding     sanity check on param->string in hugetlbfs_parse_param(). (CVE-2022-50334)

  - In the Linux kernel, the following vulnerability has been resolved: Input: cyapa - add missing input core     locking to suspend/resume functions Grab input->mutex during suspend/resume functions like it is done in     other input drivers. This fixes the following warning during system suspend/resume cycle on Samsung     Exynos5250-based Snow Chromebook: ------------[ cut here ]------------ WARNING: CPU: 1 PID: 1680 at     drivers/input/input.c:2291 input_device_enabled+0x68/0x6c Modules linked in: ... CPU: 1 PID: 1680 Comm:
    kworker/u4:12 Tainted: G W 6.6.0-rc5-next-20231009 #14109 Hardware name: Samsung Exynos (Flattened Device     Tree) Workqueue: events_unbound async_run_entry_fn unwind_backtrace from show_stack+0x10/0x14 show_stack     from dump_stack_lvl+0x58/0x70 dump_stack_lvl from __warn+0x1a8/0x1cc __warn from     warn_slowpath_fmt+0x18c/0x1b4 warn_slowpath_fmt from input_device_enabled+0x68/0x6c input_device_enabled     from cyapa_gen3_set_power_mode+0x13c/0x1dc cyapa_gen3_set_power_mode from cyapa_reinitialize+0x10c/0x15c     cyapa_reinitialize from cyapa_resume+0x48/0x98 cyapa_resume from dpm_run_callback+0x90/0x298     dpm_run_callback from device_resume+0xb4/0x258 device_resume from async_resume+0x20/0x64 async_resume from     async_run_entry_fn+0x40/0x15c async_run_entry_fn from process_scheduled_works+0xbc/0x6a8     process_scheduled_works from worker_thread+0x188/0x454 worker_thread from kthread+0x108/0x140 kthread from     ret_from_fork+0x14/0x28 Exception stack(0xf1625fb0 to 0xf1625ff8) ... ---[ end trace 0000000000000000 ]---     ... ------------[ cut here ]------------ WARNING: CPU: 1 PID: 1680 at drivers/input/input.c:2291     input_device_enabled+0x68/0x6c Modules linked in: ... CPU: 1 PID: 1680 Comm: kworker/u4:12 Tainted: G W     6.6.0-rc5-next-20231009 #14109 Hardware name: Samsung Exynos (Flattened Device Tree) Workqueue:
    events_unbound async_run_entry_fn unwind_backtrace from show_stack+0x10/0x14 show_stack from     dump_stack_lvl+0x58/0x70 dump_stack_lvl from __warn+0x1a8/0x1cc __warn from warn_slowpath_fmt+0x18c/0x1b4     warn_slowpath_fmt from input_device_enabled+0x68/0x6c input_device_enabled from     cyapa_gen3_set_power_mode+0x13c/0x1dc cyapa_gen3_set_power_mode from cyapa_reinitialize+0x10c/0x15c     cyapa_reinitialize from cyapa_resume+0x48/0x98 cyapa_resume from dpm_run_callback+0x90/0x298     dpm_run_callback from device_resume+0xb4/0x258 device_resume from async_resume+0x20/0x64 async_resume from     async_run_entry_fn+0x40/0x15c async_run_entry_fn from process_scheduled_works+0xbc/0x6a8     process_scheduled_works from worker_thread+0x188/0x454 worker_thread from kthread+0x108/0x140 kthread from     ret_from_fork+0x14/0x28 Exception stack(0xf1625fb0 to 0xf1625ff8) ... ---[ end trace 0000000000000000 ]---     (CVE-2023-52884)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Do not let histogram values     have some modifiers Histogram values can not be strings, stacktraces, graphs, symbols, syscalls, or     grouped in buckets or log. Give an error if a value is set to do so. Note, the histogram code was not     prepared to handle these modifiers for histograms and caused a bug. Mark Rutland reported: # echo     'p:copy_to_user __arch_copy_to_user n=$arg2' >> /sys/kernel/tracing/kprobe_events # echo     'hist:keys=n:vals=hitcount.buckets=8:sort=hitcount' >     /sys/kernel/tracing/events/kprobes/copy_to_user/trigger # cat     /sys/kernel/tracing/events/kprobes/copy_to_user/hist [ 143.694628] Unable to handle kernel NULL pointer     dereference at virtual address 0000000000000000 [ 143.695190] Mem abort info: [ 143.695362] ESR =     0x0000000096000004 [ 143.695604] EC = 0x25: DABT (current EL), IL = 32 bits [ 143.695889] SET = 0, FnV = 0     [ 143.696077] EA = 0, S1PTW = 0 [ 143.696302] FSC = 0x04: level 0 translation fault [ 143.702381] Data     abort info: [ 143.702614] ISV = 0, ISS = 0x00000004 [ 143.702832] CM = 0, WnR = 0 [ 143.703087] user     pgtable: 4k pages, 48-bit VAs, pgdp=00000000448f9000 [ 143.703407] [0000000000000000]     pgd=0000000000000000, p4d=0000000000000000 [ 143.704137] Internal error: Oops: 0000000096000004 [#1]     PREEMPT SMP [ 143.704714] Modules linked in: [ 143.705273] CPU: 0 PID: 133 Comm: cat Not tainted     6.2.0-00003-g6fc512c10a7c #3 [ 143.706138] Hardware name: linux,dummy-virt (DT) [ 143.706723] pstate:
    80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 143.707120] pc :
    hist_field_name.part.0+0x14/0x140 [ 143.707504] lr : hist_field_name.part.0+0x104/0x140 [ 143.707774] sp :
    ffff800008333a30 [ 143.707952] x29: ffff800008333a30 x28: 0000000000000001 x27: 0000000000400cc0 [     143.708429] x26: ffffd7a653b20260 x25: 0000000000000000 x24: ffff10d303ee5800 [ 143.708776] x23:
    ffffd7a6539b27b0 x22: ffff10d303fb8c00 x21: 0000000000000001 [ 143.709127] x20: ffff10d303ec2000 x19:
    0000000000000000 x18: 0000000000000000 [ 143.709478] x17: 0000000000000000 x16: 0000000000000000 x15:
    0000000000000000 [ 143.709824] x14: 0000000000000000 x13: 203a6f666e692072 x12: 6567676972742023 [     143.710179] x11: 0a230a6d6172676f x10: 000000000000002c x9 : ffffd7a6521e018c [ 143.710584] x8 :
    000000000000002c x7 : 7f7f7f7f7f7f7f7f x6 : 000000000000002c [ 143.710915] x5 : ffff10d303b0103e x4 :
    ffffd7a653b20261 x3 : 000000000000003d [ 143.711239] x2 : 0000000000020001 x1 : 0000000000000001 x0 :
    0000000000000000 [ 143.711746] Call trace: [ 143.712115] hist_field_name.part.0+0x14/0x140 [ 143.712642]     hist_field_name.part.0+0x104/0x140 [ 143.712925] hist_field_print+0x28/0x140 [ 143.713125]     event_hist_trigger_print+0x174/0x4d0 [ 143.713348] hist_show+0xf8/0x980 [ 143.713521]     seq_read_iter+0x1bc/0x4b0 [ 143.713711] seq_read+0x8c/0xc4 [ 143.713876] vfs_read+0xc8/0x2a4 [ 143.714043]     ksys_read+0x70/0xfc [ 143.714218] __arm64_sys_read+0x24/0x30 [ 143.714400] invoke_syscall+0x50/0x120 [     143.714587] el0_svc_common.constprop.0+0x4c/0x100 [ 143.714807] do_el0_svc+0x44/0xd0 [ 143.714970]     el0_svc+0x2c/0x84 [ 143.715134] el0t_64_sync_handler+0xbc/0x140 [ 143.715334] el0t_64_sync+0x190/0x194 [     143.715742] Code: a9bd7bfd 910003fd a90153f3 aa0003f3 (f9400000) [ 143.716510] ---[ end trace     0000000000000000 ]--- Segmentation fault (CVE-2023-53093)

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
303705	Linux Distros Unpatched Vulnerability : CVE-2026-23377	Nessus	Misc.	3/25/2026	9/23/2026	medium
359751	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1786824415)	Nessus	Rocky Linux Local Security Checks	10/1/2026	10/1/2026	critical
323152	EulerOS 2.0 SP15 : kernel (EulerOS-SA-2026-2444)	Nessus	Huawei Local Security Checks	6/27/2026	6/29/2026	high
323212	EulerOS 2.0 SP15 : kernel (EulerOS-SA-2026-2485)	Nessus	Huawei Local Security Checks	6/27/2026	6/29/2026	high
359602	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1786824415)	Nessus	Alma Linux Local Security Checks	10/1/2026	10/1/2026	critical

Detections

Analytics

Plugins Search

medium

critical

high

high

critical