In the Linux kernel, the following vulnerability has been resolved: mac80211: fix potential double free on mesh join While commit 6a01afcf8468 ("mac80211: mesh: Free ie data when leaving mesh") fixed a memory leak on mesh leave / teardown it introduced a potential memory corruption caused by a double free when rejoining the mesh: ieee80211_leave_mesh() -> kfree(sdata->u.mesh.ie); ... ieee80211_join_mesh() -> copy_mesh_setup() -> old_ie = ifmsh->ie; -> kfree(old_ie); This double free / kernel panics can be reproduced by using wpa_supplicant with an encrypted mesh (if set up without encryption via "iw" then ifmsh->ie is always NULL, which avoids this issue). And then calling: $ iw dev mesh0 mesh leave $ iw dev mesh0 mesh join my-mesh Note that typically these commands are not used / working when using wpa_supplicant. And it seems that wpa_supplicant or wpa_cli are going through a NETDEV_DOWN/NETDEV_UP cycle between a mesh leave and mesh join where the NETDEV_UP resets the mesh.ie to NULL via a memcpy of default_mesh_setup in cfg80211_netdev_notifier_call, which then avoids the memory corruption, too. The issue was first observed in an application which was not using wpa_supplicant but "Senf" instead, which implements its own calls to nl80211. Fixing the issue by removing the kfree()'ing of the mesh IE in the mesh join function and leaving it solely up to the mesh leave to free the mesh IE.

The CentOS Linux 8.4 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS8.4:CLSA-2025:1749568993 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: cifs: potential buffer overflow in     handling symlinks Smatch printed a warning: arch/x86/crypto/poly1305_glue.c:198 poly1305_update_arch()     error: __memcpy() 'dctx->buf' too small (16 vs u32max) It's caused because Smatch marks 'link_len' as     untrusted since it comes from sscanf(). Add a check to ensure that 'link_len' is not larger than the size     of the 'link_str' buffer. (CVE-2022-49058)

  - In the Linux kernel, the following vulnerability has been resolved: mac80211: fix potential double free on     mesh join While commit 6a01afcf8468 (mac80211: mesh: Free ie data when leaving mesh) fixed a memory leak     on mesh leave / teardown it introduced a potential memory corruption caused by a double free when     rejoining the mesh: ieee80211_leave_mesh() -> kfree(sdata->u.mesh.ie); ... ieee80211_join_mesh() ->     copy_mesh_setup() -> old_ie = ifmsh->ie; -> kfree(old_ie); This double free / kernel panics can be     reproduced by using wpa_supplicant with an encrypted mesh (if set up without encryption via iw then     ifmsh->ie is always NULL, which avoids this issue). And then calling: $ iw dev mesh0 mesh leave $ iw dev     mesh0 mesh join my-mesh Note that typically these commands are not used / working when using     wpa_supplicant. And it seems that wpa_supplicant or wpa_cli are going through a NETDEV_DOWN/NETDEV_UP     cycle between a mesh leave and mesh join where the NETDEV_UP resets the mesh.ie to NULL via a memcpy of     default_mesh_setup in cfg80211_netdev_notifier_call, which then avoids the memory corruption, too. The     issue was first observed in an application which was not using wpa_supplicant but Senf instead, which     implements its own calls to nl80211. Fixing the issue by removing the kfree()'ing of the mesh IE in the     mesh join function and leaving it solely up to the mesh leave to free the mesh IE. (CVE-2022-49290)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Fix potential double free in     create_var_ref() In create_var_ref(), init_var_ref() is called to initialize the fields of variable     ref_field, which is allocated in the previous function call to create_hist_field(). Function     init_var_ref() allocates the corresponding fields such as ref_field->system, but frees these fields when     the function encounters an error. The caller later calls destroy_hist_field() to conduct error handling,     which frees the fields and the variable itself. This results in double free of the fields which are     already freed in the previous function. Fix this by storing NULL to the corresponding fields when they are     freed in init_var_ref(). (CVE-2022-49410)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix use-after-free in     chanctx code In ieee80211_vif_use_reserved_context(), when we have an old context and the new context's     replace_state is set to IEEE80211_CHANCTX_REPLACE_NONE, we free the old context in     ieee80211_vif_use_reserved_reassign(). Therefore, we cannot check the old_ctx anymore, so we should set it     to NULL after this point. However, since the new_ctx replace state is clearly not     IEEE80211_CHANCTX_REPLACES_OTHER, we're not going to do anything else in this function and can just return     to avoid accessing the freed old_ctx. (CVE-2022-49416)

  - In the Linux kernel, the following vulnerability has been resolved: media: pvrusb2: fix array-index-out-     of-bounds in pvr2_i2c_core_init Syzbot reported that -1 is used as array index. The problem was in missing     validation check. hdw->unit_number is initialized with -1 and then if init table walk fails this value     remains unchanged. Since code blindly uses this member for array indexing adding sanity check is the     easiest fix for that. hdw->workpoll initialization moved upper to prevent warning in __flush_work.
    (CVE-2022-49478)

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

The Rocky Linux 8.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the CIQ ciqsa-2026_1220 advisory.

    This advisory aggregates security fixes for the kernel SRPM in CIQ LTS 8.6. It addresses 24 CVEs:
    CVE-2025-39971, CVE-2024-26923, CVE-2023-53232, CVE-2023-53821, CVE-2023-52530, and 19 more.

Tenable has extracted the preceding description block directly from the CIQ 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 CentOS Linux 8.5 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS8.5:CLSA-2025:1749562017 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: mm/khugepaged: invoke MMU notifiers in     shmem/file collapse paths Any codepath that zaps page table entries must invoke MMU notifiers to ensure     that secondary MMUs (like KVM) don't keep accessing pages which aren't mapped anymore. Secondary MMUs     don't hold their own references to pages that are mirrored over, so failing to notify them can lead to     page use-after-free. I'm marking this as addressing an issue introduced in commit f3f0e1d2150b     (khugepaged: add support of collapse for tmpfs/shmem pages), but most of the security impact of this     only came in commit 27e1f8273113 (khugepaged: enable collapse pmd for pte-mapped THP), which actually     omitted flushes for the removal of present PTEs, not just for the removal of empty page tables.
    (CVE-2022-48991)

  - In the Linux kernel, the following vulnerability has been resolved: mac80211: fix potential double free on     mesh join While commit 6a01afcf8468 (mac80211: mesh: Free ie data when leaving mesh) fixed a memory leak     on mesh leave / teardown it introduced a potential memory corruption caused by a double free when     rejoining the mesh: ieee80211_leave_mesh() -> kfree(sdata->u.mesh.ie); ... ieee80211_join_mesh() ->     copy_mesh_setup() -> old_ie = ifmsh->ie; -> kfree(old_ie); This double free / kernel panics can be     reproduced by using wpa_supplicant with an encrypted mesh (if set up without encryption via iw then     ifmsh->ie is always NULL, which avoids this issue). And then calling: $ iw dev mesh0 mesh leave $ iw dev     mesh0 mesh join my-mesh Note that typically these commands are not used / working when using     wpa_supplicant. And it seems that wpa_supplicant or wpa_cli are going through a NETDEV_DOWN/NETDEV_UP     cycle between a mesh leave and mesh join where the NETDEV_UP resets the mesh.ie to NULL via a memcpy of     default_mesh_setup in cfg80211_netdev_notifier_call, which then avoids the memory corruption, too. The     issue was first observed in an application which was not using wpa_supplicant but Senf instead, which     implements its own calls to nl80211. Fixing the issue by removing the kfree()'ing of the mesh IE in the     mesh join function and leaving it solely up to the mesh leave to free the mesh IE. (CVE-2022-49290)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Fix potential double free in     create_var_ref() In create_var_ref(), init_var_ref() is called to initialize the fields of variable     ref_field, which is allocated in the previous function call to create_hist_field(). Function     init_var_ref() allocates the corresponding fields such as ref_field->system, but frees these fields when     the function encounters an error. The caller later calls destroy_hist_field() to conduct error handling,     which frees the fields and the variable itself. This results in double free of the fields which are     already freed in the previous function. Fix this by storing NULL to the corresponding fields when they are     freed in init_var_ref(). (CVE-2022-49410)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix use-after-free in     chanctx code In ieee80211_vif_use_reserved_context(), when we have an old context and the new context's     replace_state is set to IEEE80211_CHANCTX_REPLACE_NONE, we free the old context in     ieee80211_vif_use_reserved_reassign(). Therefore, we cannot check the old_ctx anymore, so we should set it     to NULL after this point. However, since the new_ctx replace state is clearly not     IEEE80211_CHANCTX_REPLACES_OTHER, we're not going to do anything else in this function and can just return     to avoid accessing the freed old_ctx. (CVE-2022-49416)

  - In the Linux kernel, the following vulnerability has been resolved: media: pvrusb2: fix array-index-out-     of-bounds in pvr2_i2c_core_init Syzbot reported that -1 is used as array index. The problem was in missing     validation check. hdw->unit_number is initialized with -1 and then if init table walk fails this value     remains unchanged. Since code blindly uses this member for array indexing adding sanity check is the     easiest fix for that. hdw->workpoll initialization moved upper to prevent warning in __flush_work.
    (CVE-2022-49478)

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

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2026:1886 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * kernel: mac80211: fix potential double free on mesh join (CVE-2022-49290)

    * kernel: cifs: fix oops during encryption (CVE-2022-50341)

    * kernel: i40e: fix idx validation in config queues msg (CVE-2025-39971)

    * kernel: ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (CVE-2025-40154)

    * kernel: Linux kernel: vsock vulnerability may lead to memory corruption (CVE-2025-40248)

    * kernel: Linux kernel Bluetooth L2CAP: Kernel crash due to use-after-free via race condition     (CVE-2023-53751)

    * kernel: drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE (CVE-2025-40277)

    * kernel: net: atlantic: fix fragment overflow handling in RX path (CVE-2025-68301)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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 remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2026:1495 advisory.

    The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with     extremely high determinism requirements.

    Security Fix(es):

    * kernel: mac80211: fix potential double free on mesh join (CVE-2022-49290)

    * kernel: net: bonding: fix use-after-free after 802.3ad slave unbind (CVE-2022-49667)

    * kernel: Linux kernel: be2net buffer overflow in be_get_module_eeprom (CVE-2022-49581)

    * kernel: ntb_hw_switchtec: Fix shift-out-of-bounds in switchtec_ntb_mw_set_trans (CVE-2023-53034)

    * kernel: net: openvswitch: fix nested key length validation in the set() action (CVE-2025-37789)

    * kernel: KVM: arm64: Tear down vGIC on failed vCPU creation (CVE-2025-37849)

    * kernel: smb: client: Fix use-after-free in cifs_fill_dirent (CVE-2025-38051)

    * kernel: RDMA/rxe: Fix incomplete state save in rxe_requester (CVE-2023-53539)

    * kernel: i40e: fix idx validation in config queues msg (CVE-2025-39971)

    * kernel: ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (CVE-2025-40154)

    * kernel: Linux kernel: vsock vulnerability may lead to memory corruption (CVE-2025-40248)

    * kernel: mptcp: fix race condition in mptcp_schedule_work() (CVE-2025-40258)

    * kernel: drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE (CVE-2025-40277)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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 remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2026:1494 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * kernel: mac80211: fix potential double free on mesh join (CVE-2022-49290)

    * kernel: net: bonding: fix use-after-free after 802.3ad slave unbind (CVE-2022-49667)

    * kernel: Linux kernel: be2net buffer overflow in be_get_module_eeprom (CVE-2022-49581)

    * kernel: ntb_hw_switchtec: Fix shift-out-of-bounds in switchtec_ntb_mw_set_trans (CVE-2023-53034)

    * kernel: net: openvswitch: fix nested key length validation in the set() action (CVE-2025-37789)

    * kernel: KVM: arm64: Tear down vGIC on failed vCPU creation (CVE-2025-37849)

    * kernel: smb: client: Fix use-after-free in cifs_fill_dirent (CVE-2025-38051)

    * kernel: RDMA/rxe: Fix incomplete state save in rxe_requester (CVE-2023-53539)

    * kernel: i40e: fix idx validation in config queues msg (CVE-2025-39971)

    * kernel: ASoC: Intel: bytcr_rt5640: Fix invalid quirk input mapping (CVE-2025-40154)

    * kernel: Linux kernel: vsock vulnerability may lead to memory corruption (CVE-2025-40248)

    * kernel: mptcp: fix race condition in mptcp_schedule_work() (CVE-2025-40258)

    * kernel: drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE (CVE-2025-40277)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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 remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2026:1442 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * kernel: mac80211: fix potential double free on mesh join (CVE-2022-49290)

    * kernel: media: rc: fix races with imon_disconnect() (CVE-2025-39993)

    * kernel: ipv6: Fix out-of-bounds access in ipv6_find_tlv() (CVE-2023-53705)

    * kernel: Linux kernel: vsock vulnerability may lead to memory corruption (CVE-2025-40248)

    * kernel: drm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE (CVE-2025-40277)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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-991151 advisory.

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

    mac80211: fix potential double free on mesh join

    While commit 6a01afcf8468 (mac80211: mesh: Free ie data when leaving     mesh) fixed a memory leak on mesh leave / teardown it introduced a     potential memory corruption caused by a double free when rejoining the     mesh:

      ieee80211_leave_mesh()
      -> kfree(sdata->u.mesh.ie);
      ...
      ieee80211_join_mesh()
      -> copy_mesh_setup()
         -> old_ie = ifmsh->ie;
         -> kfree(old_ie);

    This double free / kernel panics can be reproduced by using wpa_supplicant     with an encrypted mesh (if set up without encryption via iw then     ifmsh->ie is always NULL, which avoids this issue). And then calling:

      $ iw dev mesh0 mesh leave       $ iw dev mesh0 mesh join my-mesh

    Note that typically these commands are not used / working when using     wpa_supplicant. And it seems that wpa_supplicant or wpa_cli are going     through a NETDEV_DOWN/NETDEV_UP cycle between a mesh leave and mesh join     where the NETDEV_UP resets the mesh.ie to NULL via a memcpy of     default_mesh_setup in cfg80211_netdev_notifier_call, which then avoids     the memory corruption, too.

    The issue was first observed in an application which was not using     wpa_supplicant but Senf instead, which implements its own calls to     nl80211.

    Fixing the issue by removing the kfree()'ing of the mesh IE in the mesh     join function and leaving it solely up to the mesh leave to free the     mesh IE.

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

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

    mac80211: fix potential double free on mesh join

    While commit 6a01afcf8468 (mac80211: mesh: Free ie data when leaving     mesh) fixed a memory leak on mesh leave / teardown it introduced a     potential memory corruption caused by a double free when rejoining the     mesh:

      ieee80211_leave_mesh()
      -> kfree(sdata->u.mesh.ie);
      ...
      ieee80211_join_mesh()
      -> copy_mesh_setup()
         -> old_ie = ifmsh->ie;
         -> kfree(old_ie);

    This double free / kernel panics can be reproduced by using wpa_supplicant     with an encrypted mesh (if set up without encryption via iw then     ifmsh->ie is always NULL, which avoids this issue). And then calling:

      $ iw dev mesh0 mesh leave       $ iw dev mesh0 mesh join my-mesh

    Note that typically these commands are not used / working when using     wpa_supplicant. And it seems that wpa_supplicant or wpa_cli are going     through a NETDEV_DOWN/NETDEV_UP cycle between a mesh leave and mesh join     where the NETDEV_UP resets the mesh.ie to NULL via a memcpy of     default_mesh_setup in cfg80211_netdev_notifier_call, which then avoids     the memory corruption, too.

    The issue was first observed in an application which was not using     wpa_supplicant but Senf instead, which implements its own calls to     nl80211.

    Fixing the issue by removing the kfree()'ing of the mesh IE in the mesh     join function and leaving it solely up to the mesh leave to free the     mesh IE.

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

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

    mac80211: fix potential double free on mesh join

    While commit 6a01afcf8468 (mac80211: mesh: Free ie data when leaving     mesh) fixed a memory leak on mesh leave / teardown it introduced a     potential memory corruption caused by a double free when rejoining the     mesh:

      ieee80211_leave_mesh()
      -> kfree(sdata->u.mesh.ie);
      ...
      ieee80211_join_mesh()
      -> copy_mesh_setup()
         -> old_ie = ifmsh->ie;
         -> kfree(old_ie);

    This double free / kernel panics can be reproduced by using wpa_supplicant     with an encrypted mesh (if set up without encryption via iw then     ifmsh->ie is always NULL, which avoids this issue). And then calling:

      $ iw dev mesh0 mesh leave       $ iw dev mesh0 mesh join my-mesh

    Note that typically these commands are not used / working when using     wpa_supplicant. And it seems that wpa_supplicant or wpa_cli are going     through a NETDEV_DOWN/NETDEV_UP cycle between a mesh leave and mesh join     where the NETDEV_UP resets the mesh.ie to NULL via a memcpy of     default_mesh_setup in cfg80211_netdev_notifier_call, which then avoids     the memory corruption, too.

    The issue was first observed in an application which was not using     wpa_supplicant but Senf instead, which implements its own calls to     nl80211.

    Fixing the issue by removing the kfree()'ing of the mesh IE in the mesh     join function and leaving it solely up to the mesh leave to free the     mesh IE.

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

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

    mac80211: fix potential double free on mesh join

    While commit 6a01afcf8468 (mac80211: mesh: Free ie data when leaving     mesh) fixed a memory leak on mesh leave / teardown it introduced a     potential memory corruption caused by a double free when rejoining the     mesh:

      ieee80211_leave_mesh()
      -> kfree(sdata->u.mesh.ie);
      ...
      ieee80211_join_mesh()
      -> copy_mesh_setup()
         -> old_ie = ifmsh->ie;
         -> kfree(old_ie);

    This double free / kernel panics can be reproduced by using wpa_supplicant     with an encrypted mesh (if set up without encryption via iw then     ifmsh->ie is always NULL, which avoids this issue). And then calling:

      $ iw dev mesh0 mesh leave       $ iw dev mesh0 mesh join my-mesh

    Note that typically these commands are not used / working when using     wpa_supplicant. And it seems that wpa_supplicant or wpa_cli are going     through a NETDEV_DOWN/NETDEV_UP cycle between a mesh leave and mesh join     where the NETDEV_UP resets the mesh.ie to NULL via a memcpy of     default_mesh_setup in cfg80211_netdev_notifier_call, which then avoids     the memory corruption, too.

    The issue was first observed in an application which was not using     wpa_supplicant but Senf instead, which implements its own calls to     nl80211.

    Fixing the issue by removing the kfree()'ing of the mesh IE in the mesh     join function and leaving it solely up to the mesh leave to free the     mesh IE.

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 remote SUSE Linux SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:01600-1 advisory.

    The SUSE Linux Enterprise 12 SP5 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2021-47659: drm/plane: Move range check for format_count earlier (bsc#1237839).
    - CVE-2022-49044: dm integrity: fix memory corruption when tag_size is less than digest size     (bsc#1237840).
    - CVE-2022-49055: drm/amdkfd: Check for potential null return of kmalloc_array() (bsc#1237868).
    - CVE-2022-49060: net/smc: Fix NULL pointer dereference in smc_pnet_find_ib() (bsc#1237845).
    - CVE-2022-49086: net: openvswitch: fix leak of nested actions (bsc#1238037).
    - CVE-2022-49111: Bluetooth: Fix use after free in hci_send_acl (bsc#1237984).
    - CVE-2022-49118: scsi: hisi_sas: Free irq vectors in order for v3 HW (bsc#1237979).
    - CVE-2022-49121: scsi: pm8001: Fix tag leaks on error (bsc#1237926).
    - CVE-2022-49137: drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj (bsc#1238155).
    - CVE-2022-49175: PM: core: keep irq flags in device_pm_check_callbacks() (bsc#1238099).
    - CVE-2022-49176: bfq: fix use-after-free in bfq_dispatch_request (bsc#1238097).
    - CVE-2022-49179: block, bfq: do not move oom_bfqq (bsc#1238092).
    - CVE-2022-49188: remoteproc: qcom_q6v5_mss: Fix some leaks in q6v5_alloc_memory_region (bsc#1238138).
    - CVE-2022-49197: af_netlink: Fix shift out of bounds in group mask calculation (bsc#1238455).
    - CVE-2022-49205: bpf, sockmap: Fix double uncharge the mem of sk_msg (bsc#1238335).
    - CVE-2022-49232: drm/amd/display: Fix a NULL pointer dereference in     amdgpu_dm_connector_add_common_modes() (bsc#1238139).
    - CVE-2022-49290: mac80211: fix potential double free on mesh join (bsc#1238156).
    - CVE-2022-49305: drivers: staging: rtl8192u: Fix deadlock in ieee80211_beacons_stop() (bsc#1238645).
    - CVE-2022-49325: tcp: add accessors to read/set tp->snd_cwnd (bsc#1238398).
    - CVE-2022-49335: drm/amdgpu/cs: make commands with 0 chunks illegal behaviour (bsc#1238377).
    - CVE-2022-49351: net: altera: Fix refcount leak in altera_tse_mdio_create (bsc#1237939).
    - CVE-2022-49385: driver: base: fix UAF when driver_attach failed (bsc#1237951).
    - CVE-2022-49390: macsec: fix UAF bug for real_dev (bsc#1238233).
    - CVE-2022-49411: bfq: Make sure bfqg for which we are queueing requests is online (bsc#1238307).
    - CVE-2022-49442: drivers/base/node.c: fix compaction sysfs file leak (bsc#1238243).
    - CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919).
    - CVE-2022-49478: media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init (bsc#1238000).
    - CVE-2022-49489: drm/msm/disp/dpu1: set vbif hw config to NULL to avoid use after memory free during pm     runtime resume (bsc#1238244).
    - CVE-2022-49504: scsi: lpfc: Inhibit aborts if external loopback plug is inserted (bsc#1238835).
    - CVE-2022-49521: scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp() (bsc#1238938).
    - CVE-2022-49525: media: cx25821: Fix the warning when removing the module (bsc#1238022).
    - CVE-2022-49534: scsi: lpfc: Protect memory leak for NPIV ports sending PLOGI_RJT (bsc#1238893).
    - CVE-2022-49535: scsi: lpfc: Fix null pointer dereference after failing to issue FLOGI and PLOGI     (bsc#1238937).
    - CVE-2022-49536: scsi: lpfc: Fix SCSI I/O completion and abort handler deadlock (bsc#1238838).
    - CVE-2022-49537: scsi: lpfc: Fix call trace observed during I/O with CMF enabled (bsc#1238930).
    - CVE-2022-49542: scsi: lpfc: Move cfg_log_verbose check before calling lpfc_dmp_dbg() (bsc#1238722).
    - CVE-2022-49561: netfilter: conntrack: re-fetch conntrack after insertion (bsc#1238537).
    - CVE-2022-49590: igmp: Fix data-races around sysctl_igmp_llm_reports (bsc#1238844).
    - CVE-2022-49658: bpf, selftests: Add verifier test case for imm=0,umin=0,umax=1 scalar (bsc#1238803).
    - CVE-2022-49668: PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events (bsc#1237957).
    - CVE-2022-49693: drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf (bsc#1237954).
    - CVE-2022-49725: i40e: Fix call trace in setup_tx_descriptors (bsc#1238016).
    - CVE-2022-49728: kABI workaround for changeing the variable length type to size_t (bsc#1239111).
    - CVE-2022-49730: scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is aborted (bsc#1239070).
    - CVE-2022-49749: i2c: designware: use casting of u64 in clock multiplication to avoid overflow     (bsc#1240243).
    - CVE-2022-49753: dmaengine: Fix double increment of client_count in dma_chan_get() (bsc#1240250).
    - CVE-2023-53023: net: nfc: Fix use-after-free in local_cleanup() (bsc#1240309).
    - CVE-2023-53032: netfilter: ipset: Fix overflow before widen in the bitmap_ip_create() function     (bsc#1240270).
    - CVE-2024-49994: block: fix integer overflow in BLKSECDISCARD (bsc#1237757).
    - CVE-2024-50038: netfilter: xtables: fix typo causing some targets not to load on IPv6 (bsc#1231910).
    - CVE-2024-50272: filemap: Fix bounds checking in filemap_read() (bsc#1233461 bsc#1234209).
    - CVE-2024-52559: drm/msm/gem: prevent integer overflow in msm_ioctl_gem_submit() (bsc#1238507).
    - CVE-2024-54683: netfilter: IDLETIMER: Fix for possible ABBA deadlock (bsc#1235729).
    - CVE-2024-56590: skbuff: introduce skb_pull_data (bsc#1235038).
    - CVE-2024-56641: net/smc: initialize close_work early to avoid warning (bsc#1235526).
    - CVE-2024-57924: fs: relax assertions on failure to encode file handles (bsc#1236086).
    - CVE-2024-57980: media: uvcvideo: Fix double free in error path (bsc#1237911).
    - CVE-2024-57981: usb: xhci: Fix NULL pointer dereference on certain command aborts (bsc#1237912).
    - CVE-2024-58005: tpm: Change to kvalloc() in eventlog/acpi.c (bsc#1237873).
    - CVE-2024-58009: Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc (bsc#1238760).
    - CVE-2024-58017: printk: Fix signed integer overflow when defining LOG_BUF_LEN_MAX (bsc#1237950     bsc#1239112).
    - CVE-2024-58063: wifi: rtlwifi: fix memory leaks and invalid access at probe error path (bsc#1238984).
    - CVE-2024-58093: PCI/ASPM: Fix link state exit during switch upstream function removal (bsc#1241347).
    - CVE-2025-21635: rds: sysctl: rds_tcp_{rcv,snd}buf: avoid using current->nsproxy (bsc#1236111).
    - CVE-2025-21735: NFC: nci: Add bounds checking in nci_hci_create_pipe() (bsc#1238497).
    - CVE-2025-21750: wifi: brcmfmac: Check the return value of of_property_read_string_index() (bsc#1238905).
    - CVE-2025-21758: ipv6: mcast: add RCU protection to mld_newpack() (bsc#1238737).
    - CVE-2025-21768: net: ipv6: fix dst ref loops in rpl, seg6 and ioam6 lwtunnels (bsc#1238714).
    - CVE-2025-21772: partitions: mac: fix handling of bogus partition table (bsc#1238911).
    - CVE-2025-21779: KVM: x86: Reject Hyper-V's SEND_IPI hypercalls if local APIC isn't in-kernel     (bsc#1238768).
    - CVE-2025-21806: net: let net.core.dev_weight always be non-zero (bsc#1238746).
    - CVE-2025-21862: drop_monitor: fix incorrect initialization order (bsc#1239474).
    - CVE-2025-21881: uprobes: Reject the shared zeropage in uprobe_write_opcode() (bsc#1240185).
    - CVE-2025-21909: wifi: nl80211: reject cooked mode if it is set along with other flags (bsc#1240590).
    - CVE-2025-21910: wifi: cfg80211: regulatory: improve invalid hints checking (bsc#1240583).
    - CVE-2025-21926: net: gso: fix ownership in __udp_gso_segment (bsc#1240712).
    - CVE-2025-21927: nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu() (bsc#1240714).
    - CVE-2025-21931: hwpoison, memory_hotplug: lock folio before unmap hwpoisoned folio (bsc#1240709).
    - CVE-2025-21941: drm/amd/display: Fix null check for pipe_ctx->plane_state in (bsc#1240701).
    - CVE-2025-21948: HID: appleir: Fix potential NULL dereference at raw event handle (bsc#1240703).
    - CVE-2025-21956: drm/amd/display: Assign normalized_pix_clk when color depth = 14 (bsc#1240739).
    - CVE-2025-21957: scsi: qla1280: Fix kernel oops when debug level > 2 (bsc#1240742).
    - CVE-2025-21963: cifs: Fix integer overflow while processing acdirmax mount option (bsc#1240717).
    - CVE-2025-21964: cifs: Fix integer overflow while processing acregmax mount option (bsc#1240740).
    - CVE-2025-21976: fbdev: hyperv_fb: Allow graceful removal of framebuffer (bsc#1241145).
    - CVE-2025-22004: net: atm: fix use after free in lec_send() (bsc#1240835).
    - CVE-2025-22008: regulator: check that dummy regulator has been probed before using it (bsc#1240942).
    - CVE-2025-22010: RDMA/hns: Fix soft lockup during bt pages loop (bsc#1240943).
    - CVE-2025-22018: atm: Fix NULL pointer dereference (bsc#1241266).
    - CVE-2025-22053: net: ibmveth: make veth_pool_store stop hanging (bsc#1241373).
    - CVE-2025-22055: net: fix geneve_opt length integer overflow (bsc#1241371).
    - CVE-2025-22060: net: mvpp2: Prevent parser TCAM memory corruption (bsc#1241526).
    - CVE-2025-22086: RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow (bsc#1241458).
    - CVE-2025-23131: dlm: prevent NPD when writing a positive value to event_done (bsc#1241601).
    - CVE-2025-37785: ext4: fix OOB read when checking dotdot dir (bsc#1241640).


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.

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

    The SUSE Linux Enterprise 15 SP3 kernel was updated to receive various security bugfixes.

    The following security bugs were fixed:

    - CVE-2021-47248: udp: fix race between close() and udp_abort() (bsc#1224867).
    - CVE-2022-49051: net: usb: aqc111: Fix out-of-bounds accesses in RX fixup (bsc#1237903).
    - CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918).
    - CVE-2022-49275: can: m_can: m_can_tx_handler(): fix use after free of skb (bsc#1238719).
    - CVE-2022-49413: bfq: Update cgroup information before merging bio (bsc#1238710).
    - CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919).
    - CVE-2022-49545: ALSA: usb-audio: Cancel pending work at closing a MIDI substream (bsc#1238729).
    - CVE-2022-49563: crypto: qat - add param check for RSA (bsc#1238787).
    - CVE-2022-49564: crypto: qat - add param check for DH (bsc#1238789).
    - CVE-2022-49739: gfs2: Always check inode size of inline inodes (bsc#1240207).
    - CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
    - CVE-2024-56642: tipc: Fix use-after-free of kernel socket in cleanup_bearer() (bsc#1235433).
    - CVE-2024-56651: can: hi311x: hi3110_can_ist(): fix potential use-after-free (bsc#1235528).
    - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
    - CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
    - CVE-2025-21772: partitions: mac: fix handling of bogus partition table (bsc#1238911).
    - CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115).


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.

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

    The SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.

    The following security bugs were fixed:

    - CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918).
    - CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919).
    - CVE-2022-49739: gfs2: Always check inode size of inline inodes (bsc#1240207).
    - CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
    - CVE-2024-53124: net: fix data-races around sk->sk_forward_alloc (bsc#1234074).
    - CVE-2024-53176: smb: During unmount, ensure all cached dir instances drop their dentry (bsc#1234894).
    - CVE-2024-53178: smb: Do not leak cfid when reconnect races with open_cached_dir (bsc#1234895).
    - CVE-2024-56651: can: hi311x: hi3110_can_ist(): fix potential use-after-free (bsc#1235528).
    - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
    - CVE-2024-58013: Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync     (bsc#1239095).
    - CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
    - CVE-2025-21693: mm: zswap: properly synchronize freeing resources during CPU hotunplug (bsc#1237029).
    - CVE-2025-21718: net: rose: fix timer races against user threads (bsc#1239073).
    - CVE-2025-21772: partitions: mac: fix handling of bogus partition table (bsc#1238911).
    - CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115).


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.

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

    The SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2024-2201: Fixed information leak in x86/BHI (bsc#1217339).
    - CVE-2024-41092: drm/i915/gt: Fix potential UAF by revoke of fence registers (bsc#1228483).
    - CVE-2024-42098: crypto: ecdh - explicitly zeroize private_key (bsc#1228779).
    - CVE-2024-42229: crypto: aead,cipher - zeroize key buffer after use (bsc#1228708).
    - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
    - CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
    - CVE-2025-21718: net: rose: fix timer races against user threads (bsc#1239073).
    - CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115).


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.

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

  - mac80211: fix potential double free on mesh join While commit 6a01afcf8468 (mac80211: mesh: Free ie data     when leaving mesh) fixed a memory leak on mesh leave / teardown it introduced a potential memory     corruption caused by a double free when rejoining the mesh: ieee80211_leave_mesh() ->     kfree(sdata->u.mesh.ie); ... ieee80211_join_mesh() -> copy_mesh_setup() -> old_ie = ifmsh->ie; ->     kfree(old_ie); This double free / kernel panics can be reproduced by using wpa_supplicant with an     encrypted mesh (if set up without encryption via iw then ifmsh->ie is always NULL, which avoids this     issue). And then calling: $ iw dev mesh0 mesh leave $ iw dev mesh0 mesh join my-mesh Note that typically     these commands are not used / working when using wpa_supplicant. And it seems that wpa_supplicant or     wpa_cli are going through a NETDEV_DOWN/NETDEV_UP cycle between a mesh leave and mesh join where the     NETDEV_UP resets the mesh.ie to NULL via a memcpy of default_mesh_setup in cfg80211_netdev_notifier_call,     which then avoids the memory corruption, too. The issue was first observed in an application which was not     using wpa_supplicant but Senf instead, which implements its own calls to nl80211. Fixing the issue by     removing the kfree()'ing of the mesh IE in the mesh join function and leaving it solely up to the mesh     leave to free the mesh IE. (CVE-2022-49290)

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

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2022:8267 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * off-path attacker may inject data or terminate victim's TCP session (CVE-2020-36516)

    * use-after-free vulnerability in function sco_sock_sendmsg() (CVE-2021-3640)

    * smb2_ioctl_query_info NULL pointer dereference (CVE-2022-0168)

    * NULL pointer dereference in udf_expand_file_adinicbdue() during writeback (CVE-2022-0617)

    * swiotlb information leak with DMA_FROM_DEVICE (CVE-2022-0854)

    * uninitialized registers on stack in nft_do_chain can cause kernel pointer leakage to UM (CVE-2022-1016)

    * race condition in snd_pcm_hw_free leading to use-after-free (CVE-2022-1048)

    * use-after-free and memory errors in ext4 when mounting and operating on a corrupted image     (CVE-2022-1184)

    * concurrency use-after-free between drm_setmaster_ioctl and drm_mode_getresources (CVE-2022-1280)

    * kernel info leak issue in pfkey_register (CVE-2022-1353)

    * use-after-free in ath9k_htc_probe_device() could cause an escalation of privileges (CVE-2022-1679)

    * NULL pointer dereference in x86_emulate_insn may lead to DoS (CVE-2022-1852)

    * fanotify misuses fd_install() which could lead to use-after-free (CVE-2022-1998)

    * nf_tables cross-table potential use-after-free may lead to local privilege escalation (CVE-2022-2586)

    * integer underflow leads to out-of-bounds write in reserve_sfa_size() (CVE-2022-2639)

    * slab-out-of-bounds access in packet_recvmsg() (CVE-2022-20368)

    * incomplete clean-up of multi-core shared buffers (aka SBDR) (CVE-2022-21123)

    * incomplete clean-up of microarchitectural fill buffers (aka SBDS) (CVE-2022-21125)

    * incomplete clean-up in specific special register write operations (aka DRPW) (CVE-2022-21166)

    * possible to use the debugger to write zero into a location of choice (CVE-2022-21499)

    * AMD: RetBleed Arbitrary Speculative Code Execution with Return Instructions (CVE-2022-23816,     CVE-2022-29900)

    * AMD: Branch Type Confusion (non-retbleed) (CVE-2022-23825)

    * Intel: Post-barrier Return Stack Buffer Predictions (CVE-2022-26373)

    * double free in ems_usb_start_xmit in drivers/net/can/usb/ems_usb.c (CVE-2022-28390)

    * use after free in SUNRPC subsystem (CVE-2022-28893)

    * use-after-free due to improper update of reference count in net/sched/cls_u32.c (CVE-2022-29581)

    * Intel: RetBleed Arbitrary Speculative Code Execution with Return Instructions (CVE-2022-29901)

    * DoS in nfqnl_mangle in net/netfilter/nfnetlink_queue.c (CVE-2022-36946)

    * nf_tables disallow binding to already bound chain (CVE-2022-39190)

    * nfs_atomic_open() returns uninitialized data instead of ENOTDIR (CVE-2022-24448)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 9.1 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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 remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2022:7683 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * off-path attacker may inject data or terminate victim's TCP session (CVE-2020-36516)

    * race condition in VT_RESIZEX ioctl when vc_cons[i].d is already NULL leading to NULL pointer dereference     (CVE-2020-36558)

    * use-after-free vulnerability in function sco_sock_sendmsg() (CVE-2021-3640)

    * memory leak for large arguments in video_usercopy function in drivers/media/v4l2-core/v4l2-ioctl.c     (CVE-2021-30002)

    * smb2_ioctl_query_info NULL Pointer Dereference (CVE-2022-0168)

    * NULL pointer dereference in udf_expand_file_adinicbdue() during writeback (CVE-2022-0617)

    * swiotlb information leak with DMA_FROM_DEVICE (CVE-2022-0854)

    * uninitialized registers on stack in nft_do_chain can cause kernel pointer leakage to UM (CVE-2022-1016)

    * race condition in snd_pcm_hw_free leading to use-after-free (CVE-2022-1048)

    * use-after-free in tc_new_tfilter() in net/sched/cls_api.c (CVE-2022-1055)

    * use-after-free and memory errors in ext4 when mounting and operating on a corrupted image     (CVE-2022-1184)

    * NULL pointer dereference in x86_emulate_insn may lead to DoS (CVE-2022-1852)

    * buffer overflow in nft_set_desc_concat_parse() (CVE-2022-2078)

    * nf_tables cross-table potential use-after-free may lead to local privilege escalation (CVE-2022-2586)

    * openvswitch: integer underflow leads to out-of-bounds write in reserve_sfa_size() (CVE-2022-2639)

    * use-after-free when psi trigger is destroyed while being polled (CVE-2022-2938)

    * net/packet: slab-out-of-bounds access in packet_recvmsg() (CVE-2022-20368)

    * possible to use the debugger to write zero into a location of choice (CVE-2022-21499)

    * Spectre-BHB (CVE-2022-23960)

    * Post-barrier Return Stack Buffer Predictions (CVE-2022-26373)

    * memory leak in drivers/hid/hid-elo.c (CVE-2022-27950)

    * double free in ems_usb_start_xmit in drivers/net/can/usb/ems_usb.c (CVE-2022-28390)

    * use after free in SUNRPC subsystem (CVE-2022-28893)

    * use-after-free due to improper update of reference count in net/sched/cls_u32.c (CVE-2022-29581)

    * DoS in nfqnl_mangle in net/netfilter/nfnetlink_queue.c (CVE-2022-36946)

    * nfs_atomic_open() returns uninitialized data instead of ENOTDIR (CVE-2022-24448)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 8.7 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

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

An update of the linux package has been released.

ID	Name	Product	Family	Type	Severity
362017	CentOS Linux 8.4 [TuxCare] Security Update: bpftool / kernel-core / kernel-debug / kernel-debug-core / etc Multiple Vulnerabilities (CENTOS8.4:CLSA-2025:1749568993)	Nessus	CentOS Local Security Checks	Local	high
353467	Rocky Linux 8.6 [CIQ] Security Update: bpftool / bpftool-debuginfo / kernel / kernel-abi-stablelists / etc Multiple Vulnerabilities (ciqsa-2026_1220)	Nessus	Rocky Linux Local Security Checks	Local	high
352664	CentOS Linux 8.5 [TuxCare] Security Update: kernel-cross-headers / kernel-debug-modules-extra / etc Multiple Vulnerabilities (CENTOS8.5:CLSA-2025:1749562017)	Nessus	CentOS Local Security Checks	Local	high
297808	RHEL 8 : kernel (RHSA-2026:1886)	Nessus	Red Hat Local Security Checks	Local	high
297060	RHEL 9 : kernel-rt (RHSA-2026:1495)	Nessus	Red Hat Local Security Checks	Local	high
297043	RHEL 9 : kernel (RHSA-2026:1494)	Nessus	Red Hat Local Security Checks	Local	high
296997	RHEL 8 : kernel (RHSA-2026:1442)	Nessus	Red Hat Local Security Checks	Local	high
278215	Unity Linux 20.1050e Security Update: kernel (UTSA-2025-991151)	Nessus	Unity Linux Local Security Checks	Local	high
274349	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-990425)	Nessus	Unity Linux Local Security Checks	Local	high
273014	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-988940)	Nessus	Unity Linux Local Security Checks	Local	high
270983	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-987543)	Nessus	Unity Linux Local Security Checks	Local	high
237099	SUSE SLES12 Security Update : kernel (SUSE-SU-2025:01600-1)	Nessus	SuSE Local Security Checks	Local	high
234484	SUSE SLES15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:1263-1)	Nessus	SuSE Local Security Checks	Local	high
234407	SUSE SLES15 : Security update for the Linux Kernel (SUSE-SU-2025:1241-1)	Nessus	SuSE Local Security Checks	Local	high
233410	SUSE SLES15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:1027-1)	Nessus	SuSE Local Security Checks	Local	high
225475	Linux Distros Unpatched Vulnerability : CVE-2022-49290	Nessus	Misc.	Local	high
167620	RHEL 9 : kernel (RHSA-2022:8267)	Nessus	Red Hat Local Security Checks	Local	high
167155	RHEL 8 : kernel (RHSA-2022:7683)	Nessus	Red Hat Local Security Checks	Local	high
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	Local	high

Detections

Analytics

CVE-2022-49290

high

Tenable Plugins

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high