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

> The Linux kernel Atmel ECC driver failed to validate public key presence, potentially allowing incorrect cryptographic operations using stale private keys.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102192, BELL-CVE-2026-93160, DEBIAN-CVE-2026-93160, GHSA-qjm8-c6rq-8r66, UBUNTU-CVE-2026-93160

## What is CVE-2026-93160?

CVE-2026-93160 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-93160?


## How do I fix CVE-2026-93160?

Apply the vendor's patch.

## Is CVE-2026-93160 being exploited?

There is no known exploitation of CVE-2026-93160 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93160 and fix it if it is affected.

What it is: CVE-2026-93160 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93160 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93160/ (Markdown: https://insights.sbomify.com/CVE-2026-93160/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93160
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93160
- OSV: https://osv.dev/vulnerability/CVE-2026-93160

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93160/
Summaries are generated and may contain mistakes; the official description above is the record.