CVE-2026-74670

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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:

ipvs: stop estimator after disabled calc phase

IPVS estimator kthread 0 starts with zeroed chain and tick limits until its initial calculation phase completes. If network namespace teardown clears ipvs->enable during that phase, ip_vs_est_calc_phase() can return without installing positive limits.

The kthread can then continue into its main loop and drain est_temp_list with zero chain_max, tick_max and est_max_count values. Each enqueue consumes one available tick row, but est_count never reaches the zero est_max_count value. After all rows are consumed, the row lookup returns IPVS_EST_NTICKS and ip_vs_enqueue_estimator() writes past the ticks and tick_len arrays.

Exit kthread 0 after the calculation phase if the kthread is stopping or IPVS has been disabled. That keeps temporary estimators from being drained after the limits failed to initialize.

Estimator kthreads can now self-exit before teardown or reload stops kd->task. Keep an extra task reference after creation and release it with kthread_stop_put(), so kd->task remains valid until the stop paths consume that reference.

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 22, 2026

Last Modified

August 25, 2026

Advisory Details (5)

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

ipvs: stop estimator after disabled calc phase - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/558f67f1340f803a346ecd14a69c49653111c5f4
generic

ipvs: stop estimator after disabled calc phase - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2335dedc1922dfa889ca1f9f70370924e8e79a08
generic

ipvs: stop estimator after disabled calc phase - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipvs: stop estimator after disabled calc phase - kernel/git/stable/linux.git - Linux kernel stable tree

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

ipvs: stop estimator after disabled calc phase - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d5122a2b2601145975d387006e517c56896e310e

Vendor Advisories for CVE-2026-74670(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 25× in last 7d / 28× 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-30 04:45 UTCEG score recompute
  2. 2026-08-30 04:45 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 15:37 UTCGHSA enrichment
  5. 2026-08-29 02:28 UTCEG score recompute
  6. 2026-08-29 02:27 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 13:19 UTCGHSA enrichment
  9. 2026-08-28 00:11 UTCEG score recompute
  10. 2026-08-28 00:11 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 11:00 UTCGHSA enrichment
  13. 2026-08-26 21:52 UTCEG score recompute
  14. 2026-08-26 21:52 UTCGHSA enrichment
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-26 08:44 UTCGHSA enrichment
  17. 2026-08-25 19:37 UTCEG score recompute
  18. 2026-08-25 19:37 UTCGHSA enrichment
  19. 2026-08-25 13:49 UTCEPSS rescore
  20. 2026-08-25 06:29 UTCEG score recompute
  21. 2026-08-25 06:29 UTCGHSA enrichment
  22. 2026-08-25 05:56 UTCEG score recompute 7.80
  23. 2026-08-25 05:55 UTCGHSA enrichment
  24. 2026-08-25 05:55 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  25. 2026-08-24 14:18 UTCEPSS rescore
Show 3 more
  1. 2026-08-22 16:24 UTCNVD update
  2. 2026-08-22 15:40 UTCEG score recompute
  3. 2026-08-22 15:35 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74670?
CVE-2026-74670 is a high vulnerability published on August 22, 2026. In the Linux kernel, the following vulnerability has been resolved: ipvs: stop estimator after disabled calc phase IPVS estimator kthread 0 starts with zeroed chain and tick limits until its initial calculation phase completes. If network namespace teardown clears ipvs->enable during that phase,…
When was CVE-2026-74670 disclosed?
CVE-2026-74670 was first published in the National Vulnerability Database on August 22, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74670 actively exploited?
CVE-2026-74670 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 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-74670?
CVE-2026-74670 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74670?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74670, 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-74670

Explore →

Is Your Infrastructure Affected by CVE-2026-74670?

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