s390/pai: Handle multiple PMU stop callback invocations
Impact
In the Linux kernel, the following vulnerability has been resolved:
Source excerpt · LinuxAffected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
Linux · Linux
Other versions: unaffected
| Version / range | Source status |
|---|---|
| 9f66572f2889a5e72a9d7e17787e52f03b1f7bd8 to before cf348ec613f75b9774291e47b804fd7010835a6c | affected |
| 9f66572f2889a5e72a9d7e17787e52f03b1f7bd8 to before f3110e969ad226ffbb2d9b4bf5387e68d0d9ef40 | affected |
Linux · Linux
Other versions: affected
| Version / range | Source status |
|---|---|
| 6.11 | affected |
| 0 to before 6.11 | unaffected |
| 7.2.13 through 7.2.* (inclusive) | unaffected |
| 7.3 through * (inclusive) | unaffected |
Original source 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().