In the Linux kernel, the following vulnerability has been resolved: crypto: loongson - Remove broken and unused loongson-rng The loongson-rng… (CVE-2026-64311)
Source GCVE Database
Not known to be exploited : update affected systems when convenient.
Data as of 10/24/2026, 17:08:26 UTC
No CVSS score from NVD or the CNA
- Exploitation
Not in CISA KEV, no exploitation reported
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
What to do
AI-suggested
The vulnerability has been resolved by removing the loongson-rng driver from the Linux kernel. No further action is required to fix this vulnerability. Systems should update to Linux kernel versions that include this removal to ensure the vulnerability is addressed.
Description
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.
Impact
The vulnerabilities could have allowed exploitation of the loongson-rng driver, potentially compromising randomness generation on affected systems. However, since the driver was broken and unused, the practical impact is limited. The removal of the driver eliminates the attack surface related to these issues.
Summary
The Linux kernel contained a vulnerable loongson-rng driver within its crypto subsystem. This driver had several security issues, including the absence of forward security and a use-after-free vulnerability caused by the use of wait_for_completion_interruptible(). The rng_alg framework that this driver belonged to was largely unused and did not feed into the main Linux RNG, making the driver redundant. Instead of patching the vulnerabilities, the driver was removed entirely from the kernel. The removal addresses the security concerns by eliminating the vulnerable code path. There is no indication of active exploitation or cloud service impact.
References
- nvd.nist.gov/vuln/detail/CVE-2026-64311 (opens in a new tab)
- git.kernel.org/stable/c/037ec8353711c79353b12d5634e0c9ff363a9efa (opens in a new tab)
- git.kernel.org/stable/c/43de8b9f01b7dd2f6ca5360c6bf2f203c02288dc (opens in a new tab)
- git.kernel.org/stable/c/af3d1bb9a09daf928fc3f173689fb7904d6a6d4f (opens in a new tab)