s390/zcrypt: Close speculative mem read possibility
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ cfd68b33094e1a92249850ff3c3c92ae9112a541 · < e935cd525af4c6ed2e2c6404aa27ca19c7f39ddb| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/zcrypt: Close speculative mem read possibility
The domain value is extracted from a given CCA or EP11 ioctl struct when a CPRB is about to be sent. Thus this is a user controlled value. Under some special conditions (custom device node used, administrative load) this value is used as an array index after bounds checking, but without speculation barrier.
Add the missing array_index_nospec() call to prevent speculative execution where this domain value is used.
From the CVE record · Linux
The Linux kernel's s390/zcrypt code uses a user-controlled domain value from a CCA or EP11 ioctl as an array index without a speculation barrier. Under special conditions involving a custom device node and administrative load, a local user could trigger a speculative memory read. The input does not specify authentication requirements.
Engineers running Linux kernels with s390/zcrypt should check their deployments; affected versions were not provided.