CVE-2026-74438

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 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: sun4i-ss - Remove insecure and unused rng_alg

Remove sun4i_ss_rng, as it is insecure and unused:

  • It has multiple vulnerabilities. sun4i_ss_prng_seed() is missing
locking and has a buffer overflow. sun4i_ss_prng_generate() fails to fill the entire buffer with cryptographic random bytes, because it rounds the destination length down and also doesn't actually wait for the hardware to be ready before pulling bytes from it.
  • No user of this code is known. It's usable only theoretically via the
"rng" algorithm type of AF_ALG. But userspace actually just uses the actual Linux RNG (/dev/random etc) instead. And rng_algs don't contribute entropy to the actual Linux RNG either. (This may have been confused with hwrng, which does contribute entropy.)

The sun4i_ss_prng_seed() buffer overflow was reported by Tianchu Chen and discovered by Atuin - Automated Vulnerability Discovery Engine

There's no point in fixing all these vulnerabilities individually when this is unused code, so let's just remove it.

CVSS v3
7.8
EG Score
7.8(high)
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
3%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (7)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

crypto: sun4i-ss - Remove insecure and unused rng_alg - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: sun4i-ss - Remove insecure and unused rng_alg - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: sun4i-ss - Remove insecure and unused rng_alg - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: sun4i-ss - Remove insecure and unused rng_alg - kernel/git/stable/linux.git - Linux kernel stable tree

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

crypto: sun4i-ss - Remove insecure and unused rng_alg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c8086d9511189c34dfa3f9e3a03f2bee12f56a5
generic

crypto: sun4i-ss - Remove insecure and unused rng_alg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/306ded31bfa00a69d25823a60d7c797170bfb4f8
generic

crypto: sun4i-ss - Remove insecure and unused rng_alg - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2eafecaba1b46bb9774eaf3556619fd5b6a17c1c

Vendor Advisories for CVE-2026-74438(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 27× 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.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 22:49 UTCGHSA enrichment
  3. 2026-08-20 11:47 UTCGHSA enrichment
  4. 2026-08-20 00:46 UTCEG score recompute
  5. 2026-08-20 00:46 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 13:40 UTCGHSA enrichment
  8. 2026-08-19 02:38 UTCGHSA enrichment
  9. 2026-08-18 15:35 UTCGHSA enrichment
  10. 2026-08-18 04:28 UTCGHSA enrichment
  11. 2026-08-17 17:28 UTCEG score recompute
  12. 2026-08-17 17:28 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 06:25 UTCEG score recompute
  15. 2026-08-17 06:25 UTCGHSA enrichment
  16. 2026-08-17 05:55 UTCEG score recompute▲ 7.80
  17. 2026-08-17 05:55 UTCGHSA enrichment
  18. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  19. 2026-08-17 05:25 UTCEG score recompute
  20. 2026-08-17 05:25 UTCGHSA enrichment
  21. 2026-08-17 05:24 UTCMITRE cvelistV5
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 02:15 UTCEPSS rescore
  25. 2026-08-15 06:23 UTCNVD update
Show 2 more
  1. 2026-08-15 06:13 UTCEG score recompute
  2. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74438?
CVE-2026-74438 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: sun4i-ss - Remove insecure and unused rng_alg Remove sun4issrng, as it is insecure and unused: It has multiple vulnerabilities. sun4issprng_seed() is missing locking and has a buffer overflow. sun4issprng_generate() fails…
When was CVE-2026-74438 disclosed?
CVE-2026-74438 was first published in the National Vulnerability Database on August 15, 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-74438 actively exploited?
CVE-2026-74438 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 96.7% of all scored CVEs.
What is the CVSS score of CVE-2026-74438?
CVE-2026-74438 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74438?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74438, 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

Explore the affected products and dependency analysis for CVE-2026-74438

Explore →

Is Your Infrastructure Affected by CVE-2026-74438?

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

Start Free Scan →Browse All CVEs