CVE-2026-80550
Description
A flaw was found in the s390/vfio_ccw component of the Linux kernel. The ccwchain_calc_length() routine, which counts channel command words (CCWs), incorrectly checked array boundaries. This could lead to an out-of-bounds read, where the system attempts to access memory beyond its allocated limits. Such an issue could potentially cause system instability or lead to the disclosure of sensitive information.
Statement
A moderate out-of-bounds read flaw was found in the s390 vfio_ccw driver of the Linux kernel as shipped in Red Hat Enterprise Linux 9 and 10 and Red Hat In-Vehicle OS. The ccwchain_calc_length() routine counts the channel command words (CCWs) chained in a channel program submitted through a vfio-ccw mediated device and rejects programs longer than 256 CCWs, but its loop condition allowed a possible 257th CCW to be examined before the program was rejected, reading one element beyond the allocated CCW array. Exploiting this requires local, privileged access in a context that can submit channel programs to a vfio-ccw device on s390 hardware, for example a guest with such a device assigned; the flaw is not network-reachable. The main consequence assessed by Red Hat is an impact to system availability (kernel instability), with at most a theoretical disclosure of adjacent memory. Red Hat Enterprise Linux 6, 7, and 8 are not affected because the vulnerable code is not present in those releases. For the affected releases the fix is deferred: the issue is a single-element out-of-bounds read restricted to specific s390 vfio-ccw configurations and rated moderate, so the residual risk is limited to s390 deployments that expose vfio-ccw mediated devices to privileged local users or guests until a fix is delivered. Red Hat rates this flaw MODERATE (CVSS 5.5, availability impact only), which differs from the upstream CVEORG rating of 7.9/IMPORTANT because the upstream score credits high confidentiality impact, whereas Red Hat's assessment finds the realistic impact to be availability.
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.9 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Changed |
| Confidentiality | None | N/A | High |
| Integrity Impact | None | N/A | None |
| Availability Impact | High | N/A | Low |
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:N/UI:N/S:C/C:H/I:N/A:L
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Memory
An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.
Confidentiality
Technical Impact: Bypass Protection Mechanism
Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.
Availability
Technical Impact: DoS: Crash, Exit, or Restart
An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.
Other
Technical Impact: Varies by Context
The read operation could produce other 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.