CVE-2026-23270

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks

As Paolo said earlier [1]:

"Since the blamed commit below, classify can return TC_ACT_CONSUMED while the current skb being held by the defragmentation engine. As reported by GangMin Kim, if such packet is that may cause a UaF when the defrag engine later on tries to tuch again such packet."

act_ct was never meant to be used in the egress path, however some users are attaching it to egress today [2]. Attempting to reach a middle ground, we noticed that, while most qdiscs are not handling TC_ACT_CONSUMED, clsact/ingress qdiscs are. With that in mind, we address the issue by only allowing act_ct to bind to clsact/ingress qdiscs and shared blocks. That way it's still possible to attach act_ct to egress (albeit only with clsact).

[1] https://lore.kernel.org/netdev/674b8cbfc385c6f37fb29a1de08d8fe5c2b0fbee.1771321118.git.pabeni@redhat.com/ [2] https://lore.kernel.org/netdev/cc6bfb4a-4a2b-42d8-b9ce-7ef6644fb22b@ovn.org/

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

Published

March 18, 2026

Last Modified

July 14, 2026

Advisory Details (7)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks - kernel/git/stable/linux.git - Linux kernel stable tree

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

net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/524ce8b4ea8f64900b6c52b6a28df74f6bc0801e
generic

net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/380ad8b7c65ea7aa10ef2258297079ed5ac1f5b6
generic

net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/11cb63b0d1a0685e0831ae3c77223e002ef18189

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-55.77.1.el10_02026-06-08redhat
redhatkernel-0:5.14.0-570.119.1.el9_62026-06-04redhat
redhatkernel-0:5.14.0-284.174.1.el9_22026-06-03redhat
redhatkernel-rt-0:5.14.0-284.174.1.rt14.459.el9_22026-06-03redhat
redhatkernel-0:4.18.0-553.126.1.el8_102026-05-28redhat
redhatkernel-rt-0:4.18.0-553.126.1.rt7.467.el8_102026-05-28redhat
redhatkernel-0:5.14.0-427.127.1.el9_42026-05-27redhat
redhatkernel-0:6.12.0-211.16.1.el10_22026-05-20redhat
redhatkernel-0:5.14.0-687.10.1.el9_82026-05-20redhat
redhatkernel-0:5.14.0-611.54.1.el9_72026-05-04redhat
redhatkernel-0:6.12.0-124.55.1.el10_12026-05-04redhat
linuxKernel @ 5.15.203osv
linuxKernel @ 6.1.167osv

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 42× 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 123 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23270?
CVE-2026-23270 is a high vulnerability published on March 18, 2026. In the Linux kernel, the following vulnerability has been resolved: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks As Paolo said earlier [1]: "Since the blamed commit below, classify can return TCACTCONSUMED while the current skb being held by the defragmentation…
When was CVE-2026-23270 disclosed?
CVE-2026-23270 was first published in the National Vulnerability Database on March 18, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23270 actively exploited?
CVE-2026-23270 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-23270?
CVE-2026-23270 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23270?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23270, 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-23270

Explore →

Is Your Infrastructure Affected by CVE-2026-23270?

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