CVE-2026-80709
Description
A flaw was found in the Linux kernel's s390/zcrypt component. An incorrect upper limit check for the domain value when processing an EP11 Cryptographic Coprocessor Request Block (CPRB) can allow a local user on custom device nodes to access heap memory. This could lead to information disclosure or other memory corruption related issues.
Statement
A moderate severity flaw was found in the Linux kernel s390/zcrypt driver used on IBM Z systems. When an EP11 Cryptographic Coprocessor Request Block (CPRB) is processed for sending to a crypto card, the domain value is verified against a wrong upper limit. This check is only active on custom zcrypt device nodes, so a local user able to send an administrative CPRB with an out-of-range domain value may access heap memory behind the perms->adm structure. This out-of-bounds memory access can crash the kernel and otherwise disclose or corrupt kernel heap memory. Red Hat rates this flaw as moderate severity (CVSS 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), while the upstream CVE record scores it 7.8 (important); the difference reflects Red Hat's assessment that, in practice, the issue primarily affects availability and is reachable only by a local user with access to custom zcrypt device nodes on s390 systems. The kernel and kernel-rt packages in Red Hat Enterprise Linux 9 and 10, and the kernel packages in Red Hat In-Vehicle OS, are affected and the fix is currently deferred to a future update for those streams; the residual risk is limited because exploitation requires local access to a system with custom zcrypt device nodes configured and the ability to issue administrative EP11 requests. Red Hat Enterprise Linux 6, 7, and 8 are not affected because the vulnerable code is not present in those kernels.
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 | 7.8 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | High |
| Integrity Impact | None | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Integrity
Technical Impact: Modify Memory; Execute Unauthorized Code or Commands
Write operations could cause memory corruption. In some cases, an adversary can modify control data such as return addresses in order to execute unexpected code.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
Attempting to access out-of-range, invalid, or unauthorized memory could cause the product to crash.
Other
Technical Impact: Unexpected State
Subsequent write operations can produce undefined or unexpected results.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.