CVE-2026-99125

s390/pai: Handle multiple PMU stop callback invocations

Published Oct 28, 2026 CVSS 3.1 · 5.5 Medium EPSS < 1% KEV · Not listed
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().

Analysis

AI-generated

Technical impact

The flaw resides in the Linux s390 performance‑monitoring unit handling where two consecutive calls to the PMU stop callback can be triggered when a task is throttled for high sampling load and later removed by the scheduler. Without the added guard, the second invocation corrupts the PMU state and can lead to a kernel panic, effectively shutting down the system.

Affected Systems

Linux kernels running on IBM s390 hardware that have not incorporated the commit cf348ec613f75b9774291e47b804fd7010835a6c are affected. Distribution kernels containing this change are therefore the only ones that are safe; any kernel without it is vulnerable.

Risk and Exploitability

The CVSS score of 5.5 indicates moderate severity, while the EPSS score of < 1% suggests a low likelihood of exploitation in the wild. Based on the description, it is inferred that an attacker would need elevated privileges to generate a high sampling load or misuse the PERF_EVENT_IOC_PERIOD ioctl to trigger repeated PMU stop callbacks. Because the vulnerability is not in the CISA KEV catalog, there is no evidence of widespread exploitation, but if an attacker can force a kernel panic the impact is a denial of service for the affected system.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a kernel update that includes the commit cf348ec613f75b9774291e47b804fd7010835a6c
  • If an update cannot be applied immediately, disable or restrict the use of perf_event features that trigger PMU stop callbacks, particularly disabling PERF_EVENT_IOC_PERIOD for CRYPTO_ALL and NNPA_ALL events
  • Suspend or deactivate the perf_event subsystem on s390 machines until the patch is in place

Generated by OpenCVE AI on October 30, 2026 at 05:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-665
Type Values Removed Values Added
Weaknesses CWE-1341
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Weaknesses CWE-665
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
Weaknesses
  • CWE-1341

    Multiple Releases of Same Resource or Handle

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 28, 2026, 10:34 AM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Oct 28, 2026, 11:17 AM
Severity
Moderate
Public date
Oct 28, 2026, 10:34 AM