# CVE-2026-68452: s390/zcrypt: Validate length for CCA AES cipher key requests

> A missing length validation in the s390/zcrypt driver allows attackers to trigger memory corruption via crafted AES key requests.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-68452, DEBIAN-CVE-2026-68452, GHSA-wcc3-pw65-4r46, UBUNTU-CVE-2026-68452

## What is CVE-2026-68452?

CVE-2026-68452 is a high-severity memory corruption vulnerability in Linux, published on 13 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

s390/zcrypt: Validate length for CCA AES cipher key requests

cca_cipher2protkey() derives the copy length for the CPRB parameter
block directly from the length field in the key token. Reject the
request early if the token length exceeds the available space in the
parameter block.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2026-68452?


## How do I fix CVE-2026-68452?

Apply the vendor's patch.

## Is CVE-2026-68452 being exploited?

There is no known exploitation of CVE-2026-68452 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68452 and fix it if it is affected.

What it is: CVE-2026-68452 is a high-severity memory corruption vulnerability in Linux, published on 13 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68452 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68452/ (Markdown: https://insights.sbomify.com/CVE-2026-68452/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68452
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68452
- OSV: https://osv.dev/vulnerability/CVE-2026-68452

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68452/
Summaries are generated and may contain mistakes; the official description above is the record.