Linux Kernel up to 7.1.7 zcrypt cca_clr2cipherkey information disclosure

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.2 | $0-$5k | 0.00+ |
Summary
A vulnerability was found in Linux Kernel up to 7.1.7. It has been rated as problematic. This vulnerability affects the function cca_clr2cipherkey of the component zcrypt. The manipulation leads to information disclosure.
This vulnerability is documented as CVE-2026-80708. The attack needs to be performed locally. There is not any exploit available.
Details
A vulnerability, which was classified as problematic, has been found in Linux Kernel up to 7.1.7. This issue affects the function cca_clr2cipherkey of the component zcrypt. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
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.
The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-80708 since 08/26/2026. The exploitation is known to be easy. An attack has to be approached locally. The exploitation needs additional levels of successful authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 5.10.265, 5.15.216, 6.1.183, 6.6.152, 6.12.104, 6.18.44 or 7.1.8 eliminates this vulnerability. Applying the patch 8e1c0def77b7450be0ed607ed0d7bae629d30020/be7ae07fb745d1cf575b03a178a055b0a2859364/4e26d0d72bfdec311f12acfa0c6b7fbeb6a343d3/7dd6e556dbfc91d3d511cfd1015d2dad42608010/b453003ae6a869f5bdf025b5519cbb38295ae4f1/fbb0410986e8ad214121e51a4a28c3d0a10b7644/ebfbb9ac7adbb1e3556100b54a27e8a9b102feac/01476391aecef36a3b789ee844357b22fbc90665 is able to eliminate this problem.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 5.10.264
- 5.15.215
- 6.1.182
- 6.6.151
- 6.12.103
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 7.1.0
- 7.1.1
- 7.1.2
- 7.1.3
- 7.1.4
- 7.1.5
- 7.1.6
- 7.1.7
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.3VulDB Meta Temp Score: 2.2
VulDB Base Score: 2.3
VulDB Temp Score: 2.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.10.265/5.15.216/6.1.183/6.6.152/6.12.104/6.18.44/7.1.8
Patch: 8e1c0def77b7450be0ed607ed0d7bae629d30020/be7ae07fb745d1cf575b03a178a055b0a2859364/4e26d0d72bfdec311f12acfa0c6b7fbeb6a343d3/7dd6e556dbfc91d3d511cfd1015d2dad42608010/b453003ae6a869f5bdf025b5519cbb38295ae4f1/fbb0410986e8ad214121e51a4a28c3d0a10b7644/ebfbb9ac7adbb1e3556100b54a27e8a9b102feac/01476391aecef36a3b789ee844357b22fbc90665
Timeline
08/26/2026 CVE reserved08/28/2026 Advisory disclosed
08/28/2026 VulDB entry created
08/28/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-80708 (🔒)
GCVE (CVE): GCVE-0-2026-80708
GCVE (VulDB): GCVE-100-396641
Entry
Created: 08/28/2026 11:00Changes: 08/28/2026 11:00 (59)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.