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

  - bpf: Fix reference state management for synchronous callbacks Currently, verifier verifies callback     functions (sync and async) as if they will be executed once, (i.e. it explores execution state as if the     function was being called once). The next insn to explore is set to start of subprog and the exit from     nested frame is handled using curframe > 0 and prepare_func_exit. In case of async callback it uses a     customized variant of push_stack simulating a kind of branch to set up custom state and execution context     for the async callback. While this approach is simple and works when callback really will be executed only     once, it is unsafe for all of our current helpers which are for_each style, i.e. they execute the callback     multiple times. A callback releasing acquired references of the caller may do so multiple times, but     currently verifier sees it as one call inside the frame, which then returns to caller. Hence, it thinks it     released some reference that the cb e.g. got access through callback_ctx (register filled inside cb from     spilled typed register on stack). Similarly, it may see that an acquire call is unpaired inside the     callback, so the caller will copy the reference state of callback and then will have to release the     register with new ref_obj_ids. But again, the callback may execute multiple times, but the verifier will     only account for acquired references for a single symbolic execution of the callback, which will cause     leaks. Note that for async callback case, things are different. While currently we have     bpf_timer_set_callback which only executes it once, even for multiple executions it would be safe, as     reference state is NULL and check_reference_leak would force program to release state before BPF_EXIT. The     state is also unaffected by analysis for the caller frame. Hence async callback is safe. Since we want the     reference state to be accessible, e.g. for pointers loaded from stack through callback_ctx's PTR_TO_STACK,     we still have to copy caller's reference_state to callback's bpf_func_state, but we enforce that whatever     references it adds to that reference_state has been released before it hits BPF_EXIT. This requires     introducing a new callback_ref member in the reference state to distinguish between caller vs callee     references. Hence, check_reference_leak now errors out if it sees we are in callback_fn and we have not     released callback_ref refs. Since there can be multiple nested callbacks, like frame 0 -> cb1 -> cb2 etc.
    we need to also distinguish between whether this particular ref belongs to this callback frame or parent,     and only error for our own, so we store state->frameno (which is always non-zero for callbacks). In short,     callbacks can read parent reference_state, but cannot mutate it, to be able to use pointers acquired by     the caller. They must only undo their changes (by releasing their own acquired_refs before BPF_EXIT) on     top of caller reference_state before returning (at which point the caller and callback state will match     anyway, so no need to copy it back to caller). (CVE-2022-50650)

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

The version of kernel installed on the remote host is prior to 5.15.75-48.135. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2025-090 advisory.

    A vulnerability, which was classified as problematic, has been found in Linux Kernel. This issue affects     the function nilfs_attach_log_writer of the file fs/nilfs2/segment.c of the component BPF. The     manipulation leads to memory leak. The attack may be initiated remotely. It is recommended to apply a     patch to fix this issue. The identifier VDB-211961 was assigned to this vulnerability. (CVE-2022-3646)

    drivers/scsi/stex.c in the Linux kernel through 5.19.9 allows local users to obtain sensitive information     from kernel memory because stex_queuecommand_lck lacks a memset for the PASSTHRU_CMD case.
    (CVE-2022-40768)

    The Linux kernel NFSD implementation prior to versions 5.19.17 and 6.0.2 are vulnerable to buffer     overflow. NFSD tracks the number of pages held by each NFSD thread by combining the receive and send     buffers of a remote procedure call (RPC) into a single array of pages. A client can force the send buffer     to shrink by sending an RPC message over TCP with garbage data added at the end of the message. The RPC     message with garbage data is still correctly formed according to the specification and is passed forward     to handlers. Vulnerable code in NFSD is not expecting the oversized request and writes beyond the     allocated buffer space. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (CVE-2022-43945)

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

    NFSD: Protect against send buffer overflow in NFSv2 READDIR (CVE-2022-50235)

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

    NFSD: fix use-after-free on source server when doing inter-server copy (CVE-2022-50241)

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

    sctp: handle the error returned from sctp_auth_asoc_init_active_key (CVE-2022-50243)

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

    xen/gntdev: Prevent leaking grants (CVE-2022-50257)

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

    vhost/vsock: Use kvmalloc/kvfree for larger packets. (CVE-2022-50271)

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

    md: Replace snprintf with scnprintf (CVE-2022-50299)

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

    nbd: Fix hung when signal interrupts nbd_start_device_ioctl() (CVE-2022-50314)

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

    jbd2: fix potential use-after-free in jbd2_fc_wait_bufs (CVE-2022-50328)

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

    ext4: fix null-ptr-deref in ext4_write_info (CVE-2022-50344)

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

    NFSD: Protect against send buffer overflow in NFSv3 READ (CVE-2022-50345)

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

    nfsd: Fix a memory leak in an error handling path (CVE-2022-50348)

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

    btrfs: fix race between quota enable and quota rescan ioctl (CVE-2022-50379)

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

    net/ieee802154: reject zero-sized raw_sendmsg() (CVE-2022-50397)

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

    net: If sock is dead don't access sock's sk_wq in sk_stream_wait_memory (CVE-2022-50409)

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

    NFSD: Protect against send buffer overflow in NFSv2 READ (CVE-2022-50410)

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

    scsi: libsas: Fix use-after-free bug in smp_execute_task_sg() (CVE-2022-50422)

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

    ext4: avoid crash when inline data creation follows DIO write (CVE-2022-50435)

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

    xfrm: Reinject transport-mode packets through workqueue (CVE-2022-50445)

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

    xen/gntdev: Accommodate VMA splitting (CVE-2022-50471)

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

    drm/mipi-dsi: Detach devices when removing the host (CVE-2022-50489)

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

    bpf: Propagate error from htab_lock_bucket() to userspace (CVE-2022-50490)

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

    ext4: fix potential memory leak in ext4_fc_record_regions() (CVE-2022-50512)

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

    usb: host: xhci: Fix potential memory leak in xhci_alloc_stream_info() (CVE-2022-50544)

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

    xfrm: Update ipcomp_scratches with NULL when freed (CVE-2022-50569)

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

    arm64: ftrace: fix module PLTs with mcount (CVE-2022-50579)

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

    blk-throttle: prevent overflow while calculating wait time (CVE-2022-50580)

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

    ext4: fix potential memory leak in ext4_fc_record_modified_inode() (CVE-2022-50622)

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

    mm: hugetlb: fix UAF in hugetlb_handle_userfault (CVE-2022-50630)

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

    io-wq: Fix memory leak in worker creation (CVE-2022-50639)

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

    bpf: Fix reference state management for synchronous callbacks (CVE-2022-50650)

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

    RDMA/siw: Fix QP destroy to wait for all references dropped. (CVE-2022-50666)

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

    net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks() (CVE-2022-50676)

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

    net/ieee802154: don't warn zero-sized raw_sendmsg() (CVE-2022-50706)

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

    crypto: akcipher - default implementation for setting a private key (CVE-2022-50731)

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

    md/raid5: Remove unnecessary bio_put() in raid5_read_one_chunk() (CVE-2022-50752)

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

    btrfs: set generation before calling btrfs_clean_tree_block in btrfs_init_new_buffer (CVE-2022-50766)

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

    jbd2: add miss release buffer head in fc_do_one_pass() (CVE-2022-50835)

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

    jbd2: fix potential buffer head reference count leak (CVE-2022-50839)

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

    cifs: Fix the error length of VALIDATE_NEGOTIATE_INFO message (CVE-2022-50859)

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

    drm: Prevent drm_copy_field() to attempt copying a NULL pointer (CVE-2022-50884)

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.

ID	Name	Product	Family	Published	Updated	Severity
278044	Linux Distros Unpatched Vulnerability : CVE-2022-50650	Nessus	Misc.	12/10/2025	2/4/2026	high
266163	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2025-090 (ALASKERNEL-5.15-2025-090)	Nessus	Amazon Linux Local Security Checks	9/30/2025	2/9/2026	high

Detections

Analytics

Plugins Search

high

high