crypto: mxs-dcp - Ensure payload is zero when using key slot
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:
crypto: mxs-dcp - Ensure payload is zero when using key slot
We could leak stack memory through the payload field when running AES with a key from one of the hardware's key slots. Fix this by ensuring the payload field is set to 0 in such cases.
This does not affect the common use case when the key is supplied from main memory via the descriptor payload.
From the CVE record · Linux
The Linux kernel's mxs-dcp crypto driver can leak stack memory through the payload field when AES uses a key from a hardware key slot. The common case where the key comes from main memory is unaffected; the input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels that use mxs-dcp for AES with hardware key slots should check their systems; affected versions are not specified.