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

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

    clk: qcom: ipq8074: dont disable gcc_sleep_clk_src

    Once the usb sleep clocks are disabled, clock framework is trying to     disable the sleep clock source also.

    However, it seems that it cannot be disabled and trying to do so produces:
    [  245.436390] ------------[ cut here ]------------     [  245.441233] gcc_sleep_clk_src status stuck at 'on'     [  245.441254] WARNING: CPU: 2 PID: 223 at clk_branch_wait+0x130/0x140     [  245.450435] Modules linked in: xhci_plat_hcd xhci_hcd dwc3 dwc3_qcom leds_gpio     [  245.456601] CPU: 2 PID: 223 Comm: sh Not tainted 5.18.0-rc4 #215     [  245.463889] Hardware name: Xiaomi AX9000 (DT)     [  245.470050] pstate: 204000c5 (nzCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)     [  245.474307] pc : clk_branch_wait+0x130/0x140     [  245.481073] lr : clk_branch_wait+0x130/0x140     [  245.485588] sp : ffffffc009f2bad0     [  245.489838] x29: ffffffc009f2bad0 x28: ffffff8003e6c800 x27: 0000000000000000     [  245.493057] x26: 0000000000000000 x25: 0000000000000000 x24: ffffff800226ef20     [  245.500175] x23: ffffffc0089ff550 x22: 0000000000000000 x21: ffffffc008476ad0     [  245.507294] x20: 0000000000000000 x19: ffffffc00965ac70 x18: fffffffffffc51a7     [  245.514413] x17: 68702e3030303837 x16: 3a6d726f6674616c x15: ffffffc089f2b777     [  245.521531] x14: ffffffc0095c9d18 x13: 0000000000000129 x12: 0000000000000129     [  245.528649] x11: 00000000ffffffea x10: ffffffc009621d18 x9 : 0000000000000001     [  245.535767] x8 : 0000000000000001 x7 : 0000000000017fe8 x6 : 0000000000000001     [  245.542885] x5 : ffffff803fdca6d8 x4 : 0000000000000000 x3 : 0000000000000027     [  245.550002] x2 : 0000000000000027 x1 : 0000000000000023 x0 : 0000000000000026     [  245.557122] Call trace:
    [  245.564229]  clk_branch_wait+0x130/0x140     [  245.566490]  clk_branch2_disable+0x2c/0x40     [  245.570656]  clk_core_disable+0x60/0xb0     [  245.574561]  clk_core_disable+0x68/0xb0     [  245.578293]  clk_disable+0x30/0x50     [  245.582113]  dwc3_qcom_remove+0x60/0xc0 [dwc3_qcom]     [  245.585588]  platform_remove+0x28/0x60     [  245.590361]  device_remove+0x4c/0x80     [  245.594179]  device_release_driver_internal+0x1dc/0x230     [  245.597914]  device_driver_detach+0x18/0x30     [  245.602861]  unbind_store+0xec/0x110     [  245.607027]  drv_attr_store+0x24/0x40     [  245.610847]  sysfs_kf_write+0x44/0x60     [  245.614405]  kernfs_fop_write_iter+0x128/0x1c0     [  245.618052]  new_sync_write+0xc0/0x130     [  245.622391]  vfs_write+0x1d4/0x2a0     [  245.626123]  ksys_write+0x58/0xe0     [  245.629508]  __arm64_sys_write+0x1c/0x30     [  245.632895]  invoke_syscall.constprop.0+0x5c/0x110     [  245.636890]  do_el0_svc+0xa0/0x150     [  245.641488]  el0_svc+0x18/0x60     [  245.644872]  el0t_64_sync_handler+0xa4/0x130     [  245.647914]  el0t_64_sync+0x174/0x178     [  245.652340] ---[ end trace 0000000000000000 ]---

    So, add CLK_IS_CRITICAL flag to the clock so that the kernel won't try     to disable the sleep clock.

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 SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:02537-1 advisory.

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


    The following security bugs were fixed:

    - CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).
    - CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361     bsc#1226552).
    - CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).
    - CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).
    - CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain     (bsc#1222634).
    - CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).
    - CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).
    - CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).
    - CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).
    - CVE-2024-53057: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT (bsc#1233551).
    - CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).
    - CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).
    - CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).
    - CVE-2024-57947: netfilter: nf_set_pipapo: fix initial map fill (bsc#1236333).
    - CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).
    - CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (bsc#1237312).
    - CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
    - CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).
    - CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses     (bsc#1242782).
    - CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).
    - CVE-2025-37797: net_sched: hfsc: Fix a UAF vulnerability in class handling (bsc#1242417).
    - CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).
    - CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc     (bsc#1243330).
    - CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).
    - CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).
    - CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).
    - CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
    - CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).


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.

  - clk: qcom: ipq8074: dont disable gcc_sleep_clk_src Once the usb sleep clocks are disabled, clock framework     is trying to disable the sleep clock source also. However, it seems that it cannot be disabled and trying     to do so produces: [ 245.436390] ------------[ cut here ]------------ [ 245.441233] gcc_sleep_clk_src     status stuck at 'on' [ 245.441254] WARNING: CPU: 2 PID: 223 at clk_branch_wait+0x130/0x140 [ 245.450435]     Modules linked in: xhci_plat_hcd xhci_hcd dwc3 dwc3_qcom leds_gpio [ 245.456601] CPU: 2 PID: 223 Comm: sh     Not tainted 5.18.0-rc4 #215 [ 245.463889] Hardware name: Xiaomi AX9000 (DT) [ 245.470050] pstate: 204000c5     (nzCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 245.474307] pc : clk_branch_wait+0x130/0x140 [     245.481073] lr : clk_branch_wait+0x130/0x140 [ 245.485588] sp : ffffffc009f2bad0 [ 245.489838] x29:
    ffffffc009f2bad0 x28: ffffff8003e6c800 x27: 0000000000000000 [ 245.493057] x26: 0000000000000000 x25:
    0000000000000000 x24: ffffff800226ef20 [ 245.500175] x23: ffffffc0089ff550 x22: 0000000000000000 x21:
    ffffffc008476ad0 [ 245.507294] x20: 0000000000000000 x19: ffffffc00965ac70 x18: fffffffffffc51a7 [     245.514413] x17: 68702e3030303837 x16: 3a6d726f6674616c x15: ffffffc089f2b777 [ 245.521531] x14:
    ffffffc0095c9d18 x13: 0000000000000129 x12: 0000000000000129 [ 245.528649] x11: 00000000ffffffea x10:
    ffffffc009621d18 x9 : 0000000000000001 [ 245.535767] x8 : 0000000000000001 x7 : 0000000000017fe8 x6 :
    0000000000000001 [ 245.542885] x5 : ffffff803fdca6d8 x4 : 0000000000000000 x3 : 0000000000000027 [     245.550002] x2 : 0000000000000027 x1 : 0000000000000023 x0 : 0000000000000026 [ 245.557122] Call trace: [     245.564229] clk_branch_wait+0x130/0x140 [ 245.566490] clk_branch2_disable+0x2c/0x40 [ 245.570656]     clk_core_disable+0x60/0xb0 [ 245.574561] clk_core_disable+0x68/0xb0 [ 245.578293] clk_disable+0x30/0x50 [     245.582113] dwc3_qcom_remove+0x60/0xc0 [dwc3_qcom] [ 245.585588] platform_remove+0x28/0x60 [ 245.590361]     device_remove+0x4c/0x80 [ 245.594179] device_release_driver_internal+0x1dc/0x230 [ 245.597914]     device_driver_detach+0x18/0x30 [ 245.602861] unbind_store+0xec/0x110 [ 245.607027]     drv_attr_store+0x24/0x40 [ 245.610847] sysfs_kf_write+0x44/0x60 [ 245.614405]     kernfs_fop_write_iter+0x128/0x1c0 [ 245.618052] new_sync_write+0xc0/0x130 [ 245.622391]     vfs_write+0x1d4/0x2a0 [ 245.626123] ksys_write+0x58/0xe0 [ 245.629508] __arm64_sys_write+0x1c/0x30 [     245.632895] invoke_syscall.constprop.0+0x5c/0x110 [ 245.636890] do_el0_svc+0xa0/0x150 [ 245.641488]     el0_svc+0x18/0x60 [ 245.644872] el0t_64_sync_handler+0xa4/0x130 [ 245.647914] el0t_64_sync+0x174/0x178 [     245.652340] ---[ end trace 0000000000000000 ]--- So, add CLK_IS_CRITICAL flag to the clock so that the     kernel won't try to disable the sleep clock. (CVE-2022-50029)

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

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

    clk: qcom: ipq8074: dont disable gcc_sleep_clk_src

    Once the usb sleep clocks are disabled, clock framework is trying to     disable the sleep clock source also.

    However, it seems that it cannot be disabled and trying to do so produces:
    [  245.436390] ------------[ cut here ]------------     [  245.441233] gcc_sleep_clk_src status stuck at 'on'     [  245.441254] WARNING: CPU: 2 PID: 223 at clk_branch_wait+0x130/0x140     [  245.450435] Modules linked in: xhci_plat_hcd xhci_hcd dwc3 dwc3_qcom leds_gpio     [  245.456601] CPU: 2 PID: 223 Comm: sh Not tainted 5.18.0-rc4 #215     [  245.463889] Hardware name: Xiaomi AX9000 (DT)     [  245.470050] pstate: 204000c5 (nzCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)     [  245.474307] pc : clk_branch_wait+0x130/0x140     [  245.481073] lr : clk_branch_wait+0x130/0x140     [  245.485588] sp : ffffffc009f2bad0     [  245.489838] x29: ffffffc009f2bad0 x28: ffffff8003e6c800 x27: 0000000000000000     [  245.493057] x26: 0000000000000000 x25: 0000000000000000 x24: ffffff800226ef20     [  245.500175] x23: ffffffc0089ff550 x22: 0000000000000000 x21: ffffffc008476ad0     [  245.507294] x20: 0000000000000000 x19: ffffffc00965ac70 x18: fffffffffffc51a7     [  245.514413] x17: 68702e3030303837 x16: 3a6d726f6674616c x15: ffffffc089f2b777     [  245.521531] x14: ffffffc0095c9d18 x13: 0000000000000129 x12: 0000000000000129     [  245.528649] x11: 00000000ffffffea x10: ffffffc009621d18 x9 : 0000000000000001     [  245.535767] x8 : 0000000000000001 x7 : 0000000000017fe8 x6 : 0000000000000001     [  245.542885] x5 : ffffff803fdca6d8 x4 : 0000000000000000 x3 : 0000000000000027     [  245.550002] x2 : 0000000000000027 x1 : 0000000000000023 x0 : 0000000000000026     [  245.557122] Call trace:
    [  245.564229]  clk_branch_wait+0x130/0x140     [  245.566490]  clk_branch2_disable+0x2c/0x40     [  245.570656]  clk_core_disable+0x60/0xb0     [  245.574561]  clk_core_disable+0x68/0xb0     [  245.578293]  clk_disable+0x30/0x50     [  245.582113]  dwc3_qcom_remove+0x60/0xc0 [dwc3_qcom]     [  245.585588]  platform_remove+0x28/0x60     [  245.590361]  device_remove+0x4c/0x80     [  245.594179]  device_release_driver_internal+0x1dc/0x230     [  245.597914]  device_driver_detach+0x18/0x30     [  245.602861]  unbind_store+0xec/0x110     [  245.607027]  drv_attr_store+0x24/0x40     [  245.610847]  sysfs_kf_write+0x44/0x60     [  245.614405]  kernfs_fop_write_iter+0x128/0x1c0     [  245.618052]  new_sync_write+0xc0/0x130     [  245.622391]  vfs_write+0x1d4/0x2a0     [  245.626123]  ksys_write+0x58/0xe0     [  245.629508]  __arm64_sys_write+0x1c/0x30     [  245.632895]  invoke_syscall.constprop.0+0x5c/0x110     [  245.636890]  do_el0_svc+0xa0/0x150     [  245.641488]  el0_svc+0x18/0x60     [  245.644872]  el0t_64_sync_handler+0xa4/0x130     [  245.647914]  el0t_64_sync+0x174/0x178     [  245.652340] ---[ end trace 0000000000000000 ]---

    So, add CLK_IS_CRITICAL flag to the clock so that the kernel won't try     to disable the sleep clock.

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 SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:02264-1 advisory.

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


    The following security bugs were fixed:

    - CVE-2021-47557: net/sched: sch_ets: do not peek at classes beyond 'nbands' (bsc#1207361 bsc#1225468).
    - CVE-2021-47595: net/sched: sch_ets: do not remove idle classes from the round-robin list (bsc#1207361     bsc#1226552).
    - CVE-2023-52924: netfilter: nf_tables: do not skip expired elements during walk (bsc#1236821).
    - CVE-2023-52925: netfilter: nf_tables: do not fail inserts if duplicate has expired (bsc#1236822).
    - CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain     (bsc#1222634).
    - CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).
    - CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).
    - CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).
    - CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).
    - CVE-2024-53125: bpf: sync_linked_regs() must preserve subreg_def (bsc#1234156).
    - CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).
    - CVE-2024-53197: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices     (bsc#1235464).
    - CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).
    - CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).
    - CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (bsc#1237312).
    - CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
    - CVE-2025-21756: vsock: Orphan socket after transport release (bsc#1238876).
    - CVE-2025-23141: KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses     (bsc#1242782).
    - CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).
    - CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).
    - CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc     (bsc#1243330).
    - CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).
    - CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).
    - CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).
    - CVE-2025-38014: dmaengine: idxd: Refactor remove call with idxd_cleanup() helper (bsc#1244732).
    - CVE-2025-38060: bpf: abort verification if env->cur_state->loop_entry != NULL (bsc#1245155).
    - CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).


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

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

    clk: qcom: ipq8074: dont disable gcc_sleep_clk_src

    Once the usb sleep clocks are disabled, clock framework is trying to     disable the sleep clock source also.

    However, it seems that it cannot be disabled and trying to do so produces:
    [  245.436390] ------------[ cut here ]------------     [  245.441233] gcc_sleep_clk_src status stuck at 'on'     [  245.441254] WARNING: CPU: 2 PID: 223 at clk_branch_wait+0x130/0x140     [  245.450435] Modules linked in: xhci_plat_hcd xhci_hcd dwc3 dwc3_qcom leds_gpio     [  245.456601] CPU: 2 PID: 223 Comm: sh Not tainted 5.18.0-rc4 #215     [  245.463889] Hardware name: Xiaomi AX9000 (DT)     [  245.470050] pstate: 204000c5 (nzCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)     [  245.474307] pc : clk_branch_wait+0x130/0x140     [  245.481073] lr : clk_branch_wait+0x130/0x140     [  245.485588] sp : ffffffc009f2bad0     [  245.489838] x29: ffffffc009f2bad0 x28: ffffff8003e6c800 x27: 0000000000000000     [  245.493057] x26: 0000000000000000 x25: 0000000000000000 x24: ffffff800226ef20     [  245.500175] x23: ffffffc0089ff550 x22: 0000000000000000 x21: ffffffc008476ad0     [  245.507294] x20: 0000000000000000 x19: ffffffc00965ac70 x18: fffffffffffc51a7     [  245.514413] x17: 68702e3030303837 x16: 3a6d726f6674616c x15: ffffffc089f2b777     [  245.521531] x14: ffffffc0095c9d18 x13: 0000000000000129 x12: 0000000000000129     [  245.528649] x11: 00000000ffffffea x10: ffffffc009621d18 x9 : 0000000000000001     [  245.535767] x8 : 0000000000000001 x7 : 0000000000017fe8 x6 : 0000000000000001     [  245.542885] x5 : ffffff803fdca6d8 x4 : 0000000000000000 x3 : 0000000000000027     [  245.550002] x2 : 0000000000000027 x1 : 0000000000000023 x0 : 0000000000000026     [  245.557122] Call trace:
    [  245.564229]  clk_branch_wait+0x130/0x140     [  245.566490]  clk_branch2_disable+0x2c/0x40     [  245.570656]  clk_core_disable+0x60/0xb0     [  245.574561]  clk_core_disable+0x68/0xb0     [  245.578293]  clk_disable+0x30/0x50     [  245.582113]  dwc3_qcom_remove+0x60/0xc0 [dwc3_qcom]     [  245.585588]  platform_remove+0x28/0x60     [  245.590361]  device_remove+0x4c/0x80     [  245.594179]  device_release_driver_internal+0x1dc/0x230     [  245.597914]  device_driver_detach+0x18/0x30     [  245.602861]  unbind_store+0xec/0x110     [  245.607027]  drv_attr_store+0x24/0x40     [  245.610847]  sysfs_kf_write+0x44/0x60     [  245.614405]  kernfs_fop_write_iter+0x128/0x1c0     [  245.618052]  new_sync_write+0xc0/0x130     [  245.622391]  vfs_write+0x1d4/0x2a0     [  245.626123]  ksys_write+0x58/0xe0     [  245.629508]  __arm64_sys_write+0x1c/0x30     [  245.632895]  invoke_syscall.constprop.0+0x5c/0x110     [  245.636890]  do_el0_svc+0xa0/0x150     [  245.641488]  el0_svc+0x18/0x60     [  245.644872]  el0t_64_sync_handler+0xa4/0x130     [  245.647914]  el0t_64_sync+0x174/0x178     [  245.652340] ---[ end trace 0000000000000000 ]---

    So, add CLK_IS_CRITICAL flag to the clock so that the kernel won't try     to disable the sleep clock.

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 Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:2458 advisory.

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

    Security Fix(es):

    * use-after-free in l2cap_connect and l2cap_le_connect_req in net/bluetooth/l2cap_core.c (CVE-2022-42896)

    * net/ulp: use-after-free in listening ULP sockets (CVE-2023-0461)

    * cpu: AMD CPUs may transiently execute beyond unconditional direct branch (CVE-2021-26341)

    * malicious data for FBIOPUT_VSCREENINFO ioctl may cause OOB write memory (CVE-2021-33655)

    * possible race condition in drivers/tty/tty_buffers.c (CVE-2022-1462)

    * KVM: NULL pointer dereference in kvm_mmu_invpcid_gva (CVE-2022-1789)

    * use-after-free in free_pipe_info() could lead to privilege escalation (CVE-2022-1882)

    * KVM: nVMX: missing IBPB when exiting from nested guest can lead to Spectre v2 attacks (CVE-2022-2196)

    * netfilter: nf_conntrack_irc message handling issue (CVE-2022-2663)

    * race condition in xfrm_probe_algs can lead to OOB read/write (CVE-2022-3028)

    * out-of-bounds read in fib_nh_match of the file net/ipv4/fib_semantics.c (CVE-2022-3435)

    * race condition in hugetlb_no_page() in mm/hugetlb.c (CVE-2022-3522)

    * memory leak in ipv6_renew_options() (CVE-2022-3524)

    * data races around icsk->icsk_af_ops in do_ipv6_setsockopt (CVE-2022-3566)

    * data races around sk->sk_prot (CVE-2022-3567)

    * memory leak in l2cap_recv_acldata of the file net/bluetooth/l2cap_core.c (CVE-2022-3619)

    * denial of service in follow_page_pte in mm/gup.c due to poisoned pte entry (CVE-2022-3623)

    * use-after-free after failed devlink reload in devlink_param_get (CVE-2022-3625)

    * USB-accessible buffer overflow in brcmfmac (CVE-2022-3628)

    * use after free flaw in l2cap_conn_del in net/bluetooth/l2cap_core.c (CVE-2022-3640)

    * Double-free in split_2MB_gtt_entry when function intel_gvt_dma_map_guest_page failed (CVE-2022-3707)

    * mptcp: NULL pointer dereference in subflow traversal at disconnect time (CVE-2022-4128)

    * l2tp: missing lock when clearing sk_user_data can lead to NULL pointer dereference (CVE-2022-4129)

    * igmp: use-after-free in ip_check_mc_rcu when opening and closing inet sockets (CVE-2022-20141)

    * lockdown bypass using IMA (CVE-2022-21505)

    * double free in usb_8dev_start_xmit in drivers/net/can/usb/usb_8dev.c (CVE-2022-28388)

    * network backend may cause Linux netfront to use freed SKBs (XSA-405) (CVE-2022-33743)

    * unmap_mapping_range() race with munmap() on VM_PFNMAP mappings leads to stale TLB entry (CVE-2022-39188)

    * TLB flush operations are mishandled in certain KVM_VCPU_PREEMPTED leading to guest malfunctioning     (CVE-2022-39189)

    * u8 overflow problem in cfg80211_update_notlisted_nontrans() (CVE-2022-41674)

    * use-after-free related to leaf anon_vma double reuse (CVE-2022-42703)

    * use-after-free in bss_ref_get in net/wireless/scan.c (CVE-2022-42720)

    * BSS list corruption in cfg80211_add_nontrans_list in net/wireless/scan.c (CVE-2022-42721)

    * Denial of service in beacon protection for P2P-device (CVE-2022-42722)

    * memory corruption in usbmon driver (CVE-2022-43750)

    * NULL pointer dereference in traffic control subsystem (CVE-2022-47929)

    * NULL pointer dereference in rawv6_push_pending_frames (CVE-2023-0394)

    * use-after-free due to race condition in qdisc_graft() (CVE-2023-0590)

    * use-after-free caused by invalid pointer hostname in fs/cifs/connect.c (CVE-2023-1195)

    * denial of service in tipc_conn_close (CVE-2023-1382)

    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.2 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 SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:02308-1 advisory.

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


    The following security bugs were fixed:

    - CVE-2022-50085: dm raid: fix address sanitizer warning in raid_resume (bsc#1245147).
    - CVE-2022-50087: firmware: arm_scpi: Ensure scpi_info is not assigned if the probe fails (bsc#1245119).
    - CVE-2022-50200: selinux: Add boundary check in put_entry() (bsc#1245149).
    - CVE-2024-26924: scsi: lpfc: Release hbalock before calling lpfc_worker_wake_up() (bsc#1225820).
    - CVE-2024-27397: kabi: place tstamp needed for nftables set in a hole (bsc#1224095).
    - CVE-2024-36978: net: sched: sch_multiq: fix possible OOB write in multiq_tune() (bsc#1226514).
    - CVE-2024-46800: sch/netem: fix use after free in netem_dequeue (bsc#1230827).
    - CVE-2024-53141: netfilter: ipset: add missing range check in bitmap_ip_uadt (bsc#1234381).
    - CVE-2024-56770: sch/netem: fix use after free in netem_dequeue (bsc#1235637).
    - CVE-2025-21700: net: sched: Disallow replacing of child qdisc from one parent to another (bsc#1237159).
    - CVE-2025-21702: pfifo_tail_enqueue: Drop new packet when sch->limit == 0 (bsc#1237312).
    - CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
    - CVE-2025-37752: net_sched: sch_sfq: move the limit validation (bsc#1242504).
    - CVE-2025-37823: net_sched: hfsc: Fix a potential UAF in hfsc_dequeue() too (bsc#1242924).
    - CVE-2025-37890: net_sched: hfsc: Fix a UAF vulnerability in class with netem as child qdisc     (bsc#1243330).
    - CVE-2025-37997: netfilter: ipset: fix region locking in hash types (bsc#1243832).
    - CVE-2025-38000: sch_hfsc: Fix qlen accounting bug when using peek in hfsc_enqueue() (bsc#1244277).
    - CVE-2025-38001: net_sched: hfsc: Address reentrant enqueue adding class to eltree twice (bsc#1244234).
    - CVE-2025-38083: net_sched: prio: fix a race in prio_tune() (bsc#1245183).


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
280629	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2025-992257)	Nessus	Unity Linux Local Security Checks	12/30/2025	12/30/2025	medium
242951	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:02537-1)	Nessus	SuSE Local Security Checks	7/29/2025	9/24/2025	high
249761	Linux Distros Unpatched Vulnerability : CVE-2022-50029	Nessus	Misc.	8/15/2025	1/14/2026	medium
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	7/22/2021	3/23/2026	high
307276	Unity Linux 20.1050e / 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-007367)	Nessus	Unity Linux Local Security Checks	4/17/2026	4/21/2026	medium
241963	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:02264-1)	Nessus	SuSE Local Security Checks	7/11/2025	9/24/2025	high
281319	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-993094)	Nessus	Unity Linux Local Security Checks	12/31/2025	12/31/2025	medium
175477	RHEL 9 : kernel (RHSA-2023:2458)	Nessus	Red Hat Local Security Checks	5/13/2023	9/10/2025	high
242100	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:02308-1)	Nessus	SuSE Local Security Checks	7/15/2025	9/24/2025	high

Detections

Analytics

Plugins Search

medium

high

medium

high

medium

high

medium

high

high