CVE-2026-64530

CVE CVE-2026-64530EUVD EUVD-2026-49051Published 2026-07-26T06:28:42.000ZLast changed 2026-08-05T12:42:39.000ZCVSS 9.8

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

Linux — Linux 6.7.2 <6.8; 6.8; patch: 6.6.145; 3f14b377d01d8357eba032b4cabc8c1149b458b6 <e28aedab9488343924d227b5a896faed67ce84d5; patch: 7.1.5; patch: 6.18.40; 6.6.14 <6.6.145; 3f14b377d01d8357eba032b4cabc8c1149b458b6 <a8a02897f2b479127db261de05cbf0c28b98d159; f5346df0591d10bc948761ca854b1fae6d2ef441; patch: 0; patch: 6.12.97; 3f14b377d01d8357eba032b4cabc8c1149b458b6 <2140c2f3f2e7b066e1ae616ede8856cafd8015e9; 73f7da5fd124f2cda9161e2e46114915e6e82e97 <447d493034a9cf7bf13a2abac86d0573d907ec2f; patch: 6.1.178; patch: 7.2-rc1; 0b5b831122fc3789fff75be433ba3e4dd7b779d4 <f42e8134a3a1074b834a574d404352f867ba994a; 172ba7d46c202e679f3ccb10264c67416aaeb1c4 <5ed3d6f85991656667059d3fa5a1d683ac58c447; 5.15.148 <5.15.212; 6.1.75 <6.1.178; patch: 5.15.212; 3f14b377d01d8357eba032b4cabc8c1149b458b6 <e1270e69dcf2c3512c453484178f2e9dc0db3f05

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

Linux — Linux

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.