In the Linux kernel, the following vulnerability has been resolved: sctp: fix err_chunk memory leaks in INIT handling When sctp_verify_init() encounters unrecognized parameters, it allocates an err_chunk to report them. However, this chunk is leaked in several code paths: 1. In sctp_sf_do_5_1B_init(), if security_sctp_assoc_request() fails after sctp_verify_init() has populated err_chunk, the function returns immediately without freeing it. 2. In sctp_sf_do_unexpected_init(), the same leak occurs on the security_sctp_assoc_request() failure path. 3. In sctp_sf_do_unexpected_init(), on the success path after copying unrecognized parameters to the INIT-ACK, the function returns without freeing err_chunk, unlike sctp_sf_do_5_1B_init() which properly frees it. Fix all three leaks by adding sctp_chunk_free(err_chunk) calls before returning in the error paths and on the success path in sctp_sf_do_unexpected_init().

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

  - nfqnl_mangle in net/netfilter/nfnetlink_queue.c in the Linux kernel through 5.18.14 allows remote     attackers to cause a denial of service (panic) because, in the case of an nf_queue verdict with a one-byte     nfta_payload attribute, an skb_pull can encounter a negative skb->len. (CVE-2022-36946)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: Fix a memory     corruption issue A few lines above, space is kzalloc()'ed for: sizeof(struct iwl_nvm_data) + sizeof(struct     ieee80211_channel) + sizeof(struct ieee80211_rate) 'mvm->nvm_data' is a 'struct iwl_nvm_data', so it is     fine. At the end of this structure, there is the 'channels' flex array. Each element is of type 'struct     ieee80211_channel'. So only 1 element is allocated in this array. When doing:
    mvm->nvm_data->bands[0].channels = mvm->nvm_data->channels; We point at the first element of the     'channels' flex array. So this is fine. However, when doing: mvm->nvm_data->bands[0].bitrates = (void
    *)((u8 *)mvm->nvm_data->channels + 1); because of the (u8 *) cast, we add only 1 to the address of the     beginning of the flex array. It is likely that we want point at the 'struct ieee80211_rate' allocated just     after. Remove the spurious casting so that the pointer arithmetic works as expected. (CVE-2023-52531)

  - In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Don't (re)check L1     intercepts when completing userspace I/O When completing emulation of instruction that generated a     userspace exit for I/O, don't recheck L1 intercepts as KVM has already finished that phase of instruction     execution, i.e. has already committed to allowing L2 to perform I/O. If L1 (or host userspace) modifies     the I/O permission bitmaps during the exit to userspace, KVM will treat the access as being intercepted     despite already having emulated the I/O access. Pivot on EMULTYPE_NO_DECODE to detect that KVM is     completing emulation. Of the three users of EMULTYPE_NO_DECODE, only complete_emulated_io() (the intended     recipient) can reach the code in question. gp_interception()'s use is mutually exclusive with     is_guest_mode(), and complete_emulated_insn_gp() unconditionally pairs EMULTYPE_NO_DECODE with     EMULTYPE_SKIP. The bad behavior was detected by a syzkaller program that toggles port I/O interception     during the userspace I/O exit, ultimately resulting in a WARN on vcpu->arch.pio.count being non-zero due     to KVM no completing emulation of the I/O instruction. WARNING: CPU: 23 PID: 1083 at     arch/x86/kvm/x86.c:8039 emulator_pio_in_out+0x154/0x170 [kvm] Modules linked in: kvm_intel kvm irqbypass     CPU: 23 UID: 1000 PID: 1083 Comm: repro Not tainted 6.16.0-rc5-c1610d2d66b1-next-vm #74 NONE Hardware     name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 RIP: 0010:emulator_pio_in_out+0x154/0x170     [kvm] PKRU: 55555554 Call Trace: <TASK> kvm_fast_pio+0xd6/0x1d0 [kvm] vmx_handle_exit+0x149/0x610     [kvm_intel] kvm_arch_vcpu_ioctl_run+0xda8/0x1ac0 [kvm] kvm_vcpu_ioctl+0x244/0x8c0 [kvm]
    __x64_sys_ioctl+0x8a/0xd0 do_syscall_64+0x5d/0xc60 entry_SYSCALL_64_after_hwframe+0x4b/0x53 </TASK>     (CVE-2025-40026)

  - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btusb: fix use-after-free     on registration failure Make sure to release the sibling interfaces in case controller registration fails     to avoid use-after-free and double-free when they are eventually disconnected. This issue was reported by     Sashiko while reviewing a fix for a wakeup source leak in the btusb probe errors paths. (CVE-2026-64471)

  - In the Linux kernel, the following vulnerability has been resolved: ALSA: firewire: isight: bound the     sample count to the packet payload isight_packet() takes the frame count from the device iso packet and     checks it only against the device claimed iso length. count = be32_to_cpu(payload->sample_count); if     (likely(count <= (length - 16) / 4)) isight_samples(isight, payload->samples, count); length is the iso     header data_length. It can be up to 0xffff. So the gate allows a count up to about 16379. isight_samples()     then copies count frames out of payload->samples into the PCM DMA buffer. payload->samples holds only 2 *     MAX_FRAMES_PER_PACKET values. The device multiplexes two samples per frame. A count past     MAX_FRAMES_PER_PACKET reads past the payload. A count past the buffer size writes past runtime->dma_area.
    The smallest PCM buffer is larger than MAX_FRAMES_PER_PACKET. Bounding the count to MAX_FRAMES_PER_PACKET     keeps both the read and the write in range. A malicious or faulty Apple iSight on the FireWire bus reaches     this during a normal capture. Add the MAX_FRAMES_PER_PACKET bound to the gate. (CVE-2026-64483)

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

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

  - In the Linux kernel, the following vulnerability has been resolved: HID: core: zero-initialize the report     buffer Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it     during allocation to make sure that it can't be ever used to leak kernel memory via specially-crafted     report. (CVE-2024-50302)

  - In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Fix potential out-of-     bound accesses for Extigy and Mbox devices A bogus device can provide a bNumConfigurations value that     exceeds the initial value used in usb_get_configuration for allocating dev->config. This can lead to out-     of-bounds accesses later, e.g. in usb_destroy_configuration. (CVE-2024-53197)

  - In the Linux kernel, the following vulnerability has been resolved: smb: client: reject userspace     cifs.spnego descriptions cifs.spnego key descriptions contain authority-bearing fields such as pid, uid,     creduid, and upcall_target that cifs.upcall treats as kernel-originating inputs. However, userspace can     also create keys of this type through request_key(2) or add_key(2), allowing those fields to be supplied     without CIFS origin. Only accept cifs.spnego descriptions while CIFS is using its private spnego_cred to     request the key. (CVE-2026-46243)

  - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: serialize accept_q access     bt_sock_poll() walks the accept queue without synchronization, while child teardown can unlink the same     socket and drop its last reference. The unsynchronized accept queue walk has existed since the initial     Bluetooth import. Protect accept_q with a dedicated lock for queue updates and polling. Also rework     bt_accept_dequeue() to take temporary child references under the queue lock before dropping it and locking     the child socket. (CVE-2026-52918)

  - In the Linux kernel, the following vulnerability has been resolved: netfilter: bridge: make ebt_snat ARP     rewrite writable The ebtables SNAT target keeps the Ethernet source address rewrite behind     skb_ensure_writable(skb, 0). This is intentional: at the bridge ebtables hooks the Ethernet header is     addressed through skb_mac_header()/eth_hdr(), while skb->data points at the Ethernet payload. Asking     skb_ensure_writable() for ETH_HLEN bytes would check the payload, not the Ethernet header, and would     reintroduce the small packet regression fixed by commit 63137bc5882a. However, the optional ARP sender     hardware address rewrite is different. It writes through skb_store_bits() at an offset relative to     skb->data: skb_store_bits(skb, sizeof(struct arphdr), info->mac, ETH_ALEN) skb_header_pointer() only     safely reads the ARP header; it does not make the later sender hardware address range writable. If that     range is still held in a nonlinear skb fragment backed by a splice-imported file page, skb_store_bits()     maps the frag page and copies the new MAC address directly into it. Ensure the ARP SHA range is writable     before reading the ARP header and before calling skb_store_bits(). (CVE-2026-53266)

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

The CentOS Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS-STREAM8:CLSA-2026:1792239979 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: kyber: fix out of bounds access when     preempted __blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and passes the hctx to
    ->bio_merge(). kyber_bio_merge() then gets the ctx for the current CPU again and uses that to get the     corresponding Kyber context in the passed hctx. However, the thread may be preempted between the two calls     to blk_mq_get_ctx(), and the ctx returned the second time may no longer correspond to the passed hctx.
    This works accidentally most of the time, but it can cause us to read garbage if the second ctx came     from an hctx with more ctx's than the first one (i.e., if ctx->index_hw[hctx->type] > hctx->nr_ctx). This     manifested as this UBSAN array index out of bounds error reported by Jakub: UBSAN: array-index-out-of-     bounds in ../kernel/locking/qspinlock.c:130:9 index 13106 is out of range for type 'long unsigned int     [128]' Call Trace: dump_stack+0xa4/0xe5 ubsan_epilogue+0x5/0x40
    __ubsan_handle_out_of_bounds.cold.13+0x2a/0x34 queued_spin_lock_slowpath+0x476/0x480     do_raw_spin_lock+0x1c2/0x1d0 kyber_bio_merge+0x112/0x180 blk_mq_submit_bio+0x1f5/0x1100     submit_bio_noacct+0x7b0/0x870 submit_bio+0xc2/0x3a0 btrfs_map_bio+0x4f0/0x9d0     btrfs_submit_data_bio+0x24e/0x310 submit_one_bio+0x7f/0xb0 submit_extent_page+0xc4/0x440
    __extent_writepage_io+0x2b8/0x5e0 __extent_writepage+0x28d/0x6e0 extent_write_cache_pages+0x4d7/0x7a0     extent_writepages+0xa2/0x110 do_writepages+0x8f/0x180 __writeback_single_inode+0x99/0x7f0     writeback_sb_inodes+0x34e/0x790 __writeback_inodes_wb+0x9e/0x120 wb_writeback+0x4d2/0x660     wb_workfn+0x64d/0xa10 process_one_work+0x53a/0xa80 worker_thread+0x69/0x5b0 kthread+0x20b/0x240     ret_from_fork+0x1f/0x30 Only Kyber uses the hctx, so fix it by passing the request_queue to ->bio_merge()     instead. BFQ and mq-deadline just use that, and Kyber can map the queues itself to avoid the mismatch.
    (CVE-2021-46984)

  - A use-after-free flaw was found in the Linux kernel's SGI GRU driver in the way the first     gru_file_unlocked_ioctl function is called by the user, where a fail pass occurs in the     gru_check_chiplet_assignment function. This flaw allows a local user to crash or potentially escalate     their privileges on the system. (CVE-2022-3424)

  - In the Linux kernel, the following vulnerability has been resolved: bpf, test_run: Fix alignment problem     in bpf_prog_test_run_skb() We got a syzkaller problem because of aarch64 alignment fault if KFENCE     enabled. When the size from user bpf program is an odd number, like 399, 407, etc, it will cause the     struct skb_shared_info's unaligned access. As seen below: BUG: KFENCE: use-after-free read in
    __skb_clone+0x23c/0x2a0 net/core/skbuff.c:1032 Use-after-free read at 0xffff6254fffac077 (in kfence-#213):
    __lse_atomic_add arch/arm64/include/asm/atomic_lse.h:26 [inline] arch_atomic_add     arch/arm64/include/asm/atomic.h:28 [inline] arch_atomic_inc include/linux/atomic-arch-fallback.h:270     [inline] atomic_inc include/asm-generic/atomic-instrumented.h:241 [inline] __skb_clone+0x23c/0x2a0     net/core/skbuff.c:1032 skb_clone+0xf4/0x214 net/core/skbuff.c:1481 ____bpf_clone_redirect     net/core/filter.c:2433 [inline] bpf_clone_redirect+0x78/0x1c0 net/core/filter.c:2420     bpf_prog_d3839dd9068ceb51+0x80/0x330 bpf_dispatcher_nop_func include/linux/bpf.h:728 [inline]     bpf_test_run+0x3c0/0x6c0 net/bpf/test_run.c:53 bpf_prog_test_run_skb+0x638/0xa7c net/bpf/test_run.c:594     bpf_prog_test_run kernel/bpf/syscall.c:3148 [inline] __do_sys_bpf kernel/bpf/syscall.c:4441 [inline]
    __se_sys_bpf+0xad0/0x1634 kernel/bpf/syscall.c:4381 kfence-#213: 0xffff6254fffac000-0xffff6254fffac196,     size=407, cache=kmalloc-512 allocated by task 15074 on cpu 0 at 1342.585390s: kmalloc     include/linux/slab.h:568 [inline] kzalloc include/linux/slab.h:675 [inline]     bpf_test_init.isra.0+0xac/0x290 net/bpf/test_run.c:191 bpf_prog_test_run_skb+0x11c/0xa7c     net/bpf/test_run.c:512 bpf_prog_test_run kernel/bpf/syscall.c:3148 [inline] __do_sys_bpf     kernel/bpf/syscall.c:4441 [inline] __se_sys_bpf+0xad0/0x1634 kernel/bpf/syscall.c:4381
    __arm64_sys_bpf+0x50/0x60 kernel/bpf/syscall.c:4381 To fix the problem, we adjust @size so that (@size +     @hearoom) is a multiple of SMP_CACHE_BYTES. So we make sure the struct skb_shared_info is aligned to a     cache line. (CVE-2022-49840)

  - In the Linux kernel, the following vulnerability has been resolved: usbnet: Fix linkwatch use-after-free     on disconnect usbnet uses the work usbnet_deferred_kevent() to perform tasks which may sleep. On     disconnect, completion of the work was originally awaited in ->ndo_stop(). But in 2003, that was moved to
    ->disconnect() by historic commit [PATCH] USB: usbnet, prevent exotic rtnl deadlock:
    https://git.kernel.org/tglx/history/c/0f138bbfd83c The change was made because back then, the kernel's     workqueue implementation did not allow waiting for a single work. One had to wait for completion of *all*     work by calling flush_scheduled_work(), and that could deadlock when waiting for usbnet_deferred_kevent()     with rtnl_mutex held in ->ndo_stop(). The commit solved one problem but created another: It causes a use-     after-free in USB Ethernet drivers aqc111.c, asix_devices.c, ax88179_178a.c, ch9200.c and smsc75xx.c: * If     the drivers receive a link change interrupt immediately before disconnect, they raise EVENT_LINK_RESET in     their (non-sleepable) ->status() callback and schedule usbnet_deferred_kevent(). *     usbnet_deferred_kevent() invokes the driver's ->link_reset() callback, which calls     netif_carrier_{on,off}(). * That in turn schedules the work linkwatch_event(). Because     usbnet_deferred_kevent() is awaited after unregister_netdev(), netif_carrier_{on,off}() may operate on an     unregistered netdev and linkwatch_event() may run after free_netdev(), causing a use-after-free. In 2010,     usbnet was changed to only wait for a single instance of usbnet_deferred_kevent() instead of *all* work by     commit 23f333a2bfaf (drivers/net: don't use flush_scheduled_work()). Unfortunately the commit neglected     to move the wait back to ->ndo_stop(). Rectify that omission at long last. (CVE-2022-50220)

  - In the Linux kernel, the following vulnerability has been resolved: cifs: fix oops during encryption When     running xfstests against Azure the following oops occurred on an arm64 system Unable to handle kernel     write to read-only memory at virtual address ffff0001221cf000 Mem abort info: ESR = 0x9600004f EC = 0x25:
    DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x0f: level 3 permission fault     Data abort info: ISV = 0, ISS = 0x0000004f CM = 0, WnR = 1 swapper pgtable: 4k pages, 48-bit VAs,     pgdp=00000000294f3000 [ffff0001221cf000] pgd=18000001ffff8003, p4d=18000001ffff8003, pud=18000001ff82e003,     pmd=18000001ff71d003, pte=00600001221cf787 Internal error: Oops: 9600004f [#1] PREEMPT SMP ... pstate:
    80000005 (Nzcv daif -PAN -UAO -TCO BTYPE=--) pc : __memcpy+0x40/0x230 lr :
    scatterwalk_copychunks+0xe0/0x200 sp : ffff800014e92de0 x29: ffff800014e92de0 x28: ffff000114f9de80 x27:
    0000000000000008 x26: 0000000000000008 x25: ffff800014e92e78 x24: 0000000000000008 x23: 0000000000000001     x22: 0000040000000000 x21: ffff000000000000 x20: 0000000000000001 x19: ffff0001037c4488 x18:
    0000000000000014 x17: 235e1c0d6efa9661 x16: a435f9576b6edd6c x15: 0000000000000058 x14: 0000000000000001     x13: 0000000000000008 x12: ffff000114f2e590 x11: ffffffffffffffff x10: 0000040000000000 x9 :
    ffff8000105c3580 x8 : 2e9413b10000001a x7 : 534b4410fb86b005 x6 : 534b4410fb86b005 x5 : ffff0001221cf008     x4 : ffff0001037c4490 x3 : 0000000000000001 x2 : 0000000000000008 x1 : ffff0001037c4488 x0 :
    ffff0001221cf000 Call trace: __memcpy+0x40/0x230 scatterwalk_map_and_copy+0x98/0x100     crypto_ccm_encrypt+0x150/0x180 crypto_aead_encrypt+0x2c/0x40 crypt_message+0x750/0x880     smb3_init_transform_rq+0x298/0x340 smb_send_rqst.part.11+0xd8/0x180 smb_send_rqst+0x3c/0x100     compound_send_recv+0x534/0xbc0 smb2_query_info_compound+0x32c/0x440 smb2_set_ea+0x438/0x4c0     cifs_xattr_set+0x5d4/0x7c0 This is because in scatterwalk_copychunks(), we attempted to write to a buffer     (@sign) that was allocated in the stack (vmalloc area) by crypt_message() and thus accessing its remaining     8 (x2) bytes ended up crossing a page boundary. To simply fix it, we could just pass @sign kmalloc'd from     crypt_message() and then we're done. Luckily, we don't seem to pass any other vmalloc'd buffers in     smb_rqst::rq_iov... Instead, let's map the correct pages and offsets from vmalloc buffers as well in     cifs_sg_set_buf() and then avoiding such oopses. (CVE-2022-50341)

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

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 version of kernel installed on the remote host is prior to 5.10.268-266.1092. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2026-132 advisory.

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

    drm/virtio: use uninterruptible resv lock for plane updates (CVE-2026-64098)

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

    bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized

    When CONFIG_BPF_LSM=y is set, BPF inode storage maps(BPF_MAP_TYPE_INODE_STORAGE) are compiled into the     kernel. However,if the BPF LSM is not explicitly enabled at boot time (e.g. omittedfrom the lsm= boot     parameter), lsm_prepare() is never executed forthe BPF LSM.

    Consequently, the BPF inode security blob offset(bpf_lsm_blob_sizes.lbs_inode) is never initialized and     remains atits default compiled size of 8 bytes instead of being updated to avalid offset past the reserved     struct rcu_head (typically 16 bytesor more).

    When a privileged user creates and updates a BPF_MAP_TYPE_INODE_STORAGEmap, bpf_inode() evaluates     inode->i_security + 8. This erroneouslyaliases the struct rcu_head.func callback pointer at the     beginningof the inode->i_security blob. During subsequent map element cleanupor inode destruction, writing     NULL to owner_storage clears the queuedRCU callback pointer. When rcu_do_batch() later executes the     queuedcallback, it attempts an instruction fetch at address 0x0, triggeringan immediate kernel panic.

    Fix this by introducing a global bpf_lsm_initialized boolean flagmarked with __ro_after_init. Set this     flag to true inside bpf_lsm_init()when the LSM framework successfully registers the BPF LSM. Gate     mapallocation in inode_storage_map_alloc() on this flag, returning-EOPNOTSUPP if the BPF LSM is in turn     uninitialized.

    This fail-fast approach prevents userspace from allocating inodestorage maps when the supporting BPF LSM     infrastructure is absent,avoiding zombie map states. (CVE-2026-64192)

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

    i2c: core: fix adapter deregistration race (CVE-2026-64279)

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

    libceph: fix two unsafe bare decodes in decode_lockers() (CVE-2026-68082)

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

    audit: fix recursive locking deadlock in audit_dupe_exe() (CVE-2026-68096)

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

    super: fix emergency thaw deadlock on frozen block devices (CVE-2026-68132)

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

    net: gro: fix double aggregation of flush-marked skbs (CVE-2026-68136)

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

    ftrace: Add global mutex to serialize trace_parser access (CVE-2026-68146)

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

    libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE (CVE-2026-68159)

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

    sctp: avoid auth_enable sysctl UAF during netns teardown (CVE-2026-68162)

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

    drm/virtio: bound EDID block reads to the response buffer (CVE-2026-68255)

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

    drm/dp/mst: fix OOB reads on 2-byte fields in sideband reply parsers (CVE-2026-68277)

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

    drm/dp/mst: fix buffer overflows in sideband chunk accumulation (CVE-2026-68278)

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

    drm/dp/mst: fix OOB reads in remote DPCD/I2C sideband reply parsers (CVE-2026-68279)

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

    mmc: vub300: fix use-after-free on probe failure (CVE-2026-72073)

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

    scsi: target: Bound PR-OUT TransportID parsing to the received buffer (CVE-2026-72084)

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

    scsi: lpfc: Fix memory leak in lpfc_sli4_driver_resource_setup() (CVE-2026-72087)

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

    dm-verity: make error counter atomic (CVE-2026-72096)

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

    dm-integrity: don't increment hash_offset twice (CVE-2026-72099)

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

    jbd2: fix integer underflow in jbd2_journal_initialize_fast_commit() (CVE-2026-72225)

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

    selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (CVE-2026-72242)

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

    netfilter: nft_set_pipapo: don't leak bad clone into future transaction (CVE-2026-72252)

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

    netfilter: nf_conntrack_sip: validate skb_dst() before accessing it (CVE-2026-72253)

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

    netfilter: nf_queue: pin bridge device while NFQUEUE holds fake dst (CVE-2026-72255)

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

    KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling (CVE-2026-72288)

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

    tipc: restrict socket queue dumps in enqueue tracepoints (CVE-2026-72299)

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

    mlxsw: fix refcount leak in mlxsw_sp_port_lag_join() (CVE-2026-72308)

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

    sctp: add INIT verification after cookie unpacking (CVE-2026-72398)

    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:

    netfilter: nft_compat: ebtables emulation must reject non-bridge targets (CVE-2026-72416)

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

    xprtrdma: Repost Receive buffers for malformed replies (CVE-2026-72464)

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

    RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe (CVE-2026-74378)

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

    OPP: Fix race between OPP addition and lookup (CVE-2026-74405)

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

    scsi: scsi_debug: Fix REPORT ZONES alloc_len underflow OOB write (CVE-2026-74470)

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

    net: pktgen: fix proc entry use-after-free (CVE-2026-74479)

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

    binfmt_misc: restore write access when removing an entry (CVE-2026-74487)

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

    netfilter: nf_tables: make nft_object rhltable per table (CVE-2026-74565)

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

    packet: use consistent hard_header_len in non-ring send paths (CVE-2026-74582)

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

    sched/psi: Shut down rtpoll_timer in psi_cgroup_free() (CVE-2026-74594)

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

    ring-buffer: Use current_context for safe per-CPU buffer swap (CVE-2026-74601)

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

    net/sched: act_gact, act_police: range check the fallback control action (CVE-2026-74620)

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

    mm/huge_memory: fix huge_zero_pfn race (CVE-2026-74632)

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

    perf/core: Fix group leader use-after-free after sibling detach (CVE-2026-74637)

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

    ipv4: Fix fib_nlmsg_size() for RTA_VIA nexthops (CVE-2026-74657)

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

    inet: frags: publish queues before arming timer (CVE-2026-74662)

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

    net/sched: reject overly deep qdisc hierarchies (CVE-2026-74663)

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

    packet: synchronize pressure clearing with ring reconfiguration (CVE-2026-74666)

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

    packet: use consistent hard_header_len in TX_RING send path (CVE-2026-74668)

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

    net: tap: set skb->dev before parsing virtio net header in tap_get_user_xdp() (CVE-2026-74684)

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

    net/sched: cls_api: Always acquire rtnl_lock when destroying locked classifiers (CVE-2026-74700)

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

    netfilter: flowtable: publish GC-visible tuple last (CVE-2026-74746)

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

    netfilter: ipset: fix refcount race between list:set GC and swap (CVE-2026-74748)

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

    ceph: fix hanging __ceph_get_caps() with stale mds_wanted (CVE-2026-80527)

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

    ceph: avoid fs reclaim while using current->journal_info (CVE-2026-80528)

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

    xfs: fix ilock leak on error in xfs_dq_get_next_id (CVE-2026-80534)

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

    xfs: bounds-check buffer log item's dirty bitmap (CVE-2026-80536)

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

    libceph: fix OOB read in decode_watchers() via missing bounds check (CVE-2026-80557)

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

    libceph: Avoid using invalid osd indices from primary_temp (CVE-2026-80558)

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

    libceph: fix multiple unsafe decodes in decode_locker() (CVE-2026-80561)

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

    mptcp: options: reset DSS fields in case of unexpected size (CVE-2026-80586)

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

    inet: frags: strip GSO state from fragments before reassembly (CVE-2026-80590)

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

    serial: amba-pl011: synchronize DMA teardown (CVE-2026-80737)

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

    af_packet: Don't send zero-byte data in tpacket_snd(). (CVE-2026-80742)

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

    netfilter: nf_tables_offload: suppress WARN_ON_ONCE for ENOMEM in abort path (CVE-2026-80744)

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

    selinux: do not cancel a policy conversion that never started (CVE-2026-80756)

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

    selinux: reject a class permission count below its inherited common (CVE-2026-80757)

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

    HID: hyperv: validate initial device info bounds (CVE-2026-80765)

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

    HID: core: fix OOB read of field->usage in hid_set_field() (CVE-2026-80781)

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

    ipv6: fix use-after-free in ip6_finish_output2() (CVE-2026-80792)

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

    ipv4: reject undersized MTUs in ip_do_fragment() (CVE-2026-80793)

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

    xfs: validate attr entry pointer before field access (CVE-2026-80805)

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

    ext4: stop retrying saturated xattr cache entries (CVE-2026-80808)

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

    rndis_host: add overflow check in rndis_rx_fixup() (CVE-2026-80814)

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

    net: packet: fix wrong transport_header when sending VLAN-tagged frame (CVE-2026-80906)

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

    selinux: require every boolean value to be defined (CVE-2026-80913)

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

    HID: core: fix number/pointer type confusion on long items (CVE-2026-80918)

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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - sctp: fix err_chunk memory leaks in INIT handling When sctp_verify_init() encounters unrecognized     parameters, it allocates an err_chunk to report them. However, this chunk is leaked in several code paths:
    1. In sctp_sf_do_5_1B_init(), if security_sctp_assoc_request() fails after sctp_verify_init() has     populated err_chunk, the function returns immediately without freeing it. 2. In     sctp_sf_do_unexpected_init(), the same leak occurs on the security_sctp_assoc_request() failure path. 3.
    In sctp_sf_do_unexpected_init(), on the success path after copying unrecognized parameters to the INIT-     ACK, the function returns without freeing err_chunk, unlike sctp_sf_do_5_1B_init() which properly frees     it. Fix all three leaks by adding sctp_chunk_free(err_chunk) calls before returning in the error paths and     on the success path in sctp_sf_do_unexpected_init(). (CVE-2026-72413)

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

ID	Name	Product	Family	Type	Severity
369489	CentOS Linux 7 [TuxCare] Security Update: bpftool / kernel / kernel-debug / kernel-debug-devel / kernel-devel / etc Multiple Vulnerabilities (CENTOS7:CLSA-2026:1792234299)	Nessus	CentOS Local Security Checks	Local	high
367921	CentOS Linux 6 [TuxCare] Security Update: kernel / kernel-abi-whitelists / kernel-debug / kernel-debug-devel / etc Multiple Vulnerabilities (CENTOS6:CLSA-2026:1791949745)	Nessus	CentOS Local Security Checks	Local	high
366919	Debian dla-4841 : ata-modules-6.1.0-53-armmp-di - security update	Nessus	Debian Local Security Checks	Local	high
366781	CentOS Linux 8 [TuxCare] Security Update: bpftool / kernel / kernel-core / kernel-cross-headers / etc Multiple Vulnerabilities (CENTOS-STREAM8:CLSA-2026:1792239979)	Nessus	CentOS Local Security Checks	Local	high
366749	SUSE SLES12: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2026:4687-1)	Nessus	SuSE Local Security Checks	Local	high
366742	SUSE SLED15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2026:4706-1)	Nessus	SuSE Local Security Checks	Local	high
365768	Ubuntu 26.04 LTS : Linux kernel (Azure) vulnerabilities (USN-8888-1)	Nessus	Ubuntu Local Security Checks	Local	medium
365767	Ubuntu 26.04 LTS : Linux kernel vulnerabilities (USN-8887-1)	Nessus	Ubuntu Local Security Checks	Local	medium
365463	Ubuntu 26.04 LTS : Linux kernel (OEM) vulnerabilities (USN-8889-1)	Nessus	Ubuntu Local Security Checks	Local	medium
365258	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-3192)	Nessus	Amazon Linux Local Security Checks	Local	medium
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
351061	Amazon Linux 2 : kernel (ALASKERNEL-5.10-2026-132)	Nessus	Amazon Linux Local Security Checks	Local	medium
345814	Amazon Linux 2023 : bpftool, kernel, kernel-devel (ALAS2023-2026-2143)	Nessus	Amazon Linux Local Security Checks	Local	medium
335742	Linux Distros Unpatched Vulnerability : CVE-2026-72413	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-72413

medium

Tenable Plugins

high

high

high

high

high

high

medium

medium

medium

medium

high

high

high

medium

medium

medium