net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle
Summary
| CVE | CVE-2026-64530 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-07-26 07:16:41 UTC |
|---|
| Updated | 2026-07-26 07:16:41 UTC |
|---|
| 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. |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 172ba7d46c202e679f3ccb10264c67416aaeb1c4 5ed3d6f85991656667059d3fa5a1d683ac58c447 git |
Not specified |
| CNA |
Linux |
Linux |
affected 0b5b831122fc3789fff75be433ba3e4dd7b779d4 f42e8134a3a1074b834a574d404352f867ba994a git |
Not specified |
| CNA |
Linux |
Linux |
affected 73f7da5fd124f2cda9161e2e46114915e6e82e97 447d493034a9cf7bf13a2abac86d0573d907ec2f git |
Not specified |
| CNA |
Linux |
Linux |
affected 3f14b377d01d8357eba032b4cabc8c1149b458b6 e1270e69dcf2c3512c453484178f2e9dc0db3f05 git |
Not specified |
| CNA |
Linux |
Linux |
affected 3f14b377d01d8357eba032b4cabc8c1149b458b6 2140c2f3f2e7b066e1ae616ede8856cafd8015e9 git |
Not specified |
| CNA |
Linux |
Linux |
affected 3f14b377d01d8357eba032b4cabc8c1149b458b6 e28aedab9488343924d227b5a896faed67ce84d5 git |
Not specified |
| CNA |
Linux |
Linux |
affected 3f14b377d01d8357eba032b4cabc8c1149b458b6 a8a02897f2b479127db261de05cbf0c28b98d159 git |
Not specified |
| CNA |
Linux |
Linux |
affected f5346df0591d10bc948761ca854b1fae6d2ef441 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.15.148 5.15.212 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.1.75 6.1.178 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.6.14 6.6.145 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.7.2 6.8 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.8 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.8 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.212 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.178 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.145 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.97 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.40 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1.5 7.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/f42e8134a3a1074b834a574d404352f867ba994a |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/5ed3d6f85991656667059d3fa5a1d683ac58c447 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/e1270e69dcf2c3512c453484178f2e9dc0db3f05 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/a8a02897f2b479127db261de05cbf0c28b98d159 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/447d493034a9cf7bf13a2abac86d0573d907ec2f |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/2140c2f3f2e7b066e1ae616ede8856cafd8015e9 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/e28aedab9488343924d227b5a896faed67ce84d5 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.