CVE-2026-64311
Last modified
CVE-2026-64311 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
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/20260529193648.18172-1-ebiggers@kernel.org and https://lore.kernel.org/r/20260529220430.34135-1-ebiggers@kernel.org 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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 766b2d724c8df071031412eea902b566a0049c31, < 037ec8353711c79353b12d5634e0c9ff363a9efa; >= 766b2d724c8df071031412eea902b566a0049c31, < 43de8b9f01b7dd2f6ca5360c6bf2f203c02288dc; >= 766b2d724c8df071031412eea902b566a0049c31, < af3d1bb9a09daf928fc3f173689fb7904d6a6d4f |
| Linux | Linux | 6.18 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-64311?
How severe is CVE-2026-64311?
How do I fix CVE-2026-64311?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64305In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64306In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64307In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64308In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64309In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64310In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64312In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-64313In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64314In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64315In the Linux kernel, the following vulnerability has been re…7
- CVE-2026-64316In the Linux kernel, the following vulnerability has been re…
- CVE-2026-64317In the Linux kernel, the following vulnerability has been re…7.1
Are you affected by CVE-2026-64311?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
