CVE-2026-64530

net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle

CRITICAL
9.8
CVSS Score
Published: July 26, 2026 at 06:28 AM UTC
Updated: October 19, 2026 at 09:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
CRITICAL9.8
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

0b5b831122fc3789fff75be433ba3e4dd7b779d4172ba7d46c202e679f3ccb10264c67416aaeb1c43f14b377d01d8357eba032b4cabc8c1149b458b65.15.1486.1.756.6.146.7.26.873f7da5fd124f2cda9161e2e46114915e6e82e97f5346df0591d10bc948761ca854b1fae6d2ef441
Vendor states this is fixed in 2140c2f3f2e7b066e1ae616ede8856cafd8015e9 (fixed)
Vendor states this is fixed in 447d493034a9cf7bf13a2abac86d0573d907ec2f (fixed)
Vendor states this is fixed in 5ed3d6f85991656667059d3fa5a1d683ac58c447 (fixed)
Vendor states this is fixed in a8a02897f2b479127db261de05cbf0c28b98d159 (fixed)
Vendor states this is fixed in e1270e69dcf2c3512c453484178f2e9dc0db3f05 (fixed)
Vendor states this is fixed in e28aedab9488343924d227b5a896faed67ce84d5 (fixed)
Vendor states this is fixed in f42e8134a3a1074b834a574d404352f867ba994a (fixed)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitAutomatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

9.8CRITICALLinux
Vector?

Quick Info

StatusRECEIVED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card