From: Hyunwoo Kim <imv4bel@gmail.com>
To: pablo@netfilter.org, fw@strlen.de, phil@nwl.cc,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org
Cc: netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, imv4bel@gmail.com
Subject: [PATCH net] netfilter: nf_flow_table_offload: fix heap overflow in flow_action_entry_next()
Date: Sun, 8 Mar 2026 02:23:06 +0900 [thread overview]
Message-ID: <aaxe-uH2Qr6qM4E9@v4bel> (raw)
flow_action_entry_next() increments num_entries and returns a pointer
into the flow_action_entry array without any bounds checking. The array
is allocated with a fixed size of NF_FLOW_RULE_ACTION_MAX (16) entries,
but certain combinations of IPv6 + SNAT + DNAT + double VLAN (QinQ)
require 17 or more entries, causing a slab-out-of-bounds write in the
kmalloc-4k slab.
The maximum possible entry count is:
tunnel(2) + eth(4) + VLAN(4) + IPv6_NAT(10) + redirect(1) = 21
Increase NF_FLOW_RULE_ACTION_MAX to 24 (with headroom) to cover the
worst case.
Fixes: efce49dfe6a8 ("netfilter: flowtable: add vlan pop action offload support")
Signed-off-by: Hyunwoo Kim <imv4bel@gmail.com>
---
net/netfilter/nf_flow_table_offload.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/netfilter/nf_flow_table_offload.c b/net/netfilter/nf_flow_table_offload.c
index 9b677e116487..e843f6d0355e 100644
--- a/net/netfilter/nf_flow_table_offload.c
+++ b/net/netfilter/nf_flow_table_offload.c
@@ -727,7 +727,7 @@ int nf_flow_rule_route_ipv6(struct net *net, struct flow_offload *flow,
}
EXPORT_SYMBOL_GPL(nf_flow_rule_route_ipv6);
-#define NF_FLOW_RULE_ACTION_MAX 16
+#define NF_FLOW_RULE_ACTION_MAX 24
static struct nf_flow_rule *
nf_flow_offload_rule_alloc(struct net *net,
--
2.43.0
next reply other threads:[~2026-03-07 17:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 17:23 Hyunwoo Kim [this message]
2026-03-07 19:04 ` [PATCH net] netfilter: nf_flow_table_offload: fix heap overflow in flow_action_entry_next() Florian Westphal
2026-03-16 10:53 ` Florian Westphal
2026-03-16 11:23 ` Hyunwoo Kim
2026-03-16 11:31 ` Hyunwoo Kim
2026-03-16 11:48 ` Florian Westphal
2026-03-16 11:56 ` Pablo Neira Ayuso
2026-03-16 14:17 ` Hyunwoo Kim
2026-03-16 14:58 ` Florian Westphal
2026-03-25 14:27 ` Florian Westphal
2026-03-25 15:18 ` Pablo Neira Ayuso
2026-03-08 10:41 ` Pablo Neira Ayuso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aaxe-uH2Qr6qM4E9@v4bel \
--to=imv4bel@gmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox