CVE-2026-31746: Linux kernel · s390/zcrypt: Fix memory leak with CCA cards used as accelerator
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c8d46f17c2fc7d25c18e60c008928aecab26184d : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in c8d46f17c2fc7d25c18e60c008928aecab26184d, ace37bfec3822033e59fff390f2ff99fc96ebe4f, 1650268579e1113b30402dbcca4dba6589a0fccf +1
Exploitation evidence
Disclosed: evidence found.
CVE published 1 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to c8d46f17c2fc7d25c18e60c008928aecab26184d, ace37bfec3822033e59fff390f2ff99fc96ebe4f, 1650268579e1113b30402dbcca4dba6589a0fccf or 586222c37d4027dbf60a604fbe820184fee7c1c9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: s390/zcrypt: Fix memory leak with CCA cards used as accelerator Tests showed that there is a memory leak if CCA cards are used as accelerator for clear key RSA requests (ME and CRT). With the last rework for the memory allocation the AP messages are allocated by ap_init_apmsg() but for some reason on two places (ME and CRT) the older allocation was still in place. So the first allocation simple was never freed.
References
- git.kernel.org/stable/c/1650268579e1113b30402dbcca4dba6589a0fccf (opens in a new tab)
- git.kernel.org/stable/c/586222c37d4027dbf60a604fbe820184fee7c1c9 (opens in a new tab)
- git.kernel.org/stable/c/ace37bfec3822033e59fff390f2ff99fc96ebe4f (opens in a new tab)
- git.kernel.org/stable/c/c8d46f17c2fc7d25c18e60c008928aecab26184d (opens in a new tab)