CVE-2026-93160: crypto: atmel-ecc - reject hardware ECDH without a public key

Published Sep 17, 2026
·
Updated

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 atmelecdhcomputesharedsecret() uses the private key stored in the device. However, the public key is cached only after atmelecdhsetsecret() successfully generated that private key for the current tfm.

atmelecdhgeneratepublickey() already rejects requests when no public key is cached. Add the same check to atmelecdhcomputesharedsecret() to prevent the device from using a private key that was not generated for the current tfm.

Affected Software

1 affected component
Linux Linux kernel

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Apply the Linux kernel fix so the hardware ECDH path in atmel_ecdh_compute_shared_secret() rejects hardware ECDH when no public key is available for the current tfm (as atmel_ecdh_generate_public_key() already does), to prevent use of a cached private key that was not generated.

Event History

Sep 17, 2026
CVE Published
via MITRE·04:11 PM
Data Sourced
via MITRE·04:11 PM
Description

Frequently Asked Questions

1

Which systems are exposed to this issue?

Systems using the Linux kernel's atmel-ecc hardware ECDH path are exposed when a shared-secret computation can be requested for a transform instance that has not successfully generated and cached its own public key.

2

What condition is required for exploitation?

A hardware ECDH shared-secret operation must be invoked without a public key cached for the current transform. In that state, the device may use a private key that was not generated for that transform.

3

How can I determine whether the vulnerable condition is present?

The affected condition exists if atmel_ecdh_compute_shared_secret() can proceed when no public key is cached for the current transform. The resolved behavior rejects that request, matching the existing validation in atmel_ecdh_generate_public_key().

4

What can be done before applying the fix?

Avoid invoking hardware ECDH shared-secret operations unless atmel_ecdh_set_secret() has successfully generated the private key and established a cached public key for the current transform.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203