Linux kernel speculative bounds bypass in s390 zcrypt domain checks
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/zcrypt: Guard domain index uses against speculative bypass
The previous array_index_nospec() placement only covered the admin permission check, leaving ap_test_config_usage_domain() and ap_test_config_ctrl_domain() in the CCA path exposed to speculative execution.
Move the sanitization to before all permission and config checks in both the CCA and EP11 paths. Hold the sanitized domain value in another variable so that the later use can choose to use either the original value (subject to speculative execution) or the sanitized value (which may in case of AUTOSEL_DOM reflect the wrong value). Before that, check the domain value to be either AUTOSEL_DOM or in range 0...AP_DOMAINS-1 and return with -EINVAL in case this check does not pass.
From the CVE record · Linux
The s390/zcrypt code in the Linux kernel did not sanitize a domain index before all permission and configuration checks in its CCA path, leaving some checks exposed to speculative execution. A domain index outside the allowed range could reach those checks speculatively. The input does not specify attacker access requirements or whether user interaction is needed.
Engineers running Linux kernels with s390/zcrypt should check their versions against the vendor advisory; affected versions are not specified.