s390/zcrypt: Pad trailing CCA or EP11 message with zeros
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 |
7.1
|
In the Linux kernel, the following vulnerability has been resolved:
s390/zcrypt: Pad trailing CCA or EP11 message with zeros
The both functions xcrb_msg_to_type6cprb_msgx() and xcrb_msg_to_type6_ep11cprb_msgx() copy the user space message into a kernel buffer based on the message length. But on further processing the message is supposed to be 4 byte length adjusted. Thus up to 3 bytes of uninitialized kernel memory are forwarded to further processing steps and may unwanted expose kernel memory to the crypto card firmware.
This patch contains code to pad the gap between user space copied message and message buffer length sent down to further processing of the CCA or EP11 message to zeros.
From the CVE record · Linux
The s390/zcrypt CCA and EP11 message handlers can forward up to three bytes of uninitialized kernel memory to crypto card firmware. This can occur when a user-space message is copied into a kernel buffer and its length is adjusted to a four-byte boundary.
Engineers running Linux kernels with s390/zcrypt should check their systems; affected versions are not specified.