CVE-2026-64530

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 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: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

July 26, 2026

Last Modified

August 17, 2026

Advisory Details (7)

Auto-updated Sep 14, 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(17)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkpatch-patch2026-08-19redhat
redhatkernel-0:5.14.0-284.184.1.el9_22026-07-31redhat
redhatkernel-0:4.18.0-553.150.1.el8_102026-07-31redhat
redhatkernel-0:4.18.0-372.204.1.el8_62026-07-31redhat
redhatkernel-0:5.14.0-687.33.1.el9_82026-07-31redhat
redhatkernel-0:6.12.0-211.42.1.el10_22026-07-31redhat
redhatkernel-rt-0:4.18.0-553.150.1.rt7.491.el8_102026-07-31redhat
redhatkernel-rt-0:5.14.0-284.184.1.rt14.469.el9_22026-07-29redhat
redhatkernel-0:6.12.0-55.93.1.el10_02026-07-29redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1
linux-6.126.12.100-1~deb12u1
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)6.12.100-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (159 versions)7.1.5-1

Data Freshness Timeline

(refreshed 56× in last 7d / 261× 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 542 total refreshes for this CVE.

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

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 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-64530 actively exploited?
CVE-2026-64530 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.4% 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

See which npm, PyPI, Go, and Maven packages are affected by 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.