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

s390/pai: Handle multiple PMU stop callback invocations

Handle the following scenario:
The kernel protects itself against a very high sampling load and
throttles the sampling using:

perf_event_throttle() --> PMU->stop()

Shortly later the scheduler may terminate the task and removes it from the
CPU. It again calls

PMU->stop()

which results in two invocations of PMU->stop() called back to back.
Protect against this and check the PERF_HES_STOPPED bit on function
entry. If it is already set return.
Clear bit PERF_HES_STOPPED in PMU->start().

Prohibit ioctl(fd, PERF_EVENT_IOC_PERIOD, ...) call for this event.
It sets perf_event::event_limit to a positive value and causes
perf_event_overflow() to invoke pai_stop() call back function when
perf_event::event_limit hits zero. This is not supported because the
sample events CRYPTO_ALL and NNPA_ALL are only taken at schedule out
of a task.

Use list_for_each_entry_safe() for safe iteration over syswide_list
in pai_have_samples().
Published: 2026-10-28
Score: n/a
EPSS: n/a
KEV: No
Impact: Denial of Service
Action: Immediate Patch
AI Analysis

Impact

The patch addresses a flaw in the Linux s390 kernel where two consecutive calls to the PMU stop callback could occur when high sampling load triggers throttling and a task is later removed by the scheduler. Without the added guard, the second call could leave the PMU in an inconsistent state, potentially causing a kernel panic or other abnormal termination. The vulnerability is therefore a source of denial of service where an attacker could force the kernel to crash by manipulating performance monitoring events.

Affected Systems

All Linux kernel distributions utilizing the s390 architecture are affected, as the vulnerability resides in the kernel core. The patch applies to any kernel version before the change made in the commit identified by cf348ec613f75b97. No specific version ranges are listed in the data, so any release before that commit is potentially impacted.

Risk and Exploitability

The CVSS score and EPSS data are not available, and the vulnerability is not listed in the CISA KEV catalog. Based on the description, the flaw is internal to kernel performance‑monitoring handling and would require an attacker to trigger a high sampling load or to misuse perf_event calls such as PERF_EVENT_IOC_PERIOD for the restricted events. The likely attack vector involves crafted perf_event interactions that cause the kernel to issue multiple stop callbacks, leading to a service disruption. Because no exploitation indicators are present, the risk is considered moderate to high for impacted systems if left unpatched.

Generated by OpenCVE AI on October 28, 2026 at 11:44 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to a version that contains the patch from the commit cf348ec613f75b9774291e47b804fd7010835a6c
  • If an update is not immediately possible, restrict the use of performance monitoring events that trigger stop callbacks, especially disabling PERF_EVENT_IOC_PERIOD for CRYPTO_ALL and NNPA_ALL events
  • Disable or suspend the perf_event subsystem temporarily on s390 machines until the kernel patch can be applied
  • Check with your distribution’s security updates program for any vendor‑supplied package containing the fix.

Generated by OpenCVE AI on October 28, 2026 at 11:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 28 Oct 2026 12:30:00 +0000

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux

Wed, 28 Oct 2026 12:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Wed, 28 Oct 2026 10:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: s390/pai: Handle multiple PMU stop callback invocations Handle the following scenario: The kernel protects itself against a very high sampling load and throttles the sampling using: perf_event_throttle() --> PMU->stop() Shortly later the scheduler may terminate the task and removes it from the CPU. It again calls PMU->stop() which results in two invocations of PMU->stop() called back to back. Protect against this and check the PERF_HES_STOPPED bit on function entry. If it is already set return. Clear bit PERF_HES_STOPPED in PMU->start(). Prohibit ioctl(fd, PERF_EVENT_IOC_PERIOD, ...) call for this event. It sets perf_event::event_limit to a positive value and causes perf_event_overflow() to invoke pai_stop() call back function when perf_event::event_limit hits zero. This is not supported because the sample events CRYPTO_ALL and NNPA_ALL are only taken at schedule out of a task. Use list_for_each_entry_safe() for safe iteration over syswide_list in pai_have_samples().
Title s390/pai: Handle multiple PMU stop callback invocations
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-28T10:34:40.025Z

Reserved: 2026-09-25T10:25:14.393Z

Link: CVE-2026-99125

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-28T11:17:32.210

Modified: 2026-10-28T11:17:32.210

Link: CVE-2026-99125

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-28T12:15:14Z

Weaknesses