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 tail_call_reachable rejection     for interpreter when jit failed During testing of f263a81451c1 (bpf: Track subprog poke descriptors     correctly and fix use-after-free) under various failure conditions, for example, when jit_subprogs()     fails and tries to clean up the program to be run under the interpreter, we ran into the following freeze:
    [...] #127/8 tailcall_bpf2bpf_3:FAIL [...] [ 92.041251] BUG: KASAN: slab-out-of-bounds in
    ___bpf_prog_run+0x1b9d/0x2e20 [ 92.042408] Read of size 8 at addr ffff88800da67f68 by task test_progs/682     [ 92.043707] [ 92.044030] CPU: 1 PID: 682 Comm: test_progs Tainted: G O 5.13.0-53301-ge6c08cb33a30-dirty     #87 [ 92.045542] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1 04/01/2014 [     92.046785] Call Trace: [ 92.047171] ? __bpf_prog_run_args64+0xc0/0xc0 [ 92.047773] ?
    __bpf_prog_run_args32+0x8b/0xb0 [ 92.048389] ? __bpf_prog_run_args64+0xc0/0xc0 [ 92.049019] ?     ktime_get+0x117/0x130 [...] // few hundred [similar] lines more [ 92.659025] ? ktime_get+0x117/0x130 [     92.659845] ? __bpf_prog_run_args64+0xc0/0xc0 [ 92.660738] ? __bpf_prog_run_args32+0x8b/0xb0 [ 92.661528] ?
    __bpf_prog_run_args64+0xc0/0xc0 [ 92.662378] ? print_usage_bug+0x50/0x50 [ 92.663221] ?     print_usage_bug+0x50/0x50 [ 92.664077] ? bpf_ksym_find+0x9c/0xe0 [ 92.664887] ? ktime_get+0x117/0x130 [     92.665624] ? kernel_text_address+0xf5/0x100 [ 92.666529] ? __kernel_text_address+0xe/0x30 [ 92.667725] ?     unwind_get_return_address+0x2f/0x50 [ 92.668854] ? ___bpf_prog_run+0x15d4/0x2e20 [ 92.670185] ?     ktime_get+0x117/0x130 [ 92.671130] ? __bpf_prog_run_args64+0xc0/0xc0 [ 92.672020] ?
    __bpf_prog_run_args32+0x8b/0xb0 [ 92.672860] ? __bpf_prog_run_args64+0xc0/0xc0 [ 92.675159] ?     ktime_get+0x117/0x130 [ 92.677074] ? lock_is_held_type+0xd5/0x130 [ 92.678662] ?
    ___bpf_prog_run+0x15d4/0x2e20 [ 92.680046] ? ktime_get+0x117/0x130 [ 92.681285] ?
    __bpf_prog_run32+0x6b/0x90 [ 92.682601] ? __bpf_prog_run64+0x90/0x90 [ 92.683636] ?     lock_downgrade+0x370/0x370 [ 92.684647] ? mark_held_locks+0x44/0x90 [ 92.685652] ? ktime_get+0x117/0x130 [     92.686752] ? lockdep_hardirqs_on+0x79/0x100 [ 92.688004] ? ktime_get+0x117/0x130 [ 92.688573] ?
    __cant_migrate+0x2b/0x80 [ 92.689192] ? bpf_test_run+0x2f4/0x510 [ 92.689869] ?     bpf_test_timer_continue+0x1c0/0x1c0 [ 92.690856] ? rcu_read_lock_bh_held+0x90/0x90 [ 92.691506] ?
    __kasan_slab_alloc+0x61/0x80 [ 92.692128] ? eth_type_trans+0x128/0x240 [ 92.692737] ?
    __build_skb+0x46/0x50 [ 92.693252] ? bpf_prog_test_run_skb+0x65e/0xc50 [ 92.693954] ?     bpf_prog_test_run_raw_tp+0x2d0/0x2d0 [ 92.694639] ? __fget_light+0xa1/0x100 [ 92.695162] ?     bpf_prog_inc+0x23/0x30 [ 92.695685] ? __sys_bpf+0xb40/0x2c80 [ 92.696324] ? bpf_link_get_from_fd+0x90/0x90     [ 92.697150] ? mark_held_locks+0x24/0x90 [ 92.698007] ? lockdep_hardirqs_on_prepare+0x124/0x220 [     92.699045] ? finish_task_switch+0xe6/0x370 [ 92.700072] ? lockdep_hardirqs_on+0x79/0x100 [ 92.701233] ?     finish_task_switch+0x11d/0x370 [ 92.702264] ? __switch_to+0x2c0/0x740 [ 92.703148] ?     mark_held_locks+0x24/0x90 [ 92.704155] ? __x64_sys_bpf+0x45/0x50 [ 92.705146] ? do_syscall_64+0x35/0x80 [     92.706953] ? entry_SYSCALL_64_after_hwframe+0x44/0xae [...] Turns out that the program rejection from     e411901c0b77 (bpf: allow for tailcalls in BPF subprograms for x64 JIT) is buggy since     env->prog->aux->tail_call_reachable is never true. Commit ebf7d1f508a7 (bpf, x64: rework pro/epilogue and     tailcall handling in JIT) added a tracker into check_max_stack_depth() which propagates the     tail_call_reachable condition throughout the subprograms. This info is then assigned to the subprogram's
    ---truncated--- (CVE-2021-47300)

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.10.59-52.142. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2022-004 advisory.

    A flaw was found in the Linux kernel, where a BPF program can obtain sensitive information from kernel     memory via a Speculative Store Bypass side-channel attack. This issue occurs when the protection mechanism     neglects the possibility of uninitialized memory locations on the BPF stack. The highest threat from this     vulnerability is to confidentiality. (CVE-2021-34556)

    A flaw in the Linux kernel allows a privileged BPF program to obtain sensitive information from kernel     memory via a Speculative Store Bypass side-channel in the eBPF subsystem (CVE-2021-35477)

    A vulnerability was found in the Linux kernel. Missing size validations on inbound SCTP packets may allow     the kernel to read uninitialized memory. (CVE-2021-3655)

    A lack of CPU resources in the Linux kernel tracing module functionality was found in the way users use     the trace ring buffer in specific way. Only privileged local users (with CAP_SYS_ADMIN capability) could     use this flaw to starve the resources causing denial of service. (CVE-2021-3679)

    A flaw use-after-free in the Linux kernel USB High Speed Mobile Devices functionality was found in the way     user detaches USB device. A local user could use this flaw to crash the system or escalate their     privileges on the system. (CVE-2021-37159)

    ** DISPUTED ** In drivers/char/virtio_console.c in the Linux kernel before 5.13.4, data corruption or loss     can be triggered by an untrusted device that supplies a buf->len value exceeding the buffer size. NOTE:
    the vendor indicates that the cited data corruption is not a vulnerability in any existing use case; the     length validation was added solely for robustness in the face of anomalous host OS behavior.
    (CVE-2021-38160)

    A flaw was found in the hanging of mounts in the Linux kernel's NFS4 subsystem where remote servers are     unreachable for the client during migration of data from one server to another (during trunking     detection). This flaw allows a remote NFS4 server (if the client is connected) to starve the resources,     causing a denial of service. The highest threat from this vulnerability is to system availability.
    (CVE-2021-38199)

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

    ACPI: fix NULL pointer dereference (CVE-2021-47289)

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

    ipv6: fix another slab-out-of-bounds in fib6_nh_flush_exceptions (CVE-2021-47291)

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

    net: sched: fix memory leak in tcindex_partial_destroy_work (CVE-2021-47295)

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

    bpf, sockmap: Fix potential memory leak on unlikely error case (CVE-2021-47298)

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

    xdp, net: Fix use-after-free in bpf_xdp_link_release (CVE-2021-47299)

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

    bpf: Fix tail_call_reachable rejection for interpreter when jit failed (CVE-2021-47300)

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

    igb: Fix use-after-free error during reset (CVE-2021-47301)

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

    bpf: Track subprog poke descriptors correctly and fix use-after-free (CVE-2021-47303)

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

    tcp: fix tcp_init_transfer() to not reset icsk_ca_initialized (CVE-2021-47304)

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

    dma-buf/sync_file: Don't leak fences on merge failure (CVE-2021-47305)

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

    cifs: prevent NULL deref in cifs_compose_mount_options() (CVE-2021-47307)

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

    scsi: libfc: Fix array index out of bound exception (CVE-2021-47308)

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

    net: validate lwtstate->data before returning from skb_tunnel_info() (CVE-2021-47309)

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

    net: qcom/emac: fix UAF in emac_remove (CVE-2021-47311)

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

    virtio-blk: Fix memory leak among suspend/resume procedure (CVE-2021-47319)

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

    nfs: fix acl memory leak of posix_acl_create() (CVE-2021-47320)

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

    NFSv4: Fix an Oops in pnfs_mark_request_commit() when doing O_DIRECT (CVE-2021-47322)

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

    iommu/arm-smmu: Fix arm_smmu_device refcount leak in address translation (CVE-2021-47325)

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

    iommu/arm-smmu: Fix arm_smmu_device refcount leak when arm_smmu_rpm_get fails (CVE-2021-47327)

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

    scsi: iscsi: Fix conn use after free during resets (CVE-2021-47328)

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

    scsi: megaraid_sas: Fix resource leak in case of probe failure (CVE-2021-47329)

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

    fbmem: Do not delete the mode that is still in use (CVE-2021-47338)

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

    jfs: fix GPF in diFree (CVE-2021-47340)

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

    KVM: mmio: Fix use-after-free Read in kvm_vm_ioctl_unregister_coalesced_mmio (CVE-2021-47341)

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

    dm btree remove: assign new_root only when removal succeeds (CVE-2021-47343)

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

    RDMA/cma: Fix rdma_resolve_route() memory leak (CVE-2021-47345)

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

    virtio-net: Add validation for used length (CVE-2021-47352)

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

    udf: Fix NULL pointer dereference in udf_symlink function (CVE-2021-47353)

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

    drm/sched: Avoid data corruptions (CVE-2021-47354)

    An issue was discovered in the Linux kernel before 5.13.3. lib/seq_buf.c has a seq_buf_putmem_hex buffer     overflow. (CVE-2023-28772)

    A flaw was found in the Linux Kernel's memory management subsytem. In this flaw, A task is exiting and     releasing 2MB page in a vma (vm_area_struct) and hits the BUG statement in pfn_swap_entry_to_page()     referencing pmd_t x. This may allow a local user to crash the Linux kernel. (CVE-2023-4732)

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 Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-986712 advisory.

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

    bpf: Fix tail_call_reachable rejection for interpreter when jit failed

    During testing of f263a81451c1 (bpf: Track subprog poke descriptors correctly     and fix use-after-free) under various failure conditions, for example, when     jit_subprogs() fails and tries to clean up the program to be run under the     interpreter, we ran into the following freeze:

      [...]       #127/8 tailcall_bpf2bpf_3:FAIL       [...]       [   92.041251] BUG: KASAN: slab-out-of-bounds in ___bpf_prog_run+0x1b9d/0x2e20       [   92.042408] Read of size 8 at addr ffff88800da67f68 by task test_progs/682       [   92.043707]       [   92.044030] CPU: 1 PID: 682 Comm: test_progs Tainted: G   O   5.13.0-53301-ge6c08cb33a30-dirty #87       [   92.045542] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1 04/01/2014       [   92.046785] Call Trace:
      [   92.047171]  ? __bpf_prog_run_args64+0xc0/0xc0       [   92.047773]  ? __bpf_prog_run_args32+0x8b/0xb0       [   92.048389]  ? __bpf_prog_run_args64+0xc0/0xc0       [   92.049019]  ? ktime_get+0x117/0x130       [...] // few hundred [similar] lines more       [   92.659025]  ? ktime_get+0x117/0x130       [   92.659845]  ? __bpf_prog_run_args64+0xc0/0xc0       [   92.660738]  ? __bpf_prog_run_args32+0x8b/0xb0       [   92.661528]  ? __bpf_prog_run_args64+0xc0/0xc0       [   92.662378]  ? print_usage_bug+0x50/0x50       [   92.663221]  ? print_usage_bug+0x50/0x50       [   92.664077]  ? bpf_ksym_find+0x9c/0xe0       [   92.664887]  ? ktime_get+0x117/0x130       [   92.665624]  ? kernel_text_address+0xf5/0x100       [   92.666529]  ? __kernel_text_address+0xe/0x30       [   92.667725]  ? unwind_get_return_address+0x2f/0x50       [   92.668854]  ? ___bpf_prog_run+0x15d4/0x2e20       [   92.670185]  ? ktime_get+0x117/0x130       [   92.671130]  ? __bpf_prog_run_args64+0xc0/0xc0       [   92.672020]  ? __bpf_prog_run_args32+0x8b/0xb0       [   92.672860]  ? __bpf_prog_run_args64+0xc0/0xc0       [   92.675159]  ? ktime_get+0x117/0x130       [   92.677074]  ? lock_is_held_type+0xd5/0x130       [   92.678662]  ? ___bpf_prog_run+0x15d4/0x2e20       [   92.680046]  ? ktime_get+0x117/0x130       [   92.681285]  ? __bpf_prog_run32+0x6b/0x90       [   92.682601]  ? __bpf_prog_run64+0x90/0x90       [   92.683636]  ? lock_downgrade+0x370/0x370       [   92.684647]  ? mark_held_locks+0x44/0x90       [   92.685652]  ? ktime_get+0x117/0x130       [   92.686752]  ? lockdep_hardirqs_on+0x79/0x100       [   92.688004]  ? ktime_get+0x117/0x130       [   92.688573]  ? __cant_migrate+0x2b/0x80       [   92.689192]  ? bpf_test_run+0x2f4/0x510       [   92.689869]  ? bpf_test_timer_continue+0x1c0/0x1c0       [   92.690856]  ? rcu_read_lock_bh_held+0x90/0x90       [   92.691506]  ? __kasan_slab_alloc+0x61/0x80       [   92.692128]  ? eth_type_trans+0x128/0x240       [   92.692737]  ? __build_skb+0x46/0x50       [   92.693252]  ? bpf_prog_test_run_skb+0x65e/0xc50       [   92.693954]  ? bpf_prog_test_run_raw_tp+0x2d0/0x2d0       [   92.694639]  ? __fget_light+0xa1/0x100       [   92.695162]  ? bpf_prog_inc+0x23/0x30       [   92.695685]  ? __sys_bpf+0xb40/0x2c80       [   92.696324]  ? bpf_link_get_from_fd+0x90/0x90       [   92.697150]  ? mark_held_locks+0x24/0x90       [   92.698007]  ? lockdep_hardirqs_on_prepare+0x124/0x220       [   92.699045]  ? finish_task_switch+0xe6/0x370       [   92.700072]  ? lockdep_hardirqs_on+0x79/0x100       [   92.701233]  ? finish_task_switch+0x11d/0x370       [   92.702264]  ? __switch_to+0x2c0/0x740       [   92.703148]  ? mark_held_locks+0x24/0x90       [   92.704155]  ? __x64_sys_bpf+0x45/0x50       [   92.705146]  ? do_syscall_64+0x35/0x80       [   92.706953]  ? entry_SYSCALL_64_after_hwframe+0x44/0xae       [...]

    Turns out that the program rejection from e411901c0b77 (bpf: allow for tailcalls     in BPF subprograms for x64 JIT) is buggy since env->prog->aux->tail_call_reachable     is never true. Commit ebf7d1f508a7 (bpf, x64: rework pro/epilogue and tailcall     handling in JIT) added a tracker into check_max_stack_depth() which propagates     the tail_call_reachable condition throughout the subprograms. This info is then     assigned to the subprogram's
    ---truncated---

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-988725 advisory.

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

    bpf: Fix tail_call_reachable rejection for interpreter when jit failed

    During testing of f263a81451c1 (bpf: Track subprog poke descriptors correctly     and fix use-after-free) under various failure conditions, for example, when     jit_subprogs() fails and tries to clean up the program to be run under the     interpreter, we ran into the following freeze:

      [...]       #127/8 tailcall_bpf2bpf_3:FAIL       [...]       [   92.041251] BUG: KASAN: slab-out-of-bounds in ___bpf_prog_run+0x1b9d/0x2e20       [   92.042408] Read of size 8 at addr ffff88800da67f68 by task test_progs/682       [   92.043707]       [   92.044030] CPU: 1 PID: 682 Comm: test_progs Tainted: G   O   5.13.0-53301-ge6c08cb33a30-dirty #87       [   92.045542] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1 04/01/2014       [   92.046785] Call Trace:
      [   92.047171]  ? __bpf_prog_run_args64+0xc0/0xc0       [   92.047773]  ? __bpf_prog_run_args32+0x8b/0xb0       [   92.048389]  ? __bpf_prog_run_args64+0xc0/0xc0       [   92.049019]  ? ktime_get+0x117/0x130       [...] // few hundred [similar] lines more       [   92.659025]  ? ktime_get+0x117/0x130       [   92.659845]  ? __bpf_prog_run_args64+0xc0/0xc0       [   92.660738]  ? __bpf_prog_run_args32+0x8b/0xb0       [   92.661528]  ? __bpf_prog_run_args64+0xc0/0xc0       [   92.662378]  ? print_usage_bug+0x50/0x50       [   92.663221]  ? print_usage_bug+0x50/0x50       [   92.664077]  ? bpf_ksym_find+0x9c/0xe0       [   92.664887]  ? ktime_get+0x117/0x130       [   92.665624]  ? kernel_text_address+0xf5/0x100       [   92.666529]  ? __kernel_text_address+0xe/0x30       [   92.667725]  ? unwind_get_return_address+0x2f/0x50       [   92.668854]  ? ___bpf_prog_run+0x15d4/0x2e20       [   92.670185]  ? ktime_get+0x117/0x130       [   92.671130]  ? __bpf_prog_run_args64+0xc0/0xc0       [   92.672020]  ? __bpf_prog_run_args32+0x8b/0xb0       [   92.672860]  ? __bpf_prog_run_args64+0xc0/0xc0       [   92.675159]  ? ktime_get+0x117/0x130       [   92.677074]  ? lock_is_held_type+0xd5/0x130       [   92.678662]  ? ___bpf_prog_run+0x15d4/0x2e20       [   92.680046]  ? ktime_get+0x117/0x130       [   92.681285]  ? __bpf_prog_run32+0x6b/0x90       [   92.682601]  ? __bpf_prog_run64+0x90/0x90       [   92.683636]  ? lock_downgrade+0x370/0x370       [   92.684647]  ? mark_held_locks+0x44/0x90       [   92.685652]  ? ktime_get+0x117/0x130       [   92.686752]  ? lockdep_hardirqs_on+0x79/0x100       [   92.688004]  ? ktime_get+0x117/0x130       [   92.688573]  ? __cant_migrate+0x2b/0x80       [   92.689192]  ? bpf_test_run+0x2f4/0x510       [   92.689869]  ? bpf_test_timer_continue+0x1c0/0x1c0       [   92.690856]  ? rcu_read_lock_bh_held+0x90/0x90       [   92.691506]  ? __kasan_slab_alloc+0x61/0x80       [   92.692128]  ? eth_type_trans+0x128/0x240       [   92.692737]  ? __build_skb+0x46/0x50       [   92.693252]  ? bpf_prog_test_run_skb+0x65e/0xc50       [   92.693954]  ? bpf_prog_test_run_raw_tp+0x2d0/0x2d0       [   92.694639]  ? __fget_light+0xa1/0x100       [   92.695162]  ? bpf_prog_inc+0x23/0x30       [   92.695685]  ? __sys_bpf+0xb40/0x2c80       [   92.696324]  ? bpf_link_get_from_fd+0x90/0x90       [   92.697150]  ? mark_held_locks+0x24/0x90       [   92.698007]  ? lockdep_hardirqs_on_prepare+0x124/0x220       [   92.699045]  ? finish_task_switch+0xe6/0x370       [   92.700072]  ? lockdep_hardirqs_on+0x79/0x100       [   92.701233]  ? finish_task_switch+0x11d/0x370       [   92.702264]  ? __switch_to+0x2c0/0x740       [   92.703148]  ? mark_held_locks+0x24/0x90       [   92.704155]  ? __x64_sys_bpf+0x45/0x50       [   92.705146]  ? do_syscall_64+0x35/0x80       [   92.706953]  ? entry_SYSCALL_64_after_hwframe+0x44/0xae       [...]

    Turns out that the program rejection from e411901c0b77 (bpf: allow for tailcalls     in BPF subprograms for x64 JIT) is buggy since env->prog->aux->tail_call_reachable     is never true. Commit ebf7d1f508a7 (bpf, x64: rework pro/epilogue and tailcall     handling in JIT) added a tracker into check_max_stack_depth() which propagates     the tail_call_reachable condition throughout the subprograms. This info is then     assigned to the subprogram's
    ---truncated---

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

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

ID	Name	Product	Family	Published	Updated	Severity
224302	Linux Distros Unpatched Vulnerability : CVE-2021-47300	Nessus	Misc.	3/5/2025	9/4/2025	medium
160434	Amazon Linux 2 : kernel (ALASKERNEL-5.10-2022-004)	Nessus	Amazon Linux Local Security Checks	5/2/2022	2/26/2026	high
268024	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-986712)	Nessus	Unity Linux Local Security Checks	10/7/2025	10/15/2025	medium
273611	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-988725)	Nessus	Unity Linux Local Security Checks	11/5/2025	11/5/2025	medium

Detections

Analytics

Plugins Search

medium

high

medium

medium