CVE-2026-80708 — s390/zcrypt: Fix missing mem scrub at clear key import in cca_clr2cipherkey()
In the Linux kernel, the following vulnerability has been resolved: s390/zcrypt: Fix missing mem scrub at clear key import in cca_clr2cipherkey() The helper function _ip_cprb_helper() uses internal buffer memory for building and processing CPRBs. After use this buffer was never scrubbed which could lead to leaving for example clear key material in memory which could be exposed via tricky reuse of this same memory. Extend the _ip_cprb_helper() function with another parameter 'scrub' used to steer scrubbing of this buffer. So now the caller has the opportunity to decide if scrubbing is needed or not. Extend the clear key to secure key token import process in function cca_clr2cipherkey() to tell the helper function from above to scrub the cprb buffer when the clear key value is part of the request data. Add explicit scrubbing on return from function cca_clr2cipherkey() for the random EXOR buffer and the cprb buffer. Overall this cleans the internal used buffer in case of clear key import to prevent sensitive data to get exposed.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and < 8e1c0def77b7450be0ed607ed0d7bae629d30020≥ 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and < be7ae07fb745d1cf575b03a178a055b0a2859364≥ 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and < 4e26d0d72bfdec311f12acfa0c6b7fbeb6a343d3≥ 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and < 7dd6e556dbfc91d3d511cfd1015d2dad42608010≥ 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and < b453003ae6a869f5bdf025b5519cbb38295ae4f1≥ 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and < fbb0410986e8ad214121e51a4a28c3d0a10b7644≥ 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and < ebfbb9ac7adbb1e3556100b54a27e8a9b102feac≥ 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and < 01476391aecef36a3b789ee844357b22fbc90665 and 1 moreversion 5.4 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 26, 2026 · 11 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/8e1c0def77b7450be0ed607ed0d7bae629d30020
- git.kernel.org/stable/c/b453003ae6a869f5bdf025b5519cbb38295ae4f1
- git.kernel.org/stable/c/ebfbb9ac7adbb1e3556100b54a27e8a9b102feac
- git.kernel.org/stable/c/4e26d0d72bfdec311f12acfa0c6b7fbeb6a343d3
- git.kernel.org/stable/c/be7ae07fb745d1cf575b03a178a055b0a2859364
- git.kernel.org/stable/c/fbb0410986e8ad214121e51a4a28c3d0a10b7644
- git.kernel.org/stable/c/01476391aecef36a3b789ee844357b22fbc90665
- git.kernel.org/stable/c/7dd6e556dbfc91d3d511cfd1015d2dad42608010
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 23h
- Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 23h
- Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 23h
- Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 23h
- Unknown CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 23h
- Unknown CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 23h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-80708 is "s390/zcrypt: Fix missing mem scrub at clear key import in cca_clr2cipherkey()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.