Answer in brief
CVE-2026-64311 records a High severity (CVSS 7.8) vulnerability in crypto: loongson - Remove broken and unused loongson-rng. 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.
CVSS is 7.8. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=766b2d724c8df071031412eea902b566a0049c31 <037ec8353711c79353b12d5634e0c9ff363a9efa || >=766b2d724c8df071031412eea902b566a0049c31 <43de8b9f01b7dd2f6ca5360c6bf2f203c02288dc || >=766b2d724c8df071031412eea902b566a0049c31 <af3d1bb9a09daf928fc3f173689fb7904d6a6d4f | 037ec8353711c79353b12d5634e0c9ff363a9efa, 43de8b9f01b7dd2f6ca5360c6bf2f203c02288dc, af3d1bb9a09daf928fc3f173689fb7904d6a6d4f |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: crypto: loongson - Remove broken and unused loongson-rng The loongson-rng rng_alg has several vulnerabilities, including not providing forward security, and a use-after-free bug due to the use of wait_for_completion_interruptible(). Meanwhile, the rng_alg framework doesn't really have any purpose in the first place other than to access the software algorithms crypto/drbg.c and crypto/jitterentropy.c. Hardware-specific rng_algs have no in-kernel user, and unlike hwrng there's no feed into the actual Linux RNG. As such, there's really no point to this code. There are of course other rng_alg drivers that are similarly unused, but they're similarly in the process of being phased out, e.g. https://lore.kernel.org/r/[email protected] and https://lore.kernel.org/r/[email protected] Given that, there's no point in fixing forward these vulnerabilities, and it makes much more sense to simply roll back the addition of this driver. If this platform provides TRNG (not PRNG) functionality, it could make sense to add a hwrng driver, but it would be quite different.
Quoted source text, attributed separately from HOL analysis.