CVE-2026-80668

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.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: 9.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:

netfilter: nf_conntrack_expect: use conntrack GC to reap expectations

This patch replaces the timer API by GC worker approach for expectations, as it already happened in many other subsystems.

Use the existing conntrack GC worker to iterate over the local list of expectations in the master conntrack to reap expired expectations. Check IPS_HELPER_BIT to run GC for expectations, set it on for nft_ct expectation which nevers sets it. Hold the expectation spinlock while iterating over the master conntrack expectation list to synchronize with nf_ct_remove_expectations(). This also performs runtime packet path garbage collection through the expectation insertion and lookup functions while walking over one of the chains of the global expectation hashtables. Unconfirmed conntrack entries are skipped since ct->ext can be reallocated and dying are skipped since those will be gone soon. Set on IPS_HELPER_BIT if the helper ct extension is added, then the new GC worker does not need to bump the ct refcount to check if the ct->ext helper is available.

This removes the extra bump on the refcount for expectation timers, this allows to remove several nf_ct_expect_put() calls after the unlink, after this update only refcount remains at 1 while on the expectation hashes.

This patch implicitly addresses a race with the existing timer API allowing an expectation to access a stale exp->master pointer which has been already released when expectation removal loses races with an expiring timer, ie. timer_del() reporting false.

Add a new NF_CT_EXPECT_DEAD flag to reap this expectation via GC. This is needed by nf_conntrack_unexpect_related() which is called in error paths to invalidate newly created expectations that has been added into the hashes. These expectactions cannot be inmediately released as GC or nf_ct_remove_expectations() could race to make it. On expectation insert, the runtime GC reaps stale expectations before checking the expectation limit set by policy.

Set current timestamp in nf_ct_expect_alloc(), then add the expectation policy timeout (or custom timeout specified added on top of this) to specify the expectation lifetime.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 29, 2026

Advisory Details (2)

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

netfilter: nf_conntrack_expect: use conntrack GC to reap expectations - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nf_conntrack_expect: use conntrack GC to reap expectations - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ec786f4230c2a9b2eaf97a2d45368933b49d2b2

Vendor Advisories for CVE-2026-80668(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 17× in last 7d / 17× 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:29 UTCEG score recompute
  2. 2026-08-30 04:29 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-30 00:17 UTCGHSA enrichment
  5. 2026-08-29 20:06 UTCGHSA enrichment
  6. 2026-08-29 15:51 UTCGHSA enrichment
  7. 2026-08-29 11:39 UTCEG score recompute
  8. 2026-08-29 11:39 UTCGHSA enrichment
  9. 2026-08-29 07:26 UTCEG score recompute
  10. 2026-08-29 07:26 UTCGHSA enrichment
  11. 2026-08-29 06:36 UTCEG score recompute 9.80
  12. 2026-08-29 06:36 UTCGHSA enrichment
  13. 2026-08-29 06:33 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  14. 2026-08-28 21:42 UTCEPSS rescore
  15. 2026-08-28 08:20 UTCNVD update
  16. 2026-08-28 07:34 UTCEG score recompute
  17. 2026-08-28 07:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80668?
CVE-2026-80668 is a critical vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: netfilter: nfconntrackexpect: use conntrack GC to reap expectations This patch replaces the timer API by GC worker approach for expectations, as it already happened in many other subsystems. Use the existing conntrack GC worker to…
When was CVE-2026-80668 disclosed?
CVE-2026-80668 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80668 actively exploited?
CVE-2026-80668 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 69.2% of all scored CVEs.
What is the CVSS score of CVE-2026-80668?
CVE-2026-80668 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-80668?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80668, 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-80668

Explore →

Is Your Infrastructure Affected by CVE-2026-80668?

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