CVE-2026-97592: Linux kernel · s390/crypto: Fix missing scrub of temp buffers with AES ctr and gcm algorithm
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e17b85eb8cee90a1200fa5e7806db7ffa08a0608 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e17b85eb8cee90a1200fa5e7806db7ffa08a0608, a83488cecb35f924b7541306ed84893bb9906196, 991c875310254a13b3a637bb279379c8c66e842d +10
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 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 to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A patch is available and has been applied in the fixed Linux kernel versions listed. Users and administrators should upgrade to these fixed versions to remediate the vulnerability. Since this is a kernel-level fix, applying the official kernel updates from the Linux vendor is the recommended mitigation. No additional action is required beyond applying these updates.
Description
A vulnerability in the Linux kernel's s390 crypto implementation involving AES CTR and GCM algorithms was fixed. Temporary buffers used during encryption were not properly scrubbed, potentially exposing sensitive data. The flaw affected multiple kernel versions prior to their respective fixes. The issue was resolved by explicitly scrubbing these buffers at the end of their use to prevent data leakage.
References
- git.kernel.org/stable/c/538f00558db9a66aeff20c36f43692c178a0e0eb (opens in a new tab)
- git.kernel.org/stable/c/6ab772d675a885c3119bf0e79ea9e84756d7657a (opens in a new tab)
- git.kernel.org/stable/c/e17b85eb8cee90a1200fa5e7806db7ffa08a0608 (opens in a new tab)
- git.kernel.org/stable/c/991c875310254a13b3a637bb279379c8c66e842d (opens in a new tab)
- git.kernel.org/stable/c/11eca05d2062032e1f07d56be58ed0b99f4b1d63 (opens in a new tab)
- git.kernel.org/stable/c/8b90a47c4fba27bb4f2f086611742493629e9696 (opens in a new tab)
- git.kernel.org/stable/c/a83488cecb35f924b7541306ed84893bb9906196 (opens in a new tab)
- git.kernel.org/stable/c/8b7c3b6914f19caf648d05726a86af6326d3c2c6 (opens in a new tab)