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

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

    bpf: Prevent decl_tag from being referenced in func_proto arg

    Syzkaller managed to hit another decl_tag issue:

      btf_func_proto_check kernel/bpf/btf.c:4506 [inline]       btf_check_all_types kernel/bpf/btf.c:4734 [inline]       btf_parse_type_sec+0x1175/0x1980 kernel/bpf/btf.c:4763       btf_parse kernel/bpf/btf.c:5042 [inline]       btf_new_fd+0x65a/0xb00 kernel/bpf/btf.c:6709       bpf_btf_load+0x6f/0x90 kernel/bpf/syscall.c:4342
      __sys_bpf+0x50a/0x6c0 kernel/bpf/syscall.c:5034
      __do_sys_bpf kernel/bpf/syscall.c:5093 [inline]
      __se_sys_bpf kernel/bpf/syscall.c:5091 [inline]
      __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5091       do_syscall_64+0x54/0x70 arch/x86/entry/common.c:48

    This seems similar to commit ea68376c8bed (bpf: prevent decl_tag from being     referenced in func_proto) but for the argument.

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-2026-013623 advisory.

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

    bpf: Prevent decl_tag from being referenced in func_proto arg

    Syzkaller managed to hit another decl_tag issue:

      btf_func_proto_check kernel/bpf/btf.c:4506 [inline]       btf_check_all_types kernel/bpf/btf.c:4734 [inline]       btf_parse_type_sec+0x1175/0x1980 kernel/bpf/btf.c:4763       btf_parse kernel/bpf/btf.c:5042 [inline]       btf_new_fd+0x65a/0xb00 kernel/bpf/btf.c:6709       bpf_btf_load+0x6f/0x90 kernel/bpf/syscall.c:4342
      __sys_bpf+0x50a/0x6c0 kernel/bpf/syscall.c:5034
      __do_sys_bpf kernel/bpf/syscall.c:5093 [inline]
      __se_sys_bpf kernel/bpf/syscall.c:5091 [inline]
      __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5091       do_syscall_64+0x54/0x70 arch/x86/entry/common.c:48

    This seems similar to commit ea68376c8bed (bpf: prevent decl_tag from being     referenced in func_proto) but for the argument.

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 AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1781347338 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: net: mdio: unexport __init-annotated     mdio_bus_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up     after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol     may end up with kernel panic. modpost used to detect it, but it has been broken for a decade. Recently, I     fixed modpost so it started to warn it again, then this showed up in linux-next builds. There are two ways     to fix it: - Remove __init - Remove EXPORT_SYMBOL I chose the latter for this case because the only in-     tree call-site, drivers/net/phy/phy_device.c is never compiled as modular. (CONFIG_PHYLIB is boolean)     (CVE-2022-49350)

  - In the Linux kernel, the following vulnerability has been resolved: selinux: fix memleak in     security_read_state_kernel() In this function, it directly returns the result of __security_read_policy     without freeing the allocated memory in *data, cause memory leak issue, so free the memory if
    __security_read_policy failed. [PM: subject line tweak] (CVE-2022-50201)

  - In the Linux kernel, the following vulnerability has been resolved: usb: typec: tcpci: fix of node     refcount leak in tcpci_register_port() I got the following report while doing device(mt6370-tcpc) load     test with CONFIG_OF_UNITTEST and CONFIG_OF_DYNAMIC enabled: OF: ERROR: memory leak, expected refcount 1     instead of 2, of_node_get()/of_node_put() unbalanced - destroy cset entry: attach overlay node     /i2c/pmic@34/tcpc/connector The 'fwnode' set in tcpci_parse_config() which is called in     tcpci_register_port(), its node refcount is increased in device_get_named_child_node(). It needs be put     while exiting, so call fwnode_handle_put() in the error path of tcpci_register_port() and in     tcpci_unregister_port() to avoid leak. (CVE-2022-50246)

  - In the Linux kernel, the following vulnerability has been resolved: drivers: serial: jsm: fix some leaks     in probe This error path needs to unwind instead of just returning directly. (CVE-2022-50312)

  - In the Linux kernel, the following vulnerability has been resolved: thermal: intel_powerclamp: Use     get_cpu() instead of smp_processor_id() to avoid crash When CPU 0 is offline and intel_powerclamp is used     to inject idle, it generates kernel BUG: BUG: using smp_processor_id() in preemptible [00000000] code:
    bash/15687 caller is debug_smp_processor_id+0x17/0x20 CPU: 4 PID: 15687 Comm: bash Not tainted 5.19.0-rc7+     #57 Call Trace: <TASK> dump_stack_lvl+0x49/0x63 dump_stack+0x10/0x16 check_preemption_disabled+0xdd/0xe0     debug_smp_processor_id+0x17/0x20 powerclamp_set_cur_state+0x7f/0xf9 [intel_powerclamp] ... ... Here CPU 0     is the control CPU by default and changed to the current CPU, if CPU 0 offlined. This check has to be     performed under cpus_read_lock(), hence the above warning. Use get_cpu() instead of smp_processor_id() to     avoid this BUG. [ rjw: Subject edits ] (CVE-2022-50494)

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.

  - bpf: Prevent decl_tag from being referenced in func_proto arg Syzkaller managed to hit another decl_tag     issue: btf_func_proto_check kernel/bpf/btf.c:4506 [inline] btf_check_all_types kernel/bpf/btf.c:4734     [inline] btf_parse_type_sec+0x1175/0x1980 kernel/bpf/btf.c:4763 btf_parse kernel/bpf/btf.c:5042 [inline]     btf_new_fd+0x65a/0xb00 kernel/bpf/btf.c:6709 bpf_btf_load+0x6f/0x90 kernel/bpf/syscall.c:4342
    __sys_bpf+0x50a/0x6c0 kernel/bpf/syscall.c:5034 __do_sys_bpf kernel/bpf/syscall.c:5093 [inline]
    __se_sys_bpf kernel/bpf/syscall.c:5091 [inline] __x64_sys_bpf+0x7c/0x90 kernel/bpf/syscall.c:5091     do_syscall_64+0x54/0x70 arch/x86/entry/common.c:48 This seems similar to commit ea68376c8bed (bpf:
    prevent decl_tag from being referenced in func_proto) but for the argument. (CVE-2022-50883)

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

An update of the linux package has been released.

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:0317-1 advisory.

    The SUSE Linux Enterprise 15 SP5 kernel was updated to fix various security issues

    The following security issues were fixed:

    - CVE-2022-50630: mm: hugetlb: fix UAF in hugetlb_handle_userfault (bsc#1254785).
    - CVE-2022-50700: wifi: ath10k: Delay the unmapping of the buffer (bsc#1255576).
    - CVE-2023-53254: cacheinfo: Fix shared_cpu_map to handle shared caches at different levels (bsc#1249871).
    - CVE-2023-53781: smc: Fix use-after-free in tcp_write_timer_handler() (bsc#1254751).
    - CVE-2024-56590: Bluetooth: hci_core: Fix not checking skb length on hci_acldata_packet (bsc#1235038).
    - CVE-2025-39977: futex: Prevent use-after-free during requeue-PI (bsc#1252046).
    - CVE-2025-40019: crypto: essiv - Check ssize for decryption and in-place encryption (bsc#1252678).
    - CVE-2025-40139: smc: Use __sk_dst_get() and dst_dev_rcu() in in smc_clc_prfx_set() (bsc#1253409).
    - CVE-2025-40215: kABI: xfrm: delete x->tunnel as we delete x (bsc#1254959).
    - CVE-2025-40220: fuse: fix livelock in synchronous file put from fuseblk workers (bsc#1254520).
    - CVE-2025-40233: ocfs2: clear extent cache after moving/defragmenting extents (bsc#1254813).
    - CVE-2025-40258: mptcp: fix race condition in mptcp_schedule_work() (bsc#1254843).
    - CVE-2025-40277: drm/vmwgfx: Validate command header size against (bsc#1254894).
    - CVE-2025-40280: tipc: Fix use-after-free in tipc_mon_reinit_self() (bsc#1254847).
    - CVE-2025-40331: sctp: Prevent TOCTOU out-of-bounds write (bsc#1254615).
    - CVE-2025-68732: gpu: host1x: Fix race in syncpt alloc/free (bsc#1255688).

    The following non security issues were fixed:

    - ACPI/IORT: Fix memory leak in iort_rmr_alloc_sids() (git-fixes).
    - ACPI: PRM: Remove unnecessary strict handler address checks (git-fixes).
    - ACPI: property: Do not pass NULL handles to acpi_attach_data() (git-fixes).
    - ACPI: property: Fix buffer properties extraction for subnodes (git-fixes).
    - KVM: SVM: Fix TSC_AUX virtualization setup (git-fixes).
    - RDMA/cm: Rate limit destroy CM ID timeout error message (git-fixes).
    - RDMA/counter: Check CAP_NET_RAW check in user namespace for RDMA counters (git-fixes).
    - RDMA/hns: Fix the modification of max_send_sge (git-fixes).
    - RDMA/mlx5: Check CAP_NET_RAW in user namespace for anchor create (git-fixes).
    - RDMA/mlx5: Check CAP_NET_RAW in user namespace for devx create (git-fixes).
    - RDMA/mlx5: Check CAP_NET_RAW in user namespace for flow create (git-fixes).
    - RDMA/mlx5: Fix compilation warning when USER_ACCESS isn't set (git-fixes).
    - RDMA/nldev: Check CAP_NET_RAW in user namespace for QP modify (git-fixes).
    - RDMA/uverbs: Add empty rdma_uattrs_has_raw_cap() declaration (git-fixes).
    - RDMA/uverbs: Check CAP_NET_RAW in user namespace for QP create (git-fixes).
    - RDMA/uverbs: Check CAP_NET_RAW in user namespace for RAW QP create (git-fixes).
    - RDMA/uverbs: Check CAP_NET_RAW in user namespace for flow create (git-fixes).
    - arch/idle: Change arch_cpu_idle() behavior: always exit with IRQs disabled (git-fixes).
    - cpuidle/poll: Ensure IRQs stay disabled after cpuidle_state::enter() calls (git-fixes).
    - cpuidle: Move IRQ state validation (git-fixes).
    - cpuidle: haltpoll: Do not enable interrupts when entering idle (git-fixes).
    - dm: free table mempools if not used in __bind (git-fixes).
    - padata: Honor the caller's alignment in case of chunk_size 0 (bsc#1237563).
    - platform/x86/intel-uncore-freq: Fail module load when plat_info is NULL (git-fixes).
    - x86/bugs: Fix RSB clearing in indirect_branch_prediction_barrier() (git-fixes).
    - x86/bugs: Use SBPB in write_ibpb() if applicable (git-fixes).
    - x86/paravirt: Move halt paravirt calls under CONFIG_PARAVIRT (git-fixes).
    - x86/tdx: Drop flags from __tdx_hypercall() (git-fixes).
    - x86/tdx: Dynamically disable SEPT violations from causing #VEs (git-fixes).
    - x86/tdx: Emit warning if IRQs are enabled during HLT #VE handling (git-fixes).
    - x86/tdx: Extend TDX_MODULE_CALL to support more TDCALL/SEAMCALL leafs (git-fixes).
    - x86/tdx: Fix __noreturn build warning around __tdx_hypercall_failed() (git-fixes).
    - x86/tdx: Fix arch_safe_halt() execution for TDX VMs (git-fixes).
    - x86/tdx: Introduce wrappers to read and write TD metadata (git-fixes).
    - x86/tdx: Make TDX_HYPERCALL asm similar to TDX_MODULE_CALL (git-fixes).
    - x86/tdx: Make macros of TDCALLs consistent with the spec (git-fixes).
    - x86/tdx: Pass TDCALL/SEAMCALL input/output registers via a structure (git-fixes).
    - x86/tdx: Reimplement __tdx_hypercall() using TDX_MODULE_CALL asm (git-fixes).
    - x86/tdx: Remove 'struct tdx_hypercall_args' (git-fixes).
    - x86/tdx: Remove TDX_HCALL_ISSUE_STI (git-fixes).
    - x86/tdx: Rename __tdx_module_call() to __tdcall() (git-fixes).
    - x86/tdx: Rename tdx_parse_tdinfo() to tdx_setup() (git-fixes).
    - x86/tdx: Retry partially-completed page conversion hypercalls (git-fixes).
    - x86/tdx: Skip saving output regs when SEAMCALL fails with VMFailInvalid (git-fixes).
    - x86/tdx: Zero out the missing RSI in TDX_HYPERCALL macro (git-fixes).
    - x86/virt/tdx: Make TDX_MODULE_CALL handle SEAMCALL #UD and #GP (git-fixes).
    - x86/virt/tdx: Wire up basic SEAMCALL functions (git-fixes).
    - xfs: fix sparse inode limits on runt AG (bsc#1254392).

Tenable has extracted the preceding description block directly from the SUSE 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
308906	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-010833)	Nessus	Unity Linux Local Security Checks	4/21/2026	4/21/2026	medium
309499	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2026-013623)	Nessus	Unity Linux Local Security Checks	4/22/2026	4/26/2026	medium
360826	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1781347338)	Nessus	Alma Linux Local Security Checks	10/1/2026	10/19/2026	high
280786	Linux Distros Unpatched Vulnerability : CVE-2022-50883	Nessus	Misc.	12/31/2025	11/12/2026	high
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	7/22/2021	11/2/2026	high
297191	SUSE SLES15 : Security update for the Linux Kernel (SUSE-SU-2026:0317-1)	Nessus	SuSE Local Security Checks	1/30/2026	9/29/2026	high

Detections

Analytics

Plugins Search

medium

medium

high

high

high

high