CVE-2026-97592

s390/crypto: Fix missing scrub of temp buffers with AES ctr and gcm algorithm

N/A
Published: September 25, 2026 at 10:22 AM UTC
Updated: October 19, 2026 at 10:17 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/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.

Affected

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

5.10.2105.15.1496.1.766.6.156.7.36.8a7f580cdb42ec3d53bbb7c4e4335a98423703285cd51e26a3b89706beec64f2d8296cfb1c34e0c79d07f951903fa9922c375b8ab1ce81b18a0034e3bd68ac38895e84446848b7647ab9458d54cacba3edbc9a791a70ea47be9f2acf251700fe254a2ab23e78f1a43e72daf77705ad5b9946de66fc708b874
Vendor states this is fixed in 11eca05d2062032e1f07d56be58ed0b99f4b1d63 (fixed)
Vendor states this is fixed in 538f00558db9a66aeff20c36f43692c178a0e0eb (fixed)
Vendor states this is fixed in 6ab772d675a885c3119bf0e79ea9e84756d7657a (fixed)
Vendor states this is fixed in 8b7c3b6914f19caf648d05726a86af6326d3c2c6 (fixed)
Vendor states this is fixed in 8b90a47c4fba27bb4f2f086611742493629e9696 (fixed)
Vendor states this is fixed in 991c875310254a13b3a637bb279379c8c66e842d (fixed)
Vendor states this is fixed in a83488cecb35f924b7541306ed84893bb9906196 (fixed)
Vendor states this is fixed in e17b85eb8cee90a1200fa5e7806db7ffa08a0608 (fixed)
Vendor states this is fixed in 5.10.271 (unaffected)
Vendor states this is fixed in 5.15.222 (unaffected)
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc3 (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