s390/crypto: Fix missing scrub of temp buffers with AES ctr and gcm algorithm
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d07f951903fa9922c375b8ab1ce81b18a0034e3b · < 8b90a47c4fba27bb4f2f086611742493629e9696| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s s390 AES-CTR and AES-GCM code did not scrub some temporary buffers and an error-path parameter block, potentially exposing sensitive data. The input does not specify how an attacker could access that data or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel on s390 should check their installations; affected versions are not specified.