CVE-2026-64530

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, 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:

net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle

tcf_classify() can return TC_ACT_CONSUMED while the skb is held by the defragmentation engine (e.g. act_ct on out-of-order fragments). When that happens the skb is no longer owned by the caller and must not be touched again.

tcf_qevent_handle() did not handle TC_ACT_CONSUMED: it fell through the switch and returned the skb to the caller as if classification had passed. The only qdisc that wires up qevents today is RED, via three call sites (qe_mark on RED_PROB_MARK/HARD_MARK, qe_early_drop on congestion_drop) red_enqueue() was continuing to operate on an skb it no longer owns in this case -- enqueueing it, dropping it, or updating statistics. Resulting in a UAF.

tc qdisc add dev eth0 root handle 1: red ... qevent early_drop block 10 tc filter add block 10 ... action ct

(with ct defrag enabled and traffic that produces out-of-order fragments, e.g. a fragmented UDP stream)

Handle TC_ACT_CONSUMED in tcf_qevent_handle() the same way the ingress and egress fast paths do: treat it as stolen and return NULL without touching the skb. Unlike the TC_ACT_STOLEN case, the skb must not be dropped/freed here, as it is no longer owned by us.

CVSS v3
9.8
EG Score
9.8(medium)
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
7%
KEV
Not listed

Published

July 26, 2026

Last Modified

July 27, 2026

Advisory Details (7)

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

net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5ed3d6f85991656667059d3fa5a1d683ac58c447
generic

net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/447d493034a9cf7bf13a2abac86d0573d907ec2f
generic

net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2140c2f3f2e7b066e1ae616ede8856cafd8015e9

Vendor Advisories for CVE-2026-64530(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 10× in last 7d / 10× 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-07-27 05:26 UTCEG score recompute
  2. 2026-07-27 05:26 UTCGHSA enrichment
  3. 2026-07-27 05:13 UTCEG score recompute 9.80
  4. 2026-07-27 05:13 UTCGHSA enrichment
  5. 2026-07-27 05:12 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 07:17 UTCNVD update
  9. 2026-07-26 07:14 UTCEG score recompute
  10. 2026-07-26 07:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64530?
CVE-2026-64530 is a critical vulnerability published on July 26, 2026. In the Linux kernel, the following vulnerability has been resolved: net/sched: clsapi: Handle TCACTCONSUMED in tcfqevent_handle tcfclassify() can return TCACT_CONSUMED while the skb is held by the defragmentation engine (e.g. act_ct on out-of-order fragments). When that happens the skb is no longer…
When was CVE-2026-64530 disclosed?
CVE-2026-64530 was first published in the National Vulnerability Database on July 26, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64530 actively exploited?
CVE-2026-64530 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 93.0% of all scored CVEs.
What is the CVSS score of CVE-2026-64530?
CVE-2026-64530 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-64530?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64530, 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-64530

Explore →

Is Your Infrastructure Affected by CVE-2026-64530?

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