Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64530net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64530, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.66% · top 48% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected 172ba7d46c202e679f3ccb10264c67416aaeb1c4 – < 5ed3d6f85991656667059d3fa5a1d683ac58c447
    • affected 0b5b831122fc3789fff75be433ba3e4dd7b779d4 – < f42e8134a3a1074b834a574d404352f867ba994a
    • affected 73f7da5fd124f2cda9161e2e46114915e6e82e97 – < 447d493034a9cf7bf13a2abac86d0573d907ec2f
    • affected 3f14b377d01d8357eba032b4cabc8c1149b458b6 – < e1270e69dcf2c3512c453484178f2e9dc0db3f05
    • affected 3f14b377d01d8357eba032b4cabc8c1149b458b6 – < 2140c2f3f2e7b066e1ae616ede8856cafd8015e9
    • affected 3f14b377d01d8357eba032b4cabc8c1149b458b6 – < e28aedab9488343924d227b5a896faed67ce84d5
    • affected 3f14b377d01d8357eba032b4cabc8c1149b458b6 – < a8a02897f2b479127db261de05cbf0c28b98d159
    • affected f5346df0591d10bc948761ca854b1fae6d2ef441
    • affected 5.15.148 – < 5.15.212
    • affected 6.1.75 – < 6.1.178
    • affected 6.6.14 – < 6.6.145
    • affected 6.7.2 – < 6.8
  • Linux · Linux

    • affected 6.8
    • unaffected < 6.8
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64530 badge
[![CVE-2026-64530](https://cveledger.app/badge/CVE-2026-64530.svg)](https://cveledger.app/cve/CVE-2026-64530)

Record last updated .