In the Linux kernel, the following vulnerability has been resolved: bpf: Fix unsound scalar forking in maybe_fork_scalars() for BPF_OR maybe_fork_scalars() is called for both BPF_AND and BPF_OR when the source operand is a constant. When dst has signed range [-1, 0], it forks the verifier state: the pushed path gets dst = 0, the current path gets dst = -1. For BPF_AND this is correct: 0 & K == 0. For BPF_OR this is wrong: 0 | K == K, not 0. The pushed path therefore tracks dst as 0 when the runtime value is K, producing an exploitable verifier/runtime divergence that allows out-of-bounds map access. Fix this by passing env->insn_idx (instead of env->insn_idx + 1) to push_stack(), so the pushed path re-executes the ALU instruction with dst = 0 and naturally computes the correct result for any opcode.

The remote Oracle Linux 10 / 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2026-50260 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: ipv6: use RCU in ip6_xmit() Use RCU in     ip6_xmit() in order to use dst_dev_rcu() to prevent possible UAF. (CVE-2025-40135)

  - This vulnerability was found and addressed by AMD. We are documenting it in the Security Update Guide to     encourage customers to install the May 2026 version of Windows as soon as possible. The vulnerability     assigned to this CVE is in certain processor models offered by AMD. The mitigation for this vulnerability     requires a Windows update. This CVE is being documented in the Security Update Guide to announce that the     latest builds of Windows enable the mitigation and provide protection against the vulnerability. Please     see the following for more information: AMD-SB-7052 (CVE-2025-54518)

  - In the Linux kernel, the following vulnerability has been resolved: dst: fix races in     rt6_uncached_list_del() and rt_del_uncached_list() syzbot was able to crash the kernel in     rt6_uncached_list_flush_dev() in an interesting way [1] Crash happens in list_del_init()/INIT_LIST_HEAD()     while writing list->prev, while the prior write on list->next went well. static inline void     INIT_LIST_HEAD(struct list_head *list) { WRITE_ONCE(list->next, list); // This went well     WRITE_ONCE(list->prev, list); // Crash, @list has been freed. } Issue here is that rt6_uncached_list_del()     did not attempt to lock ul->lock, as list_empty(&rt->dst.rt_uncached) returned true because the     WRITE_ONCE(list->next, list) happened on the other CPU. We might use list_del_init_careful() and     list_empty_careful(), or make sure rt6_uncached_list_del() always grabs the spinlock whenever     rt->dst.rt_uncached_list has been set. A similar fix is neeed for IPv4. [1] BUG: KASAN: slab-use-after-     free in INIT_LIST_HEAD include/linux/list.h:46 [inline] BUG: KASAN: slab-use-after-free in list_del_init     include/linux/list.h:296 [inline] BUG: KASAN: slab-use-after-free in rt6_uncached_list_flush_dev     net/ipv6/route.c:191 [inline] BUG: KASAN: slab-use-after-free in rt6_disable_ip+0x633/0x730     net/ipv6/route.c:5020 Write of size 8 at addr ffff8880294cfa78 by task kworker/u8:14/3450 CPU: 0 UID: 0     PID: 3450 Comm: kworker/u8:14 Tainted: G L syzkaller #0 PREEMPT_{RT,(full)} Tainted: [L]=SOFTLOCKUP     Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Workqueue: netns     cleanup_net Call Trace: <TASK> dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_address_description     mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150     mm/kasan/report.c:595 INIT_LIST_HEAD include/linux/list.h:46 [inline] list_del_init     include/linux/list.h:296 [inline] rt6_uncached_list_flush_dev net/ipv6/route.c:191 [inline]     rt6_disable_ip+0x633/0x730 net/ipv6/route.c:5020 addrconf_ifdown+0x143/0x18a0 net/ipv6/addrconf.c:3853     addrconf_notify+0x1bc/0x1050 net/ipv6/addrconf.c:-1 notifier_call_chain+0x19d/0x3a0 kernel/notifier.c:85     call_netdevice_notifiers_extack net/core/dev.c:2268 [inline] call_netdevice_notifiers net/core/dev.c:2282     [inline] netif_close_many+0x29c/0x410 net/core/dev.c:1785 unregister_netdevice_many_notify+0xb50/0x2330     net/core/dev.c:12353 ops_exit_rtnl_list net/core/net_namespace.c:187 [inline] ops_undo_list+0x3dc/0x990     net/core/net_namespace.c:248 cleanup_net+0x4de/0x7b0 net/core/net_namespace.c:696 process_one_work     kernel/workqueue.c:3257 [inline] process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340     worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421 kthread+0x711/0x8a0 kernel/kthread.c:463     ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30     arch/x86/entry/entry_64.S:246 </TASK> Allocated by task 803: kasan_save_stack mm/kasan/common.c:57     [inline] kasan_save_track+0x3e/0x80 mm/kasan/common.c:78 unpoison_slab_object mm/kasan/common.c:340     [inline] __kasan_slab_alloc+0x6c/0x80 mm/kasan/common.c:366 kasan_slab_alloc include/linux/kasan.h:253     [inline] slab_post_alloc_hook mm/slub.c:4953 [inline] slab_alloc_node mm/slub.c:5263 [inline]     kmem_cache_alloc_noprof+0x18d/0x6c0 mm/slub.c:5270 dst_alloc+0x105/0x170 net/core/dst.c:89 ip6_dst_alloc     net/ipv6/route.c:342 [inline] icmp6_dst_alloc+0x75/0x460 net/ipv6/route.c:3333 mld_sendpack+0x683/0xe60     net/ipv6/mcast.c:1844 mld_send_cr net/ipv6/mcast.c:2154 [inline] mld_ifc_work+0x83e/0xd60     net/ipv6/mcast.c:2693 process_one_work kernel/workqueue.c:3257 [inline]     process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340 worker_thread+0x8a0/0xda0     kernel/workqueue.c:3421 kthread+0x711/0x8a0 kernel/kthread.c:463 ret_from_fork+0x510/0xa50     arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entr ---truncated---     (CVE-2026-23004)

  - In the Linux kernel, the following vulnerability has been resolved: tls: Fix race condition in     tls_sw_cancel_work_tx() This issue was discovered during a code audit. After cancel_delayed_work_sync() is     called from tls_sk_proto_close(), tx_work_handler() can still be scheduled from paths such as the Delayed     ACK handler or ksoftirqd. As a result, the tx_work_handler() worker may dereference a freed TLS object.
    The following is a simple race scenario: cpu0 cpu1 tls_sk_proto_close() tls_sw_cancel_work_tx()     tls_write_space() tls_sw_write_space() if (!test_and_set_bit(BIT_TX_SCHEDULED, &tx_ctx->tx_bitmask))     set_bit(BIT_TX_SCHEDULED, &ctx->tx_bitmask); cancel_delayed_work_sync(&ctx->tx_work.work);
    schedule_delayed_work(&tx_ctx->tx_work.work, 0); To prevent this race condition,     cancel_delayed_work_sync() is replaced with disable_delayed_work_sync(). (CVE-2026-23240)

  - In the Linux kernel, the following vulnerability has been resolved: RDMA/umad: Reject negative data_len in     ib_umad_write ib_umad_write computes data_len from user-controlled count and the MAD header sizes. With a     mismatched user MAD header size and RMPP header length, data_len can become negative and reach     ib_create_send_mad(). This can make the padding calculation exceed the segment size and trigger an out-of-     bounds memset in alloc_send_rmpp_list(). Add an explicit check to reject negative data_len before creating     the send buffer. KASAN splat: [ 211.363464] BUG: KASAN: slab-out-of-bounds in     ib_create_send_mad+0xa01/0x11b0 [ 211.364077] Write of size 220 at addr ffff88800c3fa1f8 by task     spray_thread/102 [ 211.365867] ib_create_send_mad+0xa01/0x11b0 [ 211.365887] ib_umad_write+0x853/0x1c80     (CVE-2026-23243)

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-1646 advisory.

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

    landlock: Fix handling of disconnected directories (CVE-2025-68736)

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

    arm64/fpsimd: signal: Fix restoration of SVE context (CVE-2026-23102)

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

    spi: tegra210-quad: Protect curr_xfer check in IRQ handler (CVE-2026-23207)

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

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

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

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

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

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

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

    bpf: Fix constant blinding for PROBE_MEM32 stores (CVE-2026-23417)

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

    xfrm: Fix work re-schedule after cancel in xfrm_nat_keepalive_net_fini() (CVE-2026-31406)

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

    bpf: Fix unsound scalar forking in maybe_fork_scalars() for BPF_OR (CVE-2026-31413)

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

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

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

    netfilter: nf_conntrack_sip: fix use of uninitialized rtp_addr in process_sdp (CVE-2026-31427)

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

    netfilter: nfnetlink_log: fix uninitialized padding leak in NFULA_PAYLOAD (CVE-2026-31428)

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

    btrfs: fix leak of kobject name for sub-group space_info (CVE-2026-31434)

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

    netfs: Fix kernel BUG in netfs_limit_iter() for ITER_KVEC iterators (CVE-2026-31438)

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

    ext4: fix use-after-free in update_super_work when racing with umount (CVE-2026-31446)

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

    ext4: reject mount if bigalloc with s_first_data_block != 0 (CVE-2026-31447)

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

    ext4: avoid infinite loops caused by residual data (CVE-2026-31448)

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

    ext4: validate p_idx bounds in ext4_ext_correct_indexes (CVE-2026-31449)

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

    ext4: replace BUG_ON with proper error handling in ext4_read_inline_folio (CVE-2026-31451)

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

    ext4: convert inline data to extents when truncate exceeds inline size (CVE-2026-31452)

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

    xfs: avoid dereferencing log items after push callbacks (CVE-2026-31453)

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

    xfs: save ailp before dropping the AIL lock in push callbacks (CVE-2026-31454)

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

    xfs: stop reclaim before pushing AIL during unmount (CVE-2026-31455)

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

    mm/damon/sysfs: check contexts->nr before accessing contexts_arr[0] (CVE-2026-31458)

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

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

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

    virtio_net: Fix UAF on dst_ops when IFF_XMIT_DST_RELEASE is cleared and napi_tx is false (CVE-2026-31469)

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

    virt: tdx-guest: Fix handling of host controlled 'quote' buffer length (CVE-2026-31470)

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

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

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

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

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

    spi: use generic driver_override infrastructure (CVE-2026-31487)

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

    RDMA/irdma: Initialize free_qp completion before using it (CVE-2026-31492)

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

    netfilter: ctnetlink: use netlink policy range checks (CVE-2026-31495)

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

    netfilter: nf_conntrack_expect: skip expectations in other netns via proc (CVE-2026-31496)

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

    team: fix header_ops type confusion with non-Ethernet ports (CVE-2026-31502)

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

    udp: Fix wildcard bind conflict check when using hash2 (CVE-2026-31503)

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

    net: fix fanout UAF in packet_release() via NETDEV_UP race (CVE-2026-31504)

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

    net: openvswitch: Avoid releasing netdev before teardown completes (CVE-2026-31508)

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

    erofs: set fileio bio failed in short read case (CVE-2026-31514)

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

    af_key: validate families in pfkey_send_migrate() (CVE-2026-31515)

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

    xfrm: prevent policy_hthresh.work from racing with netns teardown (CVE-2026-31516)

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

    esp: fix skb leak with espintcp and async crypto (CVE-2026-31518)

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

    btrfs: set BTRFS_ROOT_ORPHAN_CLEANUP during subvol create (CVE-2026-31519)

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

    module: Fix kernel panic when a symbol st_shndx is out of bounds (CVE-2026-31521)

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

    nvme-pci: ensure we're polling a polled queue (CVE-2026-31523)

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

    HID: asus: avoid memory leak in asus_report_fixup() (CVE-2026-31524)

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

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

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

    driver core: platform: use generic driver_override infrastructure (CVE-2026-31527)

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

    perf: Make sure to use pmu_ctx->pmu for groups (CVE-2026-31528)

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

    futex: Require sys_futex_requeue() to have identical flags (CVE-2026-31554)

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

    futex: Clear stale exiting pointer in futex_lock_pi() retry path (CVE-2026-31555)

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

    x86/cpu: Remove X86_CR4_FRED from the CR4 pinned bits mask (CVE-2026-31561)

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

    can: gw: fix OOB heap access in cgw_csum_crc8_rel() (CVE-2026-31570)

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

    netfilter: ip6t_rt: reject oversized addrnr in rt_mt6_check() (CVE-2026-31674)

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

    openvswitch: defer tunnel netdev_put to RCU release (CVE-2026-31678)

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

    openvswitch: validate MPLS set/set_masked payload length (CVE-2026-31679)

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

    xfs: don't irele after failing to iget in xfs_attri_recover_work (CVE-2026-43063)

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

    ext4: always drain queued discard work in ext4_mb_release() (CVE-2026-43065)

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

    ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths (CVE-2026-43066)

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

    ext4: handle wraparound when searching for blocks for indirect mapped blocks (CVE-2026-43067)

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

    ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal() (CVE-2026-43068)

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.

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Fix unsound scalar forking in     maybe_fork_scalars() for BPF_OR maybe_fork_scalars() is called for both BPF_AND and BPF_OR when the source     operand is a constant. When dst has signed range [-1, 0], it forks the verifier state: the pushed path     gets dst = 0, the current path gets dst = -1. For BPF_AND this is correct: 0 & K == 0. For BPF_OR this is     wrong: 0 | K == K, not 0. The pushed path therefore tracks dst as 0 when the runtime value is K, producing     an exploitable verifier/runtime divergence that allows out-of-bounds map access. Fix this by passing     env->insn_idx (instead of env->insn_idx + 1) to push_stack(), so the pushed path re-executes the ALU     instruction with dst = 0 and naturally computes the correct result for any opcode. (CVE-2026-31413)

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

ID	Name	Product	Family	Severity
316948	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-1746)	Nessus	Amazon Linux Local Security Checks	high
314333	Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2026-50260)	Nessus	Oracle Linux Local Security Checks	high
312152	Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2026-1646)	Nessus	Amazon Linux Local Security Checks	high
306374	Linux Distros Unpatched Vulnerability : CVE-2026-31413	Nessus	Misc.	high

Detections

Analytics

CVE-2026-31413

high

Tenable Plugins

high

high

high

high