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.