s390/zcrypt: Fix buffer over-read in cca_cipher2protkey
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4bc123b18ce6ae6c42c69d0456b5acbd2f7bc8bd · < 36b230835b8a008266aad22168ca52afacc8a58d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/zcrypt: Fix buffer over-read in cca_cipher2protkey
Add validation of both the actual key buffer size and token length fields in all the cca_check_sec*token() functions. Additionally check in cca_gencipherkey() for possible underflow with returned key size.
The CCA token structures contain user-controlled len fields that were used in operations without proper validation against both the actual buffer size and minimum token structure size. An attacker could set this field larger than the actual buffer size, leading to reading beyond buffer boundaries. This may result in a kernel crash or exposure of memory via sending this as part of a request down to the crypto card. Also an attacker could have used a very small len value and thus enforce a buffer under-run which may produce similar effects as a over-read.
So now a key must - key buf length must be at least sizeof the token struct - the key len field inside the token must fit into the range of sizeof key token struct ... key buf length
From the CVE record · Linux
The Linux kernel’s s390/zcrypt CCA token handling does not adequately validate user-controlled length fields against the key buffer size. An attacker who can submit a crafted CCA key token could trigger an out-of-bounds read, potentially crashing the kernel or exposing memory through a request to a crypto card. The input does not specify authentication or other access requirements.
Engineers running Linux kernels that use s390/zcrypt CCA token handling should check their deployments; affected versions are not specified.