In the Linux kernel, the following vulnerability has been resolved: powerpc/perf: Optimize clearing the pending PMI and remove WARN_ON for PMI check in power_pmu_disable commit 2c9ac51b850d ("powerpc/perf: Fix PMU callbacks to clear pending PMI before resetting an overflown PMC") added a new function "pmi_irq_pending" in hw_irq.h. This function is to check if there is a PMI marked as pending in Paca (PACA_IRQ_PMI).This is used in power_pmu_disable in a WARN_ON. The intention here is to provide a warning if there is PMI pending, but no counter is found overflown. During some of the perf runs, below warning is hit: WARNING: CPU: 36 PID: 0 at arch/powerpc/perf/core-book3s.c:1332 power_pmu_disable+0x25c/0x2c0 Modules linked in: ----- NIP [c000000000141c3c] power_pmu_disable+0x25c/0x2c0 LR [c000000000141c8c] power_pmu_disable+0x2ac/0x2c0 Call Trace: [c000000baffcfb90] [c000000000141c8c] power_pmu_disable+0x2ac/0x2c0 (unreliable) [c000000baffcfc10] [c0000000003e2f8c] perf_pmu_disable+0x4c/0x60 [c000000baffcfc30] [c0000000003e3344] group_sched_out.part.124+0x44/0x100 [c000000baffcfc80] [c0000000003e353c] __perf_event_disable+0x13c/0x240 [c000000baffcfcd0] [c0000000003dd334] event_function+0xc4/0x140 [c000000baffcfd20] [c0000000003d855c] remote_function+0x7c/0xa0 [c000000baffcfd50] [c00000000026c394] flush_smp_call_function_queue+0xd4/0x300 [c000000baffcfde0] [c000000000065b24] smp_ipi_demux_relaxed+0xa4/0x100 [c000000baffcfe20] [c0000000000cb2b0] xive_muxed_ipi_action+0x20/0x40 [c000000baffcfe40] [c000000000207c3c] __handle_irq_event_percpu+0x8c/0x250 [c000000baffcfee0] [c000000000207e2c] handle_irq_event_percpu+0x2c/0xa0 [c000000baffcff10] [c000000000210a04] handle_percpu_irq+0x84/0xc0 [c000000baffcff40] [c000000000205f14] generic_handle_irq+0x54/0x80 [c000000baffcff60] [c000000000015740] __do_irq+0x90/0x1d0 [c000000baffcff90] [c000000000016990] __do_IRQ+0xc0/0x140 [c0000009732f3940] [c000000bafceaca8] 0xc000000bafceaca8 [c0000009732f39d0] [c000000000016b78] do_IRQ+0x168/0x1c0 [c0000009732f3a00] [c0000000000090c8] hardware_interrupt_common_virt+0x218/0x220 This means that there is no PMC overflown among the active events in the PMU, but there is a PMU pending in Paca. The function "any_pmc_overflown" checks the PMCs on active events in cpuhw->n_events. Code snippet: <<>> if (any_pmc_overflown(cpuhw)) clear_pmi_irq_pending(); else WARN_ON(pmi_irq_pending()); <<>> Here the PMC overflown is not from active event. Example: When we do perf record, default cycles and instructions will be running on PMC6 and PMC5 respectively. It could happen that overflowed event is currently not active and pending PMI is for the inactive event. Debug logs from trace_printk: <<>> any_pmc_overflown: idx is 5: pmc value is 0xd9a power_pmu_disable: PMC1: 0x0, PMC2: 0x0, PMC3: 0x0, PMC4: 0x0, PMC5: 0xd9a, PMC6: 0x80002011 <<>> Here active PMC (from idx) is PMC5 , but overflown PMC is PMC6(0x80002011). When we handle PMI interrupt for such cases, if the PMC overflown is from inactive event, it will be ignored. Reference commit: commit bc09c219b2e6 ("powerpc/perf: Fix finding overflowed PMC in interrupt") Patch addresses two changes: 1) Fix 1 : Removal of warning ( WARN_ON(pmi_irq_pending()); ) We were printing warning if no PMC is found overflown among active PMU events, but PMI pending in PACA. But this could happen in cases where PMC overflown is not in active PMC. An inactive event could have caused the overflow. Hence the warning is not needed. To know pending PMI is from an inactive event, we need to loop through all PMC's which will cause more SPR reads via mfspr and increase in context switch. Also in existing function: perf_event_interrupt, already we ignore PMI's overflown when it is from an inactive PMC. 2) Fix 2: optimization in clearing pending PMI. Currently we check for any active PMC overflown before clearing PMI pending in Paca. This is causing additional SP ---truncated---

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

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

    powerpc/perf: Optimize clearing the pending PMI and remove WARN_ON for PMI check in power_pmu_disable

    commit 2c9ac51b850d (powerpc/perf: Fix PMU callbacks to clear     pending PMI before resetting an overflown PMC) added a new     function pmi_irq_pending in hw_irq.h. This function is to check     if there is a PMI marked as pending in Paca (PACA_IRQ_PMI).This is     used in power_pmu_disable in a WARN_ON. The intention here is to     provide a warning if there is PMI pending, but no counter is found     overflown.

    During some of the perf runs, below warning is hit:

    WARNING: CPU: 36 PID: 0 at arch/powerpc/perf/core-book3s.c:1332 power_pmu_disable+0x25c/0x2c0      Modules linked in:
     -----

     NIP [c000000000141c3c] power_pmu_disable+0x25c/0x2c0      LR [c000000000141c8c] power_pmu_disable+0x2ac/0x2c0      Call Trace:
     [c000000baffcfb90] [c000000000141c8c] power_pmu_disable+0x2ac/0x2c0 (unreliable)      [c000000baffcfc10] [c0000000003e2f8c] perf_pmu_disable+0x4c/0x60      [c000000baffcfc30] [c0000000003e3344] group_sched_out.part.124+0x44/0x100      [c000000baffcfc80] [c0000000003e353c] __perf_event_disable+0x13c/0x240      [c000000baffcfcd0] [c0000000003dd334] event_function+0xc4/0x140      [c000000baffcfd20] [c0000000003d855c] remote_function+0x7c/0xa0      [c000000baffcfd50] [c00000000026c394] flush_smp_call_function_queue+0xd4/0x300      [c000000baffcfde0] [c000000000065b24] smp_ipi_demux_relaxed+0xa4/0x100      [c000000baffcfe20] [c0000000000cb2b0] xive_muxed_ipi_action+0x20/0x40      [c000000baffcfe40] [c000000000207c3c] __handle_irq_event_percpu+0x8c/0x250      [c000000baffcfee0] [c000000000207e2c] handle_irq_event_percpu+0x2c/0xa0      [c000000baffcff10] [c000000000210a04] handle_percpu_irq+0x84/0xc0      [c000000baffcff40] [c000000000205f14] generic_handle_irq+0x54/0x80      [c000000baffcff60] [c000000000015740] __do_irq+0x90/0x1d0      [c000000baffcff90] [c000000000016990] __do_IRQ+0xc0/0x140      [c0000009732f3940] [c000000bafceaca8] 0xc000000bafceaca8      [c0000009732f39d0] [c000000000016b78] do_IRQ+0x168/0x1c0      [c0000009732f3a00] [c0000000000090c8] hardware_interrupt_common_virt+0x218/0x220

    This means that there is no PMC overflown among the active events     in the PMU, but there is a PMU pending in Paca. The function     any_pmc_overflown checks the PMCs on active events in     cpuhw->n_events. Code snippet:

    <<>>     if (any_pmc_overflown(cpuhw))             clear_pmi_irq_pending();
     else             WARN_ON(pmi_irq_pending());
    <<>>

    Here the PMC overflown is not from active event. Example: When we do     perf record, default cycles and instructions will be running on PMC6     and PMC5 respectively. It could happen that overflowed event is currently     not active and pending PMI is for the inactive event. Debug logs from     trace_printk:

    <<>>     any_pmc_overflown: idx is 5: pmc value is 0xd9a     power_pmu_disable: PMC1: 0x0, PMC2: 0x0, PMC3: 0x0, PMC4: 0x0, PMC5: 0xd9a, PMC6: 0x80002011     <<>>

    Here active PMC (from idx) is PMC5 , but overflown PMC is PMC6(0x80002011).
    When we handle PMI interrupt for such cases, if the PMC overflown is     from inactive event, it will be ignored. Reference commit:
    commit bc09c219b2e6 (powerpc/perf: Fix finding overflowed PMC in interrupt)

    Patch addresses two changes:
    1) Fix 1 : Removal of warning ( WARN_ON(pmi_irq_pending()); )        We were printing warning if no PMC is found overflown among active PMU        events, but PMI pending in PACA. But this could happen in cases where        PMC overflown is not in active PMC. An inactive event could have caused        the overflow. Hence the warning is not needed. To know pending PMI is        from an inactive event, we need to loop through all PMC's which will        cause more SPR reads via mfspr and increase in context switch. Also in        existing function: perf_event_interrupt, already we ignore PMI's        overflown when it is from an inactive PMC.

    2) Fix 2: optimization in clearing pending PMI.
       Currently we check for any active PMC overflown before clearing PMI        pending in Paca. This is causing additional SP
    ---truncated---

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

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

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

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

    powerpc/perf: Optimize clearing the pending PMI and remove WARN_ON for PMI check in power_pmu_disable

    commit 2c9ac51b850d (powerpc/perf: Fix PMU callbacks to clear     pending PMI before resetting an overflown PMC) added a new     function pmi_irq_pending in hw_irq.h. This function is to check     if there is a PMI marked as pending in Paca (PACA_IRQ_PMI).This is     used in power_pmu_disable in a WARN_ON. The intention here is to     provide a warning if there is PMI pending, but no counter is found     overflown.

    During some of the perf runs, below warning is hit:

    WARNING: CPU: 36 PID: 0 at arch/powerpc/perf/core-book3s.c:1332 power_pmu_disable+0x25c/0x2c0      Modules linked in:
     -----

     NIP [c000000000141c3c] power_pmu_disable+0x25c/0x2c0      LR [c000000000141c8c] power_pmu_disable+0x2ac/0x2c0      Call Trace:
     [c000000baffcfb90] [c000000000141c8c] power_pmu_disable+0x2ac/0x2c0 (unreliable)      [c000000baffcfc10] [c0000000003e2f8c] perf_pmu_disable+0x4c/0x60      [c000000baffcfc30] [c0000000003e3344] group_sched_out.part.124+0x44/0x100      [c000000baffcfc80] [c0000000003e353c] __perf_event_disable+0x13c/0x240      [c000000baffcfcd0] [c0000000003dd334] event_function+0xc4/0x140      [c000000baffcfd20] [c0000000003d855c] remote_function+0x7c/0xa0      [c000000baffcfd50] [c00000000026c394] flush_smp_call_function_queue+0xd4/0x300      [c000000baffcfde0] [c000000000065b24] smp_ipi_demux_relaxed+0xa4/0x100      [c000000baffcfe20] [c0000000000cb2b0] xive_muxed_ipi_action+0x20/0x40      [c000000baffcfe40] [c000000000207c3c] __handle_irq_event_percpu+0x8c/0x250      [c000000baffcfee0] [c000000000207e2c] handle_irq_event_percpu+0x2c/0xa0      [c000000baffcff10] [c000000000210a04] handle_percpu_irq+0x84/0xc0      [c000000baffcff40] [c000000000205f14] generic_handle_irq+0x54/0x80      [c000000baffcff60] [c000000000015740] __do_irq+0x90/0x1d0      [c000000baffcff90] [c000000000016990] __do_IRQ+0xc0/0x140      [c0000009732f3940] [c000000bafceaca8] 0xc000000bafceaca8      [c0000009732f39d0] [c000000000016b78] do_IRQ+0x168/0x1c0      [c0000009732f3a00] [c0000000000090c8] hardware_interrupt_common_virt+0x218/0x220

    This means that there is no PMC overflown among the active events     in the PMU, but there is a PMU pending in Paca. The function     any_pmc_overflown checks the PMCs on active events in     cpuhw->n_events. Code snippet:

    <<>>     if (any_pmc_overflown(cpuhw))             clear_pmi_irq_pending();
     else             WARN_ON(pmi_irq_pending());
    <<>>

    Here the PMC overflown is not from active event. Example: When we do     perf record, default cycles and instructions will be running on PMC6     and PMC5 respectively. It could happen that overflowed event is currently     not active and pending PMI is for the inactive event. Debug logs from     trace_printk:

    <<>>     any_pmc_overflown: idx is 5: pmc value is 0xd9a     power_pmu_disable: PMC1: 0x0, PMC2: 0x0, PMC3: 0x0, PMC4: 0x0, PMC5: 0xd9a, PMC6: 0x80002011     <<>>

    Here active PMC (from idx) is PMC5 , but overflown PMC is PMC6(0x80002011).
    When we handle PMI interrupt for such cases, if the PMC overflown is     from inactive event, it will be ignored. Reference commit:
    commit bc09c219b2e6 (powerpc/perf: Fix finding overflowed PMC in interrupt)

    Patch addresses two changes:
    1) Fix 1 : Removal of warning ( WARN_ON(pmi_irq_pending()); )        We were printing warning if no PMC is found overflown among active PMU        events, but PMI pending in PACA. But this could happen in cases where        PMC overflown is not in active PMC. An inactive event could have caused        the overflow. Hence the warning is not needed. To know pending PMI is        from an inactive event, we need to loop through all PMC's which will        cause more SPR reads via mfspr and increase in context switch. Also in        existing function: perf_event_interrupt, already we ignore PMI's        overflown when it is from an inactive PMC.

    2) Fix 2: optimization in clearing pending PMI.
       Currently we check for any active PMC overflown before clearing PMI        pending in Paca. This is causing additional SP
    ---truncated---

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

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

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

  - In the Linux kernel, the following vulnerability has been resolved: powerpc/perf: Optimize clearing the     pending PMI and remove WARN_ON for PMI check in power_pmu_disable commit 2c9ac51b850d (powerpc/perf: Fix     PMU callbacks to clear pending PMI before resetting an overflown PMC) added a new function     pmi_irq_pending in hw_irq.h. This function is to check if there is a PMI marked as pending in Paca     (PACA_IRQ_PMI).This is used in power_pmu_disable in a WARN_ON. The intention here is to provide a warning     if there is PMI pending, but no counter is found overflown. During some of the perf runs, below warning is     hit: WARNING: CPU: 36 PID: 0 at arch/powerpc/perf/core-book3s.c:1332 power_pmu_disable+0x25c/0x2c0 Modules     linked in: ----- NIP [c000000000141c3c] power_pmu_disable+0x25c/0x2c0 LR [c000000000141c8c]     power_pmu_disable+0x2ac/0x2c0 Call Trace: [c000000baffcfb90] [c000000000141c8c]     power_pmu_disable+0x2ac/0x2c0 (unreliable) [c000000baffcfc10] [c0000000003e2f8c]     perf_pmu_disable+0x4c/0x60 [c000000baffcfc30] [c0000000003e3344] group_sched_out.part.124+0x44/0x100     [c000000baffcfc80] [c0000000003e353c] __perf_event_disable+0x13c/0x240 [c000000baffcfcd0]     [c0000000003dd334] event_function+0xc4/0x140 [c000000baffcfd20] [c0000000003d855c]     remote_function+0x7c/0xa0 [c000000baffcfd50] [c00000000026c394] flush_smp_call_function_queue+0xd4/0x300     [c000000baffcfde0] [c000000000065b24] smp_ipi_demux_relaxed+0xa4/0x100 [c000000baffcfe20]     [c0000000000cb2b0] xive_muxed_ipi_action+0x20/0x40 [c000000baffcfe40] [c000000000207c3c]
    __handle_irq_event_percpu+0x8c/0x250 [c000000baffcfee0] [c000000000207e2c]     handle_irq_event_percpu+0x2c/0xa0 [c000000baffcff10] [c000000000210a04] handle_percpu_irq+0x84/0xc0     [c000000baffcff40] [c000000000205f14] generic_handle_irq+0x54/0x80 [c000000baffcff60] [c000000000015740]
    __do_irq+0x90/0x1d0 [c000000baffcff90] [c000000000016990] __do_IRQ+0xc0/0x140 [c0000009732f3940]     [c000000bafceaca8] 0xc000000bafceaca8 [c0000009732f39d0] [c000000000016b78] do_IRQ+0x168/0x1c0     [c0000009732f3a00] [c0000000000090c8] hardware_interrupt_common_virt+0x218/0x220 This means that there is     no PMC overflown among the active events in the PMU, but there is a PMU pending in Paca. The function     any_pmc_overflown checks the PMCs on active events in cpuhw->n_events. Code snippet: <<>> if     (any_pmc_overflown(cpuhw)) clear_pmi_irq_pending(); else WARN_ON(pmi_irq_pending()); <<>> Here the PMC     overflown is not from active event. Example: When we do perf record, default cycles and instructions will     be running on PMC6 and PMC5 respectively. It could happen that overflowed event is currently not active     and pending PMI is for the inactive event. Debug logs from trace_printk: <<>> any_pmc_overflown: idx is 5:
    pmc value is 0xd9a power_pmu_disable: PMC1: 0x0, PMC2: 0x0, PMC3: 0x0, PMC4: 0x0, PMC5: 0xd9a, PMC6:
    0x80002011 <<>> Here active PMC (from idx) is PMC5 , but overflown PMC is PMC6(0x80002011). When we handle     PMI interrupt for such cases, if the PMC overflown is from inactive event, it will be ignored. Reference     commit: commit bc09c219b2e6 (powerpc/perf: Fix finding overflowed PMC in interrupt) Patch addresses two     changes: 1) Fix 1 : Removal of warning ( WARN_ON(pmi_irq_pending()); ) We were printing warning if no PMC     is found overflown among active PMU events, but PMI pending in PACA. But this could happen in cases where     PMC overflown is not in active PMC. An inactive event could have caused the overflow. Hence the warning is     not needed. To know pending PMI is from an inactive event, we need to loop through all PMC's which will     cause more SPR reads via mfspr and increase in context switch. Also in existing function:
    perf_event_interrupt, already we ignore PMI's overflown when it is from an inactive PMC. 2) Fix 2:
    optimization in clearing pending PMI. Currently we check for any active PMC overflown before clearing PMI     pending in Paca. This is causing additional SP ---truncated--- (CVE-2022-50118)

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

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

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.

ID	Name	Product	Family	Severity
281127	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2025-993289)	Nessus	Unity Linux Local Security Checks	medium
280452	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2025-992472)	Nessus	Unity Linux Local Security Checks	medium
246633	Linux Distros Unpatched Vulnerability : CVE-2022-50118	Nessus	Misc.	medium
242951	SUSE SLES15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:02537-1)	Nessus	SuSE Local Security Checks	high
242100	SUSE SLES15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:02308-1)	Nessus	SuSE Local Security Checks	high
241963	SUSE SLES15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:02264-1)	Nessus	SuSE Local Security Checks	high

Detections

Analytics

CVE-2022-50118

medium

Tenable Plugins

medium

medium

medium

high

high

high