Answer in brief
CVE-2026-80871 records a Unknown severity vulnerability in crypto: xilinx-trng - Remove crypto_rng interface. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=8979744aca8096ee5072798dfc1181606919b35d <83f29da85dc9d9a32fe62cd1055e8e6705e6bf80 || >=8979744aca8096ee5072798dfc1181606919b35d <9634db561e1594c151923f4950c012161c545c93 || >=8979744aca8096ee5072798dfc1181606919b35d <32b4d29280ed2a991dc196d5845b892acedc63b8 | 83f29da85dc9d9a32fe62cd1055e8e6705e6bf80, 9634db561e1594c151923f4950c012161c545c93, 32b4d29280ed2a991dc196d5845b892acedc63b8 |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.