netfilter: cttimeout: detach dataplane timeout policy and repurpose refcount
CVE-2026-74347 · published 15 Aug 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-74347?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: 50978462300f74dc48aea4a38471cb69bdf741a5 to < 1241e459a1bd17044fa6bbb68f491ab5543c3a1b, 50978462300f74dc48aea4a38471cb69bdf741a5 to < b2e84317f334d834fb06c9b340ea465f398b6d4f, 50978462300f74dc48aea4a38471cb69bdf741a5 to < 44583fd5735cb0bdf3bfe11b1e51504ce387bdb7, 50978462300f74dc48aea4a38471cb69bdf741a5 to < 9aeb0dcfeb460d33d61d434148b51103ab1d2013
- Linux Linux: 3.4
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
netfilter: cttimeout: detach dataplane timeout policy and repurpose refcount
Add a refcount for struct nf_ct_timeout which is used by ct extension to
set the custom ct timeout policy, this tells us that the ct timeout is
being used by a conntrack entry. When the last conntrack entry drops the
refcount on the ct timeout, the ct timeout is released.
Remove the refcount for control plane which controls if the ruleset
refers to the timeout policy. After this update, it is possible to
remove the ct timeout policy from nfnetlink_cttimeout immediately.
This is for simplicity not to handle two refcounts on a single object.
Remove nf_queue_nf_hook_drop(): a packet sitting in nfqueue will just
hold a reference to the nf_ct_timeout object until packet is reinjected,
since this is part of the ct extension, this will be released by the
time the conntrack is freed.
nf_ct_untimeout() is still called to clean up in a best effort basis:
the ct timeout on existing entries gets removed when the ct timeout goes
away, but as long as the iptables ruleset still refers to the ct timeout
through a template, new conntracks may keep attaching it and extend its
lifetime until the rule is removed.
nf_ct_untimeout() is not called anymore from module removal path, this
is unlikely to find timeouts give module refcount is bumped, and the new
refcount already tracks the ct timeout policy use so it is released when
unused.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/1241e459a1bd17044fa6bbb68f491ab5543c3a1b
- git.kernel.org/stable/c/b2e84317f334d834fb06c9b340ea465f398b6d4f
- git.kernel.org/stable/c/44583fd5735cb0bdf3bfe11b1e51504ce387bdb7
- git.kernel.org/stable/c/9aeb0dcfeb460d33d61d434148b51103ab1d2013
- git.kernel.org/stable/c/7d6a9cdb8d3a51d9cfe546a09a518ab3d2671549
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON