crypto: atmel-ecc - reject hardware ECDH without a public key
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 11105693fa05f499532b330da65c78ff93ed4440 · < e64d6f1aae8c837cb3f0446bf44108226d7370f4| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
crypto: atmel-ecc - reject hardware ECDH without a public key
The hardware ECDH path in atmel_ecdh_compute_shared_secret() uses the private key stored in the device. However, the public key is cached only after atmel_ecdh_set_secret() successfully generated that private key for the current tfm.
atmel_ecdh_generate_public_key() already rejects requests when no public key is cached. Add the same check to atmel_ecdh_compute_shared_secret() to prevent the device from using a private key that was not generated for the current tfm.
From the CVE record · Linux
The Linux kernel’s atmel-ecc hardware ECDH path can use a private key stored in the device even when no public key is cached for the current cryptographic context. A shared-secret request in that state can therefore use a private key not generated for that context. The input does not specify an attack route, authentication requirement, or user interaction.
Engineers running Linux kernels with the atmel-ecc driver should check whether their kernel includes the fix; affected versions are not specified.