CVE-2026-99294
netfilter: nft_fwd_netdev: use recursion counter in neigh egress path
What happened?
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 ]
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: f87b9464d152f7705f1e37288dc48f5af6a2fc0c to < fcacd948b10a351aa128acd3c2c4cee62d1ea677; affected: f87b9464d152f7705f1e37288dc48f5af6a2fc0c to < 1d47b55b36d2ec73fe6901212c8b28a593c3b27c | See vendor advisory |
| LinuxLinux | affected: 5.17; unaffected: 0 to < 5.17; unaffected: 6.18.57 to ≤ 6.18.*; unaffected: 7.1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.