Skip to main content

Linux Kernel EUVDEUVD-2026-57922

| CVE-2026-68453 HIGH
2026-08-13 Linux GHSA-fwfm-5245-f8pj
7.1
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
7.1 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
vuln.today AI
7.1 HIGH

Local-only attack via device interface requiring low-privilege access; high C and A reflect kernel memory disclosure and crash risk; no integrity impact from read-only over-read.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
6.1 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L
Red Hat
7.0 MEDIUM
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 14, 2026 - 02:39 vuln.today
CVSS changed
Aug 13, 2026 - 23:37 NVD
7.1 (HIGH)
Patch available
Aug 13, 2026 - 15:02 EUVD
CVE Published
Aug 13, 2026 - 13:59 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 13, 2026 - 13:59 cve.org
HIGH 7.1

DescriptionCVE.org

In the Linux kernel, the following vulnerability has been resolved:

s390/zcrypt: Fix buffer over-read in cca_cipher2protkey

Add validation of both the actual key buffer size and token length fields in all the cca_check_sec*token() functions. Additionally check in cca_gencipherkey() for possible underflow with returned key size.

The CCA token structures contain user-controlled len fields that were used in operations without proper validation against both the actual buffer size and minimum token structure size. An attacker could set this field larger than the actual buffer size, leading to reading beyond buffer boundaries. This may result in a kernel crash or exposure of memory via sending this as part of a request down to the crypto card. Also an attacker could have used a very small len value and thus enforce a buffer under-run which may produce similar effects as a over-read.

So now a key must

  • key buf length must be at least sizeof the token struct
  • the key len field inside the token must fit into the range of

sizeof key token struct ... key buf length

AnalysisAI

Buffer over-read and under-run vulnerabilities in the s390/zcrypt subsystem of the Linux kernel allow a local low-privileged user on IBM Z (mainframe) hardware to crash the kernel or expose adjacent kernel memory by submitting malformed CCA key token structures with attacker-controlled length fields. The affected functions cca_check_sec*token() and cca_gencipherkey() failed to validate the token's internal len field against actual buffer boundaries or minimum structure sizes before use in memory operations. No public exploit has been identified at time of analysis, and the vulnerability is not listed in the CISA KEV catalog, though the CVSS score of 7.1 reflects genuine high-severity impacts in affected environments.

Technical ContextAI

The affected code resides in the Linux kernel's s390 architecture cryptographic subsystem (drivers/s390/crypto/), which provides the software interface to IBM Z hardware cryptographic accelerator cards (CEX cards) using the CCA (Common Cryptographic Architecture) protocol. CCA key token structures passed through this interface contain user-controlled 'len' fields that represent the declared size of the token payload. Prior to the fix, functions including cca_check_sec*token() and cca_gencipherkey() consumed these len fields in memory operations without validating them against two critical bounds: the actual allocated buffer size and the minimum valid size of the token structure. An oversized len value causes an out-of-bounds read beyond the buffer (CWE-125), while an artificially small len can produce a buffer under-run producing similar effects. The fix enforces that key buffer length must be at least sizeof(token struct) and the internal len field must fall within the range [sizeof(token struct), key buf length]. The CPE identifier is cpe:2.3:a:linux:linux and the vulnerability is strictly architecture-scoped to s390/IBM Z.

RemediationAI

Upgrade to a patched Linux kernel version: 6.18.44 or 7.1.8 as confirmed by EUVD data, or apply the upstream stable fix commits at https://git.kernel.org/stable/c/a57fd7fcdb63e2d5ceac78bbe825ec986062a9da (one stable branch), https://git.kernel.org/stable/c/3b2abee2a678607ae27975bc6833785c2002df43, and https://git.kernel.org/stable/c/36b230835b8a008266aad22168ca52afacc8a58d. Note that exact patched versions for all active stable series (e.g., 5.4.x) are not independently confirmed beyond these commit references - verify with your distribution vendor. As a compensating control where patching is not immediately feasible, restrict access permissions on zcrypt device nodes (typically /dev/zcrypt, /dev/z90crypt) to only trusted service accounts, preventing unprivileged local users from submitting crafted token structures. This workaround may impact legitimate cryptographic workloads that depend on hardware acceleration and should be evaluated against operational requirements before applying.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

EUVD-2026-57922 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy