CVE-2026-97588
Description
A flaw was found in the Linux kernel's s390 cryptographic subsystem. This vulnerability allows a local user to cause a Denial of Service (DoS) by executing cryptographic operations when underlying hardware repeatedly reports a busy state. Because the subsystem fails to properly translate persistent busy errors during key conversion, the cryptographic framework incorrectly treats the failure as a queued request, preventing completion callbacks from firing and causing calling processes to hang indefinitely.
Statement
A low impact denial of service flaw was found in the Linux kernel's s390 cryptographic subsystem. When the underlying crypto hardware persistently reports a busy (-EBUSY) status after retries are exhausted during key conversion, the driver propagates -EBUSY to the crypto API completion wrapper, which interprets it as a queueing status rather than a terminal failure. As a result, the completion callback never fires, and processes waiting via crypto_wait_req() block indefinitely. A local user able to initiate cryptographic operations on an affected s390 system can therefore cause those processes to hang; there is no impact on confidentiality or integrity. Because triggering the hang requires an uncommon, persistent hardware busy condition outside the attacker's direct control, Red Hat rates the impact of this flaw as low, even though the CVSS:3.1 base score is moderate (5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). The vulnerable code is only present in recent kernels: Red Hat Enterprise Linux 6, 7, 8, and 9 (including the corresponding kernel-rt and RHEL CoreOS-based OpenShift releases) are not affected because the vulnerable code is not present, while Red Hat Enterprise Linux 10 and Red Hat In-Vehicle OS 2 are affected. The fix is currently deferred for the affected streams; the residual risk is limited to a local, condition-dependent hang of tasks performing s390 cryptographic operations, with no memory corruption or privilege escalation.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Integrity,Other
Technical Impact: Unexpected State; Alter Execution Logic
This weakness can lead to unpredictable behavior. If the function is used to make security-critical decisions or provide security-critical information, then the wrong status code can cause the product to assume that an action is safe or correct, even when it is not. This weakness could place the system in a state that could lead unexpected logic to be executed or other unintended behaviors.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.