CVE-2026-74740 json
net/sched: act_api: fix TOCTOU NULL deref on a->goto_chain
published 2026-08-26 2 mo ago modified 2026-10-30 9 d ago also EUVD-2026-66570
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
net/sched: act_api: fix TOCTOU NULL deref on a->goto_chain
tcf_action_exec() handles TC_ACT_GOTO_CHAIN by first checking rcu_access_pointer(a->goto_chain) and then calling tcf_action_goto_chain_exec(), which does a second, independent rcu_dereference_bh(a->goto_chain) read and immediately dereferences chain->filter_chain. A concurrent tcf_action_set_ctrlact() (e.g. the gact replace path) can clear a->goto_chain between the two reads, so the second read returns NULL and tcf_action_goto_chain_exec() dereferences NULL.
Fix the race by doing a single rcu_dereference_bh() read of a->goto_chain in tcf_action_exec(), checking it once for NULL, and passing the resulting chain pointer into tcf_action_goto_chain_exec(). This turns the split check/use into a single check/use on one value.
Patch / fix
- Linux Linux 6.1.191, 6.6.153, 6.12.105, 6.18.46, 7.1.10, 7.2
- linux Debian 13 6.12.105-1
- linux Debian 14 7.1.10-1
- linux-6.12 Debian 12 6.12.107-1~deb12u1
debian advisories DEBIAN-CVE-2026-74740
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1017.17
- linux-riscv Ubuntu 26.04 LTS 7.0.0-42.42.1
- linux-oracle Ubuntu 26.04 LTS 7.0.0-1015.16
- linux-hwe-7.0 Ubuntu 24.04 LTS 7.0.0-42.42~24.04.1
- linux-oem-7.0 Ubuntu 26.04 LTS 7.0.0-1017.17
ubuntu advisories UBUNTU-CVE-2026-74740
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/28aa0c9dd0b1b38436995d4c15621ad3f896c7e3 commit
- git.kernel.org/stable/c/91d55fd1fdb85c8371ca8793c788ea7d5192383a commit
- git.kernel.org/stable/c/1ec48b6715c29b20105e3485206602cff6c51ae5 commit
- git.kernel.org/stable/c/abceabc4408fca6a9dd52611f5d197dec9390d63 commit
- git.kernel.org/stable/c/6b70886ebc428eed43a069c8944a931b5fb3f4e4 commit
- git.kernel.org/stable/c/f60b396ee174206fe08ebf997d16cd3801b77b22 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-74740 updated cvss 5.5
kernel: net/sched: act_api: fix TOCTOU NULL deref on a->goto_chain
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/28aa0c9dd0b1b38436995d4c15621ad3f896c7e3
- git.kernel.org /stable/c/91d55fd1fdb85c8371ca8793c788ea7d5192383a
- git.kernel.org /stable/c/1ec48b6715c29b20105e3485206602cff6c51ae5
- git.kernel.org /stable/c/abceabc4408fca6a9dd52611f5d197dec9390d63
- git.kernel.org /stable/c/6b70886ebc428eed43a069c8944a931b5fb3f4e4
- git.kernel.org /stable/c/f60b396ee174206fe08ebf997d16cd3801b77b22
Sources
- CVE List CVE-2026-74740
- NVD CVE-2026-74740
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.