CVE-2026-80708: s390/zcrypt: Fix missing mem scrub at clear key import in cca_clr2cipherkey()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 01476391aecef36a3b789ee844357b22fbc90665, 4e26d0d72bfdec311f12acfa0c6b7fbeb6a343d3, 7dd6e556dbfc91d3d511cfd1015d2dad42608010; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 01476391aecef36a3b789ee844357b22fbc90665, 4e26d0d72bfdec311f12acfa0c6b7fbeb6a343d3, 7dd6e556dbfc91d3d511cfd1015d2dad42608010; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.4affected
- 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and later · before 8e1c0def77b7450be0ed607ed0d7bae629d30020affected · git
- 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and later · before be7ae07fb745d1cf575b03a178a055b0a2859364affected · git
- 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and later · before 4e26d0d72bfdec311f12acfa0c6b7fbeb6a343d3affected · git
- 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and later · before 7dd6e556dbfc91d3d511cfd1015d2dad42608010affected · git
- 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and later · before b453003ae6a869f5bdf025b5519cbb38295ae4f1affected · git
- 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and later · before fbb0410986e8ad214121e51a4a28c3d0a10b7644affected · git
- 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and later · before ebfbb9ac7adbb1e3556100b54a27e8a9b102feacaffected · git
- 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd and later · before 01476391aecef36a3b789ee844357b22fbc90665affected · git
- before 5.4not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80701Aug 28, 2026 · drm/vmwgfx: enforce cursor size limits for MOB cursors0Monitor
- ← EarlierCVE-2026-80703Aug 28, 2026 · drm/amdkfd: Fix missing authorization check in KFD_IOC_DBG_TRAP_DISABLE0Monitor
- Later →CVE-2026-80711Aug 28, 2026 · power: supply: max17040: handle missing status supplier0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 01476391aecef36a3b789ee844357b22fbc90665 | Vendor (CNA) |
| Linux Linux | 4e26d0d72bfdec311f12acfa0c6b7fbeb6a343d3 | Vendor (CNA) |
| Linux Linux | 7dd6e556dbfc91d3d511cfd1015d2dad42608010 | Vendor (CNA) |
| Linux Linux | 8e1c0def77b7450be0ed607ed0d7bae629d30020 | Vendor (CNA) |
| Linux Linux | b453003ae6a869f5bdf025b5519cbb38295ae4f1 | Vendor (CNA) |
| Linux Linux | be7ae07fb745d1cf575b03a178a055b0a2859364 | Vendor (CNA) |
| Linux Linux | ebfbb9ac7adbb1e3556100b54a27e8a9b102feac | Vendor (CNA) |
| Linux Linux | fbb0410986e8ad214121e51a4a28c3d0a10b7644 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0945 · Aug 31, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/4e26d0d72bfdec311f12acfa0c6b7fbeb6a343d3
- git.kernel.org/stable/c/7dd6e556dbfc91d3d511cfd1015d2dad42608010
- git.kernel.org/stable/c/8e1c0def77b7450be0ed607ed0d7bae629d30020
- git.kernel.org/stable/c/b453003ae6a869f5bdf025b5519cbb38295ae4f1
- git.kernel.org/stable/c/be7ae07fb745d1cf575b03a178a055b0a2859364
- git.kernel.org/stable/c/ebfbb9ac7adbb1e3556100b54a27e8a9b102feac
- git.kernel.org/stable/c/fbb0410986e8ad214121e51a4a28c3d0a10b7644
Vendor advisories and official records. Exploit/PoC links are deliberately left out.