CVE-2026-80708

s390/zcrypt: Fix missing mem scrub at clear key import in cca_clr2cipherkey()

N/A
Published: August 28, 2026 at 06:53 AM UTC
Updated: August 28, 2026 at 08:32 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.4 ≤ v < 5.10.2655.4 ≤ v < 5.15.2165.4 ≤ v < 6.1.1835.4 ≤ v < 6.12.1045.4 ≤ v < 6.18.445.4 ≤ v < 6.6.1525.4 ≤ v < 7.1.85.4 ≤ v < 7.24bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd5.4
Vendor states this is fixed in 01476391aecef36a3b789ee844357b22fbc90665 (fixed)
Vendor states this is fixed in 4e26d0d72bfdec311f12acfa0c6b7fbeb6a343d3 (fixed)
Vendor states this is fixed in 7dd6e556dbfc91d3d511cfd1015d2dad42608010 (fixed)
Vendor states this is fixed in 8e1c0def77b7450be0ed607ed0d7bae629d30020 (fixed)
Vendor states this is fixed in b453003ae6a869f5bdf025b5519cbb38295ae4f1 (fixed)
Vendor states this is fixed in be7ae07fb745d1cf575b03a178a055b0a2859364 (fixed)
Vendor states this is fixed in ebfbb9ac7adbb1e3556100b54a27e8a9b102feac (fixed)
Vendor states this is fixed in fbb0410986e8ad214121e51a4a28c3d0a10b7644 (fixed)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 5.4 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.104 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.152 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card