In the Linux kernel, the following vulnerability has been resolved: smb: client: fix heap overflow in DACL owner/group rewrite When id_mode_to_cifs_acl rewrites an existing DACL, it allocates a buffer sized according to the on-disk DACL length reported by dacl_ptr->size. However, replace_sids_and_copy_aces may rewrite each ACE with a new owner/group SID obtained from the cifs.idmap upcall. Those SIDs can have up to SID_MAX_SUB_AUTHORITIES (15) sub-authorities, making each ACE up to 76 bytes (sizeof(struct smb_ace)). If the original DACL contains short SIDs (e.g., 1 sub-authority) while the replacement SIDs are long, the rewritten ACEs overflow the allocation. Fix this by always budgeting for worst-case SID expansion: allocate sizeof(struct smb_acl) plus num_aces * sizeof(struct smb_ace), which covers the smb_acl header and room for every ACE at maximum SID size. This replaces the previous split logic that used dacl_ptr->size for cifsacl mounts but num_aces * sizeof(struct smb_ace) for mode_from_sid mounts: both paths can trigger the same rewrite and need the same headroom. KASAN reports this as: BUG: KASAN: slab-out-of-bounds in build_sec_desc+0x1e8a/0x2680 [cifs] Write of size 4 at addr ffff8881a5e25374 by task chown/5298 ... The buggy address is located 0 bytes to the right of allocated 884-byte region [ffff8881a5e25000, ffff8881a5e25374)

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - In the Linux kernel, the following vulnerability has been resolved: smb: client: fix heap overflow in DACL
    owner/group rewrite When id_mode_to_cifs_acl rewrites an existing DACL, it allocates a buffer sized
    according to the on-disk DACL length reported by dacl_ptr->size. However, replace_sids_and_copy_aces may
    rewrite each ACE with a new owner/group SID obtained from the cifs.idmap upcall. Those SIDs can have up to
    SID_MAX_SUB_AUTHORITIES (15) sub-authorities, making each ACE up to 76 bytes (sizeof(struct smb_ace)). If
    the original DACL contains short SIDs (e.g., 1 sub-authority) while the replacement SIDs are long, the
    rewritten ACEs overflow the allocation. Fix this by always budgeting for worst-case SID expansion:
    allocate sizeof(struct smb_acl) plus num_aces * sizeof(struct smb_ace), which covers the smb_acl header
    and room for every ACE at maximum SID size. This replaces the previous split logic that used
    dacl_ptr->size for cifsacl mounts but num_aces * sizeof(struct smb_ace) for mode_from_sid mounts: both
    paths can trigger the same rewrite and need the same headroom. KASAN reports this as: BUG: KASAN: slab-
    out-of-bounds in build_sec_desc+0x1e8a/0x2680 [cifs] Write of size 4 at addr ffff8881a5e25374 by task
    chown/5298 ... The buggy address is located 0 bytes to the right of allocated 884-byte region
    [ffff8881a5e25000, ffff8881a5e25374) (CVE-2026-97555)

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-3192 advisory.

    An issue in the Linux kernel's virtio-net/TAP networking path could allow an actor with privileged access     inside a guest virtual machine to send specially crafted network packets that corrupt host kernel memory     on KVM-based hypervisors running unpatched Linux kernel versions 4.4 through 6.18. This could result in     disclosure of host memory or a denial of service.



    In the Linux kernel, the following vulnerability has been resolved:

    sctp: fix err_chunk memory leaks in INIT handling (CVE-2026-72413)

    In the Linux kernel, the following vulnerability has been resolved:

    xfrm: Fix dev use-after-free in xfrm async resumption (CVE-2026-72463)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Guard __get_user acesss with access_ok for uprobe_multi data (CVE-2026-74258)

    In the Linux kernel, the following vulnerability has been resolved:

    ipv4: fib: Don't dump dying fib_info in fib_leaf_notify(). (CVE-2026-74289)

    In the Linux kernel, the following vulnerability has been resolved:

    netfilter: cttimeout: detach dataplane timeout policy and repurpose refcount (CVE-2026-74347)

    In the Linux kernel, the following vulnerability has been resolved:

    fou: Fix use-after-free in fou_create() (CVE-2026-74496)

    In the Linux kernel, the following vulnerability has been resolved:

    vfio/pci: clear vdev->msi_perm after freeing it on init failure (CVE-2026-89777)

    In the Linux kernel, the following vulnerability has been resolved:

    isofs: fix out-of-bounds page array access on empty zisofs block (CVE-2026-89778)

    In the Linux kernel, the following vulnerability has been resolved:

    perf: Fix use-after-free when perf mmap() revival races with the last munmap() (CVE-2026-89791)

    In the Linux kernel, the following vulnerability has been resolved:

    nvme: skip the zoned limits update if the zone info query failed (CVE-2026-89971)

    In the Linux kernel, the following vulnerability has been resolved:

    tcp: reject non zerocopy devmem tx (CVE-2026-90051)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: sch_htb: limit htb_classify inner-class filter hops (CVE-2026-90053)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: bound qdisc_pkt_len to prevent qdisc soft lockup (CVE-2026-90058)

    In the Linux kernel, the following vulnerability has been resolved:

    virtio-net: Ensure that TCP packets don't overflow gso_segs (CVE-2026-90063)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: sfq: clamp quantum to avoid signed overflow soft lockup (CVE-2026-90072)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: hhf: clamp quantum before hhf_change() to avoid overflow (CVE-2026-90073)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: fq_codel: clamp default quantum and mtu (CVE-2026-90075)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: fq: add overflow bounds to quantum and initial quantum (CVE-2026-90076)

    In the Linux kernel, the following vulnerability has been resolved:

    NFSv4/pnfs: key the data server cache on the NFS version (CVE-2026-90102)

    In the Linux kernel, the following vulnerability has been resolved:

    NFSv4.2: fix LAYOUTSTATS send buffer exhaustion (CVE-2026-90103)

    In the Linux kernel, the following vulnerability has been resolved:

    xsk: fix NULL pointer dereference in __xsk_rcv() (CVE-2026-90115)

    In the Linux kernel, the following vulnerability has been resolved:

    vsock: don't check the listener's sk_err in vsock_accept() (CVE-2026-90138)

    In the Linux kernel, the following vulnerability has been resolved:

    null_blk: register configfs subsystem after creating default devices (CVE-2026-90189)

    In the Linux kernel, the following vulnerability has been resolved:

    fs/ntfs3: reject out-of-range evcn in mi_enum_attr() (CVE-2026-90199)

    In the Linux kernel, the following vulnerability has been resolved:

    nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed() (CVE-2026-90227)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Check load-acquire src ptr type before the load (CVE-2026-90312)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf, cgroup: Fix invalid storage access after __cgroup_bpf_attach failed (CVE-2026-90313)

    In the Linux kernel, the following vulnerability has been resolved:

    dm-integrity: replace forgeable discard filler with a keyed sector marker (CVE-2026-90333)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf, x86: Fix trampoline stack size for 128-bit arguments (CVE-2026-90358)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Fix potential UAF in bpf_netns_link_update_prog (CVE-2026-90393)

    In the Linux kernel, the following vulnerability has been resolved:

    iommu/tegra241-cmdqv: Synchronize the error ISR against VINTF (de)init (CVE-2026-90429)

    In the Linux kernel, the following vulnerability has been resolved:

    RDMA/mlx5: Fix integer overflow of user QP buffer size (CVE-2026-90435)

    In the Linux kernel, the following vulnerability has been resolved:

    RDMA/core: Fix potential use after free in ib_dealloc_pd_user() (CVE-2026-92507)

    In the Linux kernel, the following vulnerability has been resolved:

    software node: Fix software_node_get_reference_args() with index -1 (CVE-2026-93046)

    In the Linux kernel, the following vulnerability has been resolved:

    uio: Fix stale info pointer in failed registration path (CVE-2026-93054)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 max (CVE-2026-93125)

    In the Linux kernel, the following vulnerability has been resolved:

    mm/secretmem: properly account locked pages (CVE-2026-93243)

    In the Linux kernel, the following vulnerability has been resolved:

    vxlan: mdb: Fix use-after-free in vxlan_mdb_flush() (CVE-2026-93250)

    In the Linux kernel, the following vulnerability has been resolved:

    ext4: skip extra isize expansion during mount to prevent deadlock (CVE-2026-93268)

    In the Linux kernel, the following vulnerability has been resolved:

    i2c: smbus: reject oversized block transfers in the common path (CVE-2026-93287)

    In the Linux kernel, the following vulnerability has been resolved:

    netfilter: nfnetlink_log: wait for rcu grace period before freeing pernet state (CVE-2026-93288)

    In the Linux kernel, the following vulnerability has been resolved:

    smb/client: zero-initialize stack-allocated cifs_open_info_data (CVE-2026-93801)

    In the Linux kernel, the following vulnerability has been resolved:

    btrfs: tree-checker: validate INODE_REF's namelen (CVE-2026-93813)

    In the Linux kernel, the following vulnerability has been resolved:

    perf: Fix addr_filter_ranges lifetime (CVE-2026-93817)

    In the Linux kernel, the following vulnerability has been resolved:

    tls: reject the combination of TLS and sockmap (CVE-2026-93824)

    In the Linux kernel, the following vulnerability has been resolved:

    virtio-fs: avoid double-free on failed queue setup (CVE-2026-93827)

    In the Linux kernel, the following vulnerability has been resolved:

    exfat: fix handling of damaged volume in exfat_create_upcase_table() (CVE-2026-93828)

    In the Linux kernel, the following vulnerability has been resolved:

    btrfs: tree-checker: validate names in ROOT_REF and ROOT_BACKREF (CVE-2026-97415)

    In the Linux kernel, the following vulnerability has been resolved:

    RDMA/umem: Be careful about boundary conditions in ib_umem_find_best_pgsz() (CVE-2026-97421)

    In the Linux kernel, the following vulnerability has been resolved:

    fs/ntfs3: validate index entry key bounds (CVE-2026-97438)

    In the Linux kernel, the following vulnerability has been resolved:

    fs/ntfs3: preserve non-DOS attribute bits in system.dos_attrib (CVE-2026-97439)

    In the Linux kernel, the following vulnerability has been resolved:

    ACPICA: Fix use-after-free in acpi_ds_terminate_control_method() (CVE-2026-97455)

    In the Linux kernel, the following vulnerability has been resolved:

    mptcp: avoid unneeded actions on subflow reset (CVE-2026-97524)

    In the Linux kernel, the following vulnerability has been resolved:

    x86/mm/pat: Acquire init_mm read lock on attribute changes to avoid UAF (CVE-2026-97533)

    In the Linux kernel, the following vulnerability has been resolved:

    smb: client: fix heap overflow in DACL owner/group rewrite (CVE-2026-97555)

    In the Linux kernel, the following vulnerability has been resolved:

    smb: client: reject short READ responses in CIFSSMBRead() (CVE-2026-97565)

    In the Linux kernel, the following vulnerability has been resolved:

    landlock: Fix use-after-free of the source's parent directory (CVE-2026-97594)

    In the Linux kernel, the following vulnerability has been resolved:

    ipvs: reject invalid states in connection template sync records (CVE-2026-97596)

    In the Linux kernel, the following vulnerability has been resolved:

    ipv6: flowlabel: cap duplicate leases per socket (CVE-2026-97597)

    In the Linux kernel, the following vulnerability has been resolved:

    inet: frags: invalidate queues before flushing them (CVE-2026-97602)

    In the Linux kernel, the following vulnerability has been resolved:

    net: openvswitch: fix use-after-free of the flow table mask array (CVE-2026-97611)

    In the Linux kernel, the following vulnerability has been resolved:

    ipv6: fix fib6 walker UAF on seq stop (CVE-2026-97940)

    In the Linux kernel, the following vulnerability has been resolved:

    x86/mm/pat: Acquire init_mm write lock on collapse to avoid UAF (CVE-2026-97943)

    In the Linux kernel, the following vulnerability has been resolved:

    configfs: unhash the dentry before dropping the item in rmdir (CVE-2026-97949)

    In the Linux kernel, the following vulnerability has been resolved:

    scsi: target: iscsi: Fix hang for aborted WRITE_PENDING commands (CVE-2026-97951)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: drr: clamp quantum in change class (CVE-2026-98010)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: hhf: clamp quantum in change and init paths (CVE-2026-98011)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: sfq: clamp quantum in change path (CVE-2026-98012)

    In the Linux kernel, the following vulnerability has been resolved:

    net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put (CVE-2026-98015)

    In the Linux kernel, the following vulnerability has been resolved:

    net/mlx5e: Fix use-after-free race in sample_restore_put() (CVE-2026-98016)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Reject untrusted allocated-object pointers (CVE-2026-98037)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Require MEM_PERCPU for percpu kptr stores (CVE-2026-98039)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Don't predict JMP32 pointer vs zero comparisons (CVE-2026-98041)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Check ancestor frames for rbtree callbacks (CVE-2026-98047)

    In the Linux kernel, the following vulnerability has been resolved:

    nvme: remove stale namespaces by NSID range during scan (CVE-2026-98056)

    In the Linux kernel, the following vulnerability has been resolved:

    bpf: Reject resilient lock operations in rbtree callbacks (CVE-2026-98060)

    In the Linux kernel, the following vulnerability has been resolved:

    net/rds: acquire RDS_IN_XMIT in rds_tcp_reset_callbacks() (CVE-2026-98070)

    In the Linux kernel, the following vulnerability has been resolved:

    ipvs: fix reversed sequence option serialization (CVE-2026-98078)

    In the Linux kernel, the following vulnerability has been resolved:

    af_packet: Don't cast tpacket_hdr.tp_len to int in tpacket_parse_header(). (CVE-2026-98095)

    In the Linux kernel, the following vulnerability has been resolved:

    ipv6: sr: restore network header before routing and forwarding (CVE-2026-98096)

    In the Linux kernel, the following vulnerability has been resolved:

    net/sched: cls_u32: fix duplicate handle when node ID pool is exhausted (CVE-2026-98104)

    In the Linux kernel, the following vulnerability has been resolved:

    netfs: Fix subreq ref leak (CVE-2026-98120)

    In the Linux kernel, the following vulnerability has been resolved:

    vxlan: mdb: Fix use-after-free in vxlan_mdb_remote_src_del() (CVE-2026-98122)

    In the Linux kernel, the following vulnerability has been resolved:

    sctp: fix soft lockup from unpadded ASCONF-ACK parameter iteration (CVE-2026-98123)

    In the Linux kernel, the following vulnerability has been resolved:

    sctp: fix a TOCTOU race in SCTP_CMD_TIMER_START (CVE-2026-98130)

    In the Linux kernel, the following vulnerability has been resolved:

    drm/virtio: use the DMA API for resource backing on Xen (CVE-2026-98156)

    In the Linux kernel, the following vulnerability has been resolved: ipv4: validate checksum_start before     completing checksum If a packet with bad checksum metadata gets into the ipv4 stack, skb_checksum_help can     corrupt the network header and cause a bunch of mischief. This was discovered and reported by Paulos, and     has been reporoduced by others independently since. We really shouldn't allow such packets in, but as a     defence in depth measure, let's also check before we complete the checksum. A more complete validation at     input is forthcoming, but needs more work. (CVE-2026-99999)

Tenable has extracted the preceding description block directly from the tested product 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.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1791741836 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: vhost: fix hung thread due to     erroneous iotlb entries In vhost_iotlb_add_range_ctx(), range size can overflow to 0 when start is 0 and     last is ULONG_MAX. One instance where it can happen is when userspace sends an IOTLB message with     iova=size=uaddr=0 (vhost_process_iotlb_msg). So, an entry with size = 0, start = 0, last = ULONG_MAX ends     up in the iotlb. Next time a packet is sent, iotlb_access_ok() loops indefinitely due to that erroneous     entry. Call Trace: <TASK> iotlb_access_ok+0x21b/0x3e0 drivers/vhost/vhost.c:1340     vq_meta_prefetch+0xbc/0x280 drivers/vhost/vhost.c:1366 vhost_transport_do_send_pkt+0xe0/0xfd0     drivers/vhost/vsock.c:104 vhost_worker+0x23d/0x3d0 drivers/vhost/vhost.c:372 kthread+0x2e9/0x3a0     kernel/kthread.c:377 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 </TASK> Reported by syzbot at:
    https://syzkaller.appspot.com/bug?extid=0abd373e2e50d704db87 To fix this, do two things: 1. Return -EINVAL     in vhost_chr_write_iter() when userspace asks to map a range with size 0. 2. Fix     vhost_iotlb_add_range_ctx() to handle the range [0, ULONG_MAX] by splitting it into two entries.
    (CVE-2022-48862)

  - In the Linux kernel, the following vulnerability has been resolved: net: hns3: add vlan list lock to     protect vlan list When adding port base VLAN, vf VLAN need to remove from HW and modify the vlan state in     vf VLAN list as false. If the periodicity task is freeing the same node, it may cause use after free     error. This patch adds a vlan list lock to protect the vlan list. (CVE-2022-49182)

  - In the Linux kernel, the following vulnerability has been resolved: perf/x86/amd: Fix crash due to race     between amd_pmu_enable_all, perf NMI and throttling amd_pmu_enable_all() does: if (!test_bit(idx,     cpuc->active_mask)) continue; amd_pmu_enable_event(cpuc->events[idx]); A perf NMI of another event can     come between these two steps. Perf NMI handler internally disables and enables _all_ events, including the     one which nmi-intercepted amd_pmu_enable_all() was in process of enabling. If that unintentionally enabled     event has very low sampling period and causes immediate successive NMI, causing the event to be throttled,     cpuc->events[idx] and cpuc->active_mask gets cleared by x86_pmu_stop(). This will result in     amd_pmu_enable_event() getting called with event=NULL when amd_pmu_enable_all() resumes after handling the     NMIs. This causes a kernel crash: BUG: kernel NULL pointer dereference, address: 0000000000000198 #PF:
    supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page [...] Call Trace: <TASK>     amd_pmu_enable_all+0x68/0xb0 ctx_resched+0xd9/0x150 event_function+0xb8/0x130 ?     hrtimer_start_range_ns+0x141/0x4a0 ? perf_duration_warn+0x30/0x30 remote_function+0x4d/0x60
    __flush_smp_call_function_queue+0xc4/0x500 flush_smp_call_function_queue+0x11d/0x1b0 do_idle+0x18f/0x2d0     cpu_startup_entry+0x19/0x20 start_secondary+0x121/0x160 secondary_startup_64_no_verify+0xe5/0xeb </TASK>     amd_pmu_disable_all()/amd_pmu_enable_all() calls inside perf NMI handler were recently added as part of     BRS enablement but I'm not sure whether we really need them. We can just disable BRS in the beginning and     enable it back while returning from NMI. This will solve the issue by not enabling those events whose     active_masks are set but are not yet enabled in hw pmu. (CVE-2022-49781)

  - In the Linux kernel, the following vulnerability has been resolved: blk-iolatency: Fix memory leak on     add_disk() failures When a gendisk is successfully initialized but add_disk() fails such as when a loop     device has invalid number of minor device numbers specified, blkcg_init_disk() is called during init and     then blkcg_exit_disk() during error handling. Unfortunately, iolatency gets initialized in the former but     doesn't get cleaned up in the latter. This is because, in non-error cases, the cleanup is performed by     del_gendisk() calling rq_qos_exit(), the assumption being that rq_qos policies, iolatency being one of     them, can only be activated once the disk is fully registered and visible. That assumption is true for wbt     and iocost, but not so for iolatency as it gets initialized before add_disk() is called. It is desirable     to lazy-init rq_qos policies because they are optional features and add to hot path overhead once     initialized - each IO has to walk all the registered rq_qos policies. So, we want to switch iolatency to     lazy init too. However, that's a bigger change. As a fix for the immediate problem, let's just add an     extra call to rq_qos_exit() in blkcg_exit_disk(). This is safe because duplicate calls to rq_qos_exit()     become noop's. (CVE-2022-50550)

  - In the Linux kernel, the following vulnerability has been resolved: usb: roles: fix NULL pointer issue     when put module's reference In current design, usb role class driver will get usb_role_switch parent's     module reference after the user get usb_role_switch device and put the reference after the user put the     usb_role_switch device. However, the parent device of usb_role_switch may be removed before the user put     the usb_role_switch. If so, then, NULL pointer issue will be met when the user put the parent module's     reference. This will save the module pointer in structure of usb_role_switch. Then, we don't need to find     module by iterating long relations. (CVE-2024-26747)

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.

  - smb: client: fix heap overflow in DACL owner/group rewrite When id_mode_to_cifs_acl rewrites an existing     DACL, it allocates a buffer sized according to the on-disk DACL length reported by dacl_ptr->size.
    However, replace_sids_and_copy_aces may rewrite each ACE with a new owner/group SID obtained from the     cifs.idmap upcall. Those SIDs can have up to SID_MAX_SUB_AUTHORITIES (15) sub-authorities, making each ACE     up to 76 bytes (sizeof(struct smb_ace)). If the original DACL contains short SIDs (e.g., 1 sub-authority)     while the replacement SIDs are long, the rewritten ACEs overflow the allocation. Fix this by always     budgeting for worst-case SID expansion: allocate sizeof(struct smb_acl) plus num_aces * sizeof(struct     smb_ace), which covers the smb_acl header and room for every ACE at maximum SID size. This replaces the     previous split logic that used dacl_ptr->size for cifsacl mounts but num_aces * sizeof(struct smb_ace) for     mode_from_sid mounts: both paths can trigger the same rewrite and need the same headroom. KASAN reports     this as: BUG: KASAN: slab-out-of-bounds in build_sec_desc+0x1e8a/0x2680 [cifs] Write of size 4 at addr     ffff8881a5e25374 by task chown/5298 ... The buggy address is located 0 bytes to the right of allocated     884-byte region [ffff8881a5e25000, ffff8881a5e25374) (CVE-2026-97555)

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

ID	Name	Product	Family	Type	Severity
475386	Google: sys-kernel/cchost-kernel-6_12, sys-kernel/cchost-kernel-6_18, sys-kernel/csql-kernel-6_12, sys-kernel/csql-kernel-6_18, sys-kernel/lakitu-kernel-6_12, sys-kernel/lakitu-kernel-6_18, sys-kernel/lakitu-nc-kernel-6_12, sys-kernel/lakitu-nc-kernel-6_18: security update to 19999.44.106	Tenable Cloud Security	Google COS Security Checks	Local	high
475386	Google: sys-kernel/cchost-kernel-6_12, sys-kernel/cchost-kernel-6_18, sys-kernel/csql-kernel-6_12, sys-kernel/csql-kernel-6_18, sys-kernel/lakitu-kernel-6_12, sys-kernel/lakitu-kernel-6_18, sys-kernel/lakitu-nc-kernel-6_12, sys-kernel/lakitu-nc-kernel-6_18: security update to 19999.44.106	Tenable Self-Hosted Container Security	Google COS Security Checks	Local	high
365258	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-3192)	Nessus	Amazon Linux Local Security Checks	Local	medium
365209	Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2026-3193)	Nessus	Amazon Linux Local Security Checks	Local	medium
364688	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1791741836)	Nessus	Alma Linux Local Security Checks	Local	critical
364137	Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2026-500374)	Nessus	Oracle Linux Local Security Checks	Local	high
362907	Debian dla-4817 : ata-modules-6.12.107+deb12-armmp-di - security update	Nessus	Debian Local Security Checks	Local	high
351155	Debian dsa-6528 : ata-modules-6.12.111+deb13-armmp-di - security update	Nessus	Debian Local Security Checks	Local	high
350508	Linux Distros Unpatched Vulnerability : CVE-2026-97555	Nessus	Misc.	Local	high

Detections

Analytics

CVE-2026-97555

high

Tenable Plugins

high

high

medium

medium

critical

high

high

high

high