CVE-2025-39726

In the Linux kernel, the following vulnerability has been resolved: s390/ism: fix concurrency management in ism_cmd() The s390x ISM device data sheet clearly states that only one request-response sequence is allowable per ISM function at any point in time. Unfortunately as of today the s390/ism driver in Linux does not honor that requirement. This patch aims to rectify that. This problem was discovered based on Aliaksei's bug report which states that for certain workloads the ISM functions end up entering error state (with PEC 2 as seen from the logs) after a while and as a consequence connections handled by the respective function break, and for future connection requests the ISM device is not considered -- given it is in a dysfunctional state. During further debugging PEC 3A was observed as well. A kernel message like [ 1211.244319] zpci: 061a:00:00.0: Event 0x2 reports an error for PCI function 0x61a is a reliable indicator of the stated function entering error state with PEC 2. Let me also point out that a kernel message like [ 1211.244325] zpci: 061a:00:00.0: The ism driver bound to the device does not support error recovery is a reliable indicator that the ISM function won't be auto-recovered because the ISM driver currently lacks support for it. On a technical level, without this synchronization, commands (inputs to the FW) may be partially or fully overwritten (corrupted) by another CPU trying to issue commands on the same function. There is hard evidence that this can lead to DMB token values being used as DMB IOVAs, leading to PEC 2 PCI events indicating invalid DMA. But this is only one of the failure modes imaginable. In theory even completely losing one command and executing another one twice and then trying to interpret the outputs as if the command we intended to execute was actually executed and not the other one is also possible. Frankly, I don't feel confident about providing an exhaustive list of possible consequences.

• CWE-362

• https://git.kernel.org/stable/c/1194ad0d44d66b273a02a3a22882dc863a68d764Patch
• https://git.kernel.org/stable/c/897e8601b9cff1d054cdd53047f568b0e1995726Patch
• https://git.kernel.org/stable/c/faf44487dfc80817f178dc8de7a0b73f960d019bPatch
• https://git.kernel.org/stable/c/fafaa4982bedb5532f5952000f714a3e63023f40Patch

Published

Sep 5, 2025

Last Modified

Jul 30, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2025-39720In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39721In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39722In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39723In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-39724In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39725In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39727In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-39728In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-39729In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2025-3973A vulnerability, which was classified as critical, was found…9.8
• CVE-2025-39730In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2025-39731In the Linux kernel, the following vulnerability has been re…5.5