CVE-2026-97589

Description

A flaw was found in the Linux kernel's s390 cryptographic drivers. When handling asynchronous cryptographic operations, certain request callbacks incorrectly propagate error codes back to the crypto engine after already completing a request. This causes the crypto engine to mistakenly perform a second completion on the same request. A local user submitting cryptographic requests that encounter errors could trigger this condition, potentially leading to a kernel crash and a Denial of Service (DoS).

Statement

The s390 protected key AES and PHMAC do_one_request callbacks explicitly finalize an asynchronous crypto request but return the negative operation result to the crypto engine. The engine can interpret this return value as a failure to take ownership and complete the same request for a second time. The first completion callback may release the request or related state before the second completion accesses it, creating a potential use after free or double free condition. For the CVSS the PR:L value is used because a local user or process must access the affected crypto algorithm and submit an operation that reaches an error path. The issue is not directly network reachable. Impact is at least a local denial of service via kernel crash and in the worst case may include confidentiality and integrity impact if the double completion produces exploitable memory corruption.

Mitigation

Mitigation for this issue is either not available or the currently available options don't 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 HatNVDcve.org
Base Score5.8N/A7
Attack VectorLocalN/ALocal
Attack ComplexityHighN/AHigh
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityLowN/AHigh
Integrity ImpactLowN/AHigh
Availability ImpactHighN/AHigh

Vector

Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H

cve.org: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Understanding the Weakness (CWE)

Integrity

Technical Impact: Modify Memory

The use of previously freed memory may corrupt valid data, if the memory area in question has been allocated and used properly elsewhere.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

If chunk consolidation occurs after the use of previously freed data, the process may crash when invalid data is used as chunk information.

Confidentiality

Technical Impact: Read Memory

Read operations on freed memory can sometimes leak sensitive information instead of causing a crash

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

If malicious data is entered before chunk consolidation can take place, it may be possible to take advantage of a write-what-where primitive to execute arbitrary code. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Frequently Asked Questions

Want to get errata notifications? Sign up here.