CVE-2026-64311

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 17, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

crypto: loongson - Remove broken and unused loongson-rng - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/af3d1bb9a09daf928fc3f173689fb7904d6a6d4f
generic

crypto: loongson - Remove broken and unused loongson-rng - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/43de8b9f01b7dd2f6ca5360c6bf2f203c02288dc
generic

crypto: loongson - Remove broken and unused loongson-rng - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/037ec8353711c79353b12d5634e0c9ff363a9efa

Vendor Advisories for CVE-2026-64311(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1

Data Freshness Timeline

(refreshed 21× in last 7d / 110× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 138 total refreshes for this CVE.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:11 UTCEG score recompute
  3. 2026-08-30 00:11 UTCGHSA enrichment
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-28 03:28 UTCGHSA enrichment
  6. 2026-08-27 15:07 UTCEG score recompute
  7. 2026-08-27 15:07 UTCGHSA enrichment
  8. 2026-08-27 02:48 UTCEG score recompute
  9. 2026-08-27 02:48 UTCGHSA enrichment
  10. 2026-08-26 14:47 UTCEPSS rescore
  11. 2026-08-26 14:29 UTCGHSA enrichment
  12. 2026-08-26 02:11 UTCGHSA enrichment
  13. 2026-08-25 13:53 UTCEG score recompute
  14. 2026-08-25 13:53 UTCGHSA enrichment
  15. 2026-08-25 13:49 UTCEPSS rescore
  16. 2026-08-25 01:35 UTCEG score recompute
  17. 2026-08-25 01:35 UTCGHSA enrichment
  18. 2026-08-24 13:18 UTCEG score recompute
  19. 2026-08-24 13:18 UTCGHSA enrichment
  20. 2026-08-24 01:00 UTCGHSA enrichment
  21. 2026-08-23 12:42 UTCGHSA enrichment
  22. 2026-08-23 00:25 UTCEG score recompute
  23. 2026-08-23 00:24 UTCGHSA enrichment
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-22 12:05 UTCEG score recompute
Show 75 more
  1. 2026-08-22 12:05 UTCGHSA enrichment
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-21 23:47 UTCGHSA enrichment
  4. 2026-08-21 11:29 UTCGHSA enrichment
  5. 2026-08-20 23:03 UTCEG score recompute
  6. 2026-08-20 23:03 UTCGHSA enrichment
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 10:44 UTCGHSA enrichment
  9. 2026-08-19 22:26 UTCEG score recompute
  10. 2026-08-19 22:26 UTCGHSA enrichment
  11. 2026-08-19 17:04 UTCEPSS rescore
  12. 2026-08-19 10:04 UTCGHSA enrichment
  13. 2026-08-18 21:46 UTCEG score recompute
  14. 2026-08-18 21:46 UTCGHSA enrichment
  15. 2026-08-18 13:48 UTCEPSS rescore
  16. 2026-08-18 08:50 UTCGHSA enrichment
  17. 2026-08-17 20:19 UTCEG score recompute
  18. 2026-08-17 20:19 UTCGHSA enrichment
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 05:20 UTCEG score recompute
  21. 2026-08-17 05:20 UTCGHSA enrichment
  22. 2026-08-16 18:35 UTCEG score recompute
  23. 2026-08-16 18:35 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 06:16 UTCGHSA enrichment
  26. 2026-08-15 17:59 UTCGHSA enrichment
  27. 2026-08-15 05:41 UTCEG score recompute
  28. 2026-08-15 05:41 UTCGHSA enrichment
  29. 2026-08-15 01:30 UTCEPSS rescore
  30. 2026-08-14 17:23 UTCGHSA enrichment
  31. 2026-08-14 05:01 UTCEG score recompute
  32. 2026-08-14 05:01 UTCGHSA enrichment
  33. 2026-08-13 22:00 UTCEPSS rescore
  34. 2026-08-13 16:43 UTCGHSA enrichment
  35. 2026-08-13 04:02 UTCGHSA enrichment
  36. 2026-08-12 15:44 UTCEG score recompute
  37. 2026-08-12 15:44 UTCGHSA enrichment
  38. 2026-08-12 13:51 UTCEPSS rescore
  39. 2026-08-12 03:27 UTCGHSA enrichment
  40. 2026-08-11 15:09 UTCEG score recompute
  41. 2026-08-11 15:09 UTCGHSA enrichment
  42. 2026-08-11 04:31 UTCEG score recompute
  43. 2026-08-11 04:31 UTCGHSA enrichment
  44. 2026-08-11 00:00 UTCEPSS rescore
  45. 2026-08-10 16:13 UTCGHSA enrichment
  46. 2026-08-10 03:55 UTCGHSA enrichment
  47. 2026-08-09 15:37 UTCEG score recompute
  48. 2026-08-09 15:37 UTCGHSA enrichment
  49. 2026-08-09 13:47 UTCEPSS rescore
  50. 2026-08-09 03:20 UTCEG score recompute
  51. 2026-08-09 03:20 UTCGHSA enrichment
  52. 2026-08-08 16:37 UTCEPSS rescore
  53. 2026-08-08 15:02 UTCGHSA enrichment
  54. 2026-08-08 02:44 UTCGHSA enrichment
  55. 2026-08-07 14:27 UTCGHSA enrichment
  56. 2026-08-07 02:08 UTCGHSA enrichment
  57. 2026-08-06 13:50 UTCEG score recompute
  58. 2026-08-06 13:50 UTCGHSA enrichment
  59. 2026-08-06 13:47 UTCEPSS rescore
  60. 2026-08-06 01:32 UTCEG score recompute
  61. 2026-08-06 01:32 UTCGHSA enrichment
  62. 2026-08-05 19:17 UTCEPSS rescore
  63. 2026-08-05 19:17 UTCEPSS rescore
  64. 2026-08-05 13:14 UTCEG score recompute
  65. 2026-08-05 13:14 UTCGHSA enrichment
  66. 2026-08-05 00:56 UTCEG score recompute
  67. 2026-08-05 00:56 UTCGHSA enrichment
  68. 2026-08-04 15:10 UTCEPSS rescore
  69. 2026-08-04 12:39 UTCEG score recompute
  70. 2026-08-04 12:39 UTCGHSA enrichment
  71. 2026-08-04 10:39 UTCEPSS rescore
  72. 2026-08-03 23:14 UTCGHSA enrichment
  73. 2026-08-03 10:56 UTCEG score recompute
  74. 2026-08-03 10:56 UTCGHSA enrichment
  75. 2026-08-03 10:36 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-64311?
CVE-2026-64311 is a high vulnerability published on July 25, 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 waitforcompletion_interruptible().…
When was CVE-2026-64311 disclosed?
CVE-2026-64311 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64311 actively exploited?
CVE-2026-64311 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.8% of all scored CVEs.
What is the CVSS score of CVE-2026-64311?
CVE-2026-64311 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64311?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64311, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64311

Explore →

Is Your Infrastructure Affected by CVE-2026-64311?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.