# CVE-2026-93159: crypto: atmel-sha204a - fix heap info leak on I2C transfer failure

> A local attacker can read uninitialized kernel memory via the atmel-sha204a crypto driver when I2C transfers fail, potentially exposing sensitive data.

- **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-102479, BELL-CVE-2026-93159, DEBIAN-CVE-2026-93159, GHSA-4wj4-h74m-5rjv, UBUNTU-CVE-2026-93159

## What is CVE-2026-93159?

CVE-2026-93159 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-sha204a - fix heap info leak on I2C transfer failure

The nonblocking RNG path allocates a work_data structure to track the
state of an in-flight asynchronous I2C request. This pointer is stored
in rng->priv and later consumed by the read path once the transaction
completes.

If the underlying I2C transfer fails, the completion callback is invoked
with a non-zero status. In this case, the allocated work_data is not
usable for producing RNG output and must not remain associated with the
hwrng state.

Previously, the failure path only logged a warning but left the pointer
state uncleared, which can result in subsequent read attempts observing
stale state and interpreting it as valid completion data.

Fix this by freeing the pending work_data. The I2C transaction reports
an error. This ensures that failed requests do not leave residual state
behind that could be interpreted as valid RNG data on later reads.
Clearing rng->priv is done at the subsequent call to nonblocking read.

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


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

Apply the vendor's patch.

## Is CVE-2026-93159 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93159 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-93159 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-93159/ (Markdown: https://insights.sbomify.com/CVE-2026-93159/index.md)
```

## Sources

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

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