# CVE-2026-80871: crypto: xilinx-trng - Remove crypto_rng interface

> A race condition in the Xilinx TRNG kernel driver allows concurrent access issues, potentially leading to incorrect random number generation or system instability.

- **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:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** BELL-CVE-2026-80871, DEBIAN-CVE-2026-80871, GHSA-qx96-qjpp-7jj8, UBUNTU-CVE-2026-80871

## What is CVE-2026-80871?

CVE-2026-80871 is a vulnerability in Linux, published on 4 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: xilinx-trng - Remove crypto_rng interface

Implementing the crypto_rng interface has no purpose, as it isn't used
in practice.  It's being removed from other drivers too.  Just remove
it.  This leaves hwrng, which is actually used.

Tagging with 'Cc stable' due to the bugs that this removes:

  - xtrng_trng_generate() sometimes returned success even when it didn't
    fill in all the bytes.

  - It was possible for xtrng_trng_generate() and
    xtrng_hwrng_trng_read() to run concurrently and interfere with each
    other, as the locking code in xtrng_hwrng_trng_read() was broken.

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


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

Apply the vendor's patch.

## Is CVE-2026-80871 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80871 is a vulnerability in Linux, published on 4 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-80871 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-80871/ (Markdown: https://insights.sbomify.com/CVE-2026-80871/index.md)
```

## Sources

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

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