CVE-2026-97592s390/crypto: Fix missing scrub of temp buffers with AES ctr and gcm algorithm
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: s390/crypto: Fix missing scrub of temp buffers with AES ctr and gcm algorithm In function ctr_aes_crypt() there is a buffer used to process remaining bytes < AES_BLOCK_SIZE. This buffer was not scrubbed and thus could lead to expose of unwanted data. When the buffer is used explicitly scrub it at the end of the code block to avoid exposure of maybe sensitive data. In a similar way the function gcm_aes_crypt() hat an error path where the CPACF param block was not scrubbed. Instead of return early now these error paths go to end of function where explicit scrubbing is done. Similar with the buffers which are part of the gcm_sg_walk structs from the variables gw_in and gw_out.
Timeline
ID reserved
By Linux
- 1 day later
· 1 day later
Published
- 24 days later
· 24 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected cd51e26a3b89706beec64f2d8296cfb1c34e0c79 – < 538f00558db9a66aeff20c36f43692c178a0e0eb
- affected a7f580cdb42ec3d53bbb7c4e4335a98423703285 – < 6ab772d675a885c3119bf0e79ea9e84756d7657a
- affected dbc9a791a70ea47be9f2acf251700fe254a2ab23 – < e17b85eb8cee90a1200fa5e7806db7ffa08a0608
- affected d68ac38895e84446848b7647ab9458d54cacba3e – < 991c875310254a13b3a637bb279379c8c66e842d
- affected d07f951903fa9922c375b8ab1ce81b18a0034e3b – < 11eca05d2062032e1f07d56be58ed0b99f4b1d63
- affected d07f951903fa9922c375b8ab1ce81b18a0034e3b – < 8b90a47c4fba27bb4f2f086611742493629e9696
- affected d07f951903fa9922c375b8ab1ce81b18a0034e3b – < a83488cecb35f924b7541306ed84893bb9906196
- affected d07f951903fa9922c375b8ab1ce81b18a0034e3b – < 8b7c3b6914f19caf648d05726a86af6326d3c2c6
- affected e78f1a43e72daf77705ad5b9946de66fc708b874
- affected 5.10.210 – < 5.10.271
- affected 5.15.149 – < 5.15.222
- affected 6.1.76 – < 6.1.189
- affected 6.6.15 – < 6.6.158
- affected 6.7.3 – < 6.8
- affected 6.8
- unaffected < 6.8
- unaffected 5.10.271 – ≤ 5.10.*
- unaffected 5.15.222 – ≤ 5.15.*
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2.7 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/538f00558db9a66aeff20c36f43692c178a0e0eb (opens in a new tab)
- https://git.kernel.org/stable/c/6ab772d675a885c3119bf0e79ea9e84756d7657a (opens in a new tab)
- https://git.kernel.org/stable/c/e17b85eb8cee90a1200fa5e7806db7ffa08a0608 (opens in a new tab)
- https://git.kernel.org/stable/c/991c875310254a13b3a637bb279379c8c66e842d (opens in a new tab)
- https://git.kernel.org/stable/c/11eca05d2062032e1f07d56be58ed0b99f4b1d63 (opens in a new tab)
- https://git.kernel.org/stable/c/8b90a47c4fba27bb4f2f086611742493629e9696 (opens in a new tab)
- https://git.kernel.org/stable/c/a83488cecb35f924b7541306ed84893bb9906196 (opens in a new tab)
- https://git.kernel.org/stable/c/8b7c3b6914f19caf648d05726a86af6326d3c2c6 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86900 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97592)Record last updated .