CVE-2026-74621
kernel: net/sched: act_ct: fix sk_buff leak when the header checks reject a packet
Overview
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.
Source: OX vulnerability database
Severity
7.5 · HIGH
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected packages · 0
No registry package. This ID affects operating system packages only.
Operating systems · 84 fixes
Azure Linux 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 3.0 | kernel | 0:6.6.152.1-1.azl3 |
Oracle Linux 2 releases · 2 packages
| Release | Package | Fixed in |
|---|---|---|
| 8 | bpftool +13 | 5.15.0-325.220.5.el8uek |
| 9 | bpftool +2 | 5.15.0-325.220.5.el9uek |
| 9 | kernel-uek +34 | 6.12.0-207.111.5.1.el9uek |
Photon OS 1 release · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 5.0 | bpftool +10 | 6.12.107-1.ph5 |
Red Hat 2 releases · 1 package
| Release | Package | Fixed in |
|---|---|---|
| 8 | bpftool +45 | affected |
| 9 | bpftool +106 | affected |
debian 3 releases · 2 packages
| Release | Package | Fixed in |
|---|---|---|
| 12 | linux | 6.1.187-1 |
| 12 | linux-6-12 | 6.12.107-1~deb12u1 |
| 13 | linux | 6.12.105-1 |
| 14 | linux | 7.1.9-1 |
echo 1 release · 2 packages
| Release | Package | Fixed in |
|---|---|---|
| linux | 1 | |
| linux-6-12 | 6.12.107-1~deb12u1 |
ubuntu 4 releases · 48 packages
| Release | Package | Fixed in |
|---|---|---|
| 20.04-ESM | linux-nvidia-tegra-5-15 | 5.15.0-1070.72~20.04.1 |
| 20.04-ESM | linux-ibm-5-15 | 5.15.0-1113.117~20.04.1 |
| 20.04-ESM | linux-riscv-5-15 | 5.15.0-1113.117~20.04.2 |
| 20.04-ESM | linux-intel-iotg-5-15 | 5.15.0-1114.120~20.04.1 |
| 20.04-ESM | linux-oracle-5-15 | 5.15.0-1116.122~20.04.1 |
| 20.04-ESM | linux-aws-5-15 | 5.15.0-1119.126~20.04.1 |
65 more rows
References
- access.redhat.com https://access.redhat.com/security/cve/CVE-2026-74621
- git.kernel.org https://git.kernel.org/stable/c/23e97d594ddd0153020c506d5041048fbde1beb4
- git.kernel.org https://git.kernel.org/stable/c/439d3e404f9d5e515911cc8132cde198b337c19e
- git.kernel.org https://git.kernel.org/stable/c/47d99828591d0fe8be4b9c8992ff3b8e47968db9
- git.kernel.org https://git.kernel.org/stable/c/737873a59905a54ca0d2d127ef882f3f88bf4379
- git.kernel.org https://git.kernel.org/stable/c/8a7ed561671aa6a911a2de99e59ef670a4d0b1df
- git.kernel.org https://git.kernel.org/stable/c/b47bb899e04b5407c5a63fe88d4b6676586a6e84
- git.kernel.org https://git.kernel.org/stable/c/b5dbecc2016e1692fd1c2532af9c41ba729cb747
- kernelcve.org https://kernelcve.org/list/?q=CVE-2026-74621
- linux.oracle.com https://linux.oracle.com/cve/CVE-2026-74621.html
Show all 30 references
- linux.oracle.com https://linux.oracle.com/errata/ELSA-2026-500377.html
- lore.kernel.org https://lore.kernel.org/linux-cve-announce/2026082219-CVE-2026-74621-81bd@gregkh/T
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2026-74621
- ubuntu.com https://ubuntu.com/security/notices/USN-8886-1
- ubuntu.com https://ubuntu.com/security/notices/USN-8959-1
- ubuntu.com https://ubuntu.com/security/notices/USN-8961-1
- ubuntu.com https://ubuntu.com/security/notices/USN-8963-1
- ubuntu.com https://ubuntu.com/security/notices/USN-9019-1
- ubuntu.com https://ubuntu.com/security/notices/USN-9020-1
- ubuntu.com https://ubuntu.com/security/notices/USN-9021-1
- ubuntu.com https://ubuntu.com/security/notices/USN-9022-1
- ubuntu.com https://ubuntu.com/security/notices/USN-9023-1
- ubuntu.com https://ubuntu.com/security/notices/USN-9024-1
- ubuntu.com https://ubuntu.com/security/notices/USN-9025-1
- ubuntu.com https://ubuntu.com/security/notices/USN-9026-1
- ubuntu.com https://ubuntu.com/security/notices/USN-9029-1
- ubuntu.com https://ubuntu.com/security/notices/USN-9039-1
- ubuntu.com https://ubuntu.com/security/notices/USN-9040-1
- ubuntu.com https://ubuntu.com/security/notices/USN-9066-1
- www.cve.org https://www.cve.org/CVERecord?id=CVE-2026-74621
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.