CVE-2026-74621net/sched: act_ct: fix sk_buff leak when the header checks reject a packet
- 7.5HighCVSS base score
- 0.49%Exploitation in 30 daysEPSS · top 57% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: net/sched: act_ct: fix sk_buff leak when the header checks reject a packet tcf_ct_handle_fragments() runs its header sanity checks before handing anything to the defragmentation engine: if (family == NFPROTO_IPV4) err = tcf_ct_ipv4_is_fragment(skb, &frag); else err = tcf_ct_ipv6_is_fragment(skb, &frag); if (err || !frag) return err; tcf_ct_ipv4_is_fragment() returns -EINVAL or -ENOMEM; tcf_ct_ipv6_is_fragment() adds -EPROTO when ipv6_find_hdr() fails. None of them frees or queues the skb, so on that path the caller still owns it. tcf_ct_act() however funnels every non-zero return into the ownership-transfer exit: err = tcf_ct_handle_fragments(net, skb, family, p->zone, &defrag); if (err) goto out_frag; ... out_frag: if (err != -EINPROGRESS) tcf_action_inc_drop_qstats(&c->common); return TC_ACT_CONSUMED; TC_ACT_CONSUMED means the action took ownership of the skb, so no caller frees it - sch_handle_ingress(), sch_handle_egress() and tcf_qevent_handle() all deliberately skip the free for that verdict. The skb is therefore orphaned: one sk_buff plus its data buffer is leaked per malformed packet, unbounded. Note the drop counter is already incremented for these errors, so the statistics claim a drop that never happens. Three different ownership states reach out_frag: today - the skb may be queued by the defrag engine (-EINPROGRESS), already freed by nf_ct_handle_fragments(), or still owned by us. Tell the caller which of those it is, and free the packet ourselves in the last case, which restores the TC_ACT_SHOT behaviour that predated the Fixes: commit. Reproduced on v7.2-rc6 with a 54-byte frame carrying a 40-byte IPv6 header with nexthdr = 0 (hop-by-hop) and nothing after it, on a clsact ingress chain with "action ct". kmemleak reports one leaked 232-byte skbuff_head_cache object plus its 704-byte data buffer per packet; with this patch it reports none.
Timeline
ID reserved
By Linux
- 7 days later
· 7 days later
Published
- 55 days later
· 55 days 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Received | 3.1 | High7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.49% · top 57% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: yes · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.
Affected products
- affected 172ba7d46c202e679f3ccb10264c67416aaeb1c4 – < b5dbecc2016e1692fd1c2532af9c41ba729cb747
- affected 0b5b831122fc3789fff75be433ba3e4dd7b779d4 – < 23e97d594ddd0153020c506d5041048fbde1beb4
- affected 73f7da5fd124f2cda9161e2e46114915e6e82e97 – < 737873a59905a54ca0d2d127ef882f3f88bf4379
- affected 3f14b377d01d8357eba032b4cabc8c1149b458b6 – < 47d99828591d0fe8be4b9c8992ff3b8e47968db9
- affected 3f14b377d01d8357eba032b4cabc8c1149b458b6 – < b47bb899e04b5407c5a63fe88d4b6676586a6e84
- affected 3f14b377d01d8357eba032b4cabc8c1149b458b6 – < 439d3e404f9d5e515911cc8132cde198b337c19e
- affected 3f14b377d01d8357eba032b4cabc8c1149b458b6 – < 8a7ed561671aa6a911a2de99e59ef670a4d0b1df
- affected f5346df0591d10bc948761ca854b1fae6d2ef441
- affected 5.15.148 – < 5.15.217
- affected 6.1.75 – < 6.1.184
- affected 6.6.14 – < 6.6.152
- affected 6.7.2 – < 6.8
- affected 6.8
- unaffected < 6.8
- unaffected 5.15.217 – ≤ 5.15.*
- unaffected 6.1.184 – ≤ 6.1.*
- unaffected 6.6.152 – ≤ 6.6.*
- unaffected 6.12.104 – ≤ 6.12.*
- unaffected 6.18.45 – ≤ 6.18.*
- unaffected 7.1.9 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References7
- https://git.kernel.org/stable/c/b5dbecc2016e1692fd1c2532af9c41ba729cb747 (opens in a new tab)
- https://git.kernel.org/stable/c/23e97d594ddd0153020c506d5041048fbde1beb4 (opens in a new tab)
- https://git.kernel.org/stable/c/737873a59905a54ca0d2d127ef882f3f88bf4379 (opens in a new tab)
- https://git.kernel.org/stable/c/47d99828591d0fe8be4b9c8992ff3b8e47968db9 (opens in a new tab)
- https://git.kernel.org/stable/c/b47bb899e04b5407c5a63fe88d4b6676586a6e84 (opens in a new tab)
- https://git.kernel.org/stable/c/439d3e404f9d5e515911cc8132cde198b337c19e (opens in a new tab)
- https://git.kernel.org/stable/c/8a7ed561671aa6a911a2de99e59ef670a4d0b1df (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-64558 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74621)Record last updated .