CVE-2026-99294 · Runtime
NO FIX YET
A netfilter nftables rule using nft_fwd_neigh in an egress chain can forward a packet back to the same device or between two devices, which re-enters the egress hook without limit. The result is infinite recursion and a kernel stack overflow, which crashes the system.
first public Nov 16, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Only Linux systems that use nftables rules with nft_fwd_neigh in netdev egress chains, where forwarding can target the same device or loop between two devices. Ordinary hosts without such rules are not exposed. The sources do not state affected kernel versions.
Not affected if default-config, no-nftables-egress-rules
Who cares kernel, linux, netfilter, nftables
uname -r and compare against the fixed kernel versions in the kernel changelog (unknown from the sources)nft list ruleset and look for fwd with neigh in an egress chain (unknown from the sources)Unknown from the sources.
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_fwd_netdev: use recursion counter in neigh egress path
nft_fwd_neigh can be used in egress chains (NF_NETDEV_EGRESS). When the forwarding rule targets the same device or two devices forward to each other, neigh_xmit() triggers dev_queue_xmit() which re-enters nf_hook_egress(), causing infinite recursion and stack overflow.
Move the nf_get_nf_dup_skb_recursion() accessor and NF_RECURSION_LIMIT to the shared header nf_dup_netdev.h as a static inline, so that nft_fwd_netdev can use the recursion counter directly without exported function call overhead. Guard neigh_xmit() with the same recursion limit already used in nf_do_netdev_egress().
[ Updated to cache the nf_get_nf_dup_skb_recursion pointer. --pablo ]
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.