s390/crypto: Fix skcipher_walk return code handling in aes_s390
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/crypto: Fix skcipher_walk return code handling in aes_s390
The return codes from skcipher_walk_virt() were not properly checked before entering the processing loops in ecb_aes_crypt() and ctr_aes_crypt(). If skcipher_walk_virt() fails, the walk structure may be in an undefined state, and attempting to process data could lead to incorrect behavior or accessing uninitialized memory.
Add proper return code checking to ensure correct handling of the walk initialization and walk advance and eventually return to the caller with that return code.
From the CVE record · Linux
The Linux kernel’s s390 AES crypto code did not properly check whether skcipher_walk_virt() failed before processing data. If it fails, processing may access uninitialized memory or behave incorrectly. The input does not establish whether an attacker can trigger this or specify network, authentication, or user-interaction conditions.
Engineers running Linux kernels with s390 AES crypto should check their deployments; affected versions are not specified.