From: Julian Anastasov <ja@ssi.bg>
To: Zihan Xi <zihanx@nebusec.ai>
Cc: Simon Horman <horms@verge.net.au>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Florian Westphal <fw@strlen.de>, Phil Sutter <phil@nwl.cc>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, lvs-devel@vger.kernel.org,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 2/2] ipvs: reject FTP control ports as data ports
Date: Sat, 19 Sep 2026 13:08:48 +0300 (EEST) [thread overview]
Message-ID: <a1ba4cd8-6e18-1ae9-fd96-8bb87f434f99@ssi.bg> (raw)
In-Reply-To: <7b561a02-461d-2320-75e4-241dd213d9f0@ssi.bg>
Hello,
On Fri, 18 Sep 2026, Julian Anastasov wrote:
> On Thu, 17 Sep 2026, Zihan Xi wrote:
>
> > ip_vs_ftp_out() creates a wildcard data connection from the
> > server-advertised passive port. If that port is one of the configured FTP
> > control ports, ip_vs_conn_new() binds the FTP helper to the new connection
> > again. A subsequent wildcard lookup can then extend a controlled-connection
> > chain.
> >
> > Reject zero and configured control ports before creating passive
> > connections. For active mode, reject a zero client port and a data port
> > derived from a configured control port.
> >
> > Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> > Cc: stable@vger.kernel.org
> > Reported-by: Vega <vega@nebusec.ai>
> > Assisted-by: LLM
> > Co-developed-by: Luxing Yin <root@tr0jan.top>
> > Signed-off-by: Luxing Yin <root@tr0jan.top>
> > Signed-off-by: Zihan Xi <zihanx@nebusec.ai>
>
> Patch looks good to me for the nf tree, thanks!
>
> Signed-off-by: Julian Anastasov <ja@ssi.bg>
Patch is ok but needs to be resent with
the other patch:
pw-bot: changes-requested
> > changes in v2:
> > - Reject the data port derived from a configured control port in
> > ip_vs_ftp_in() to cover the active-mode bypass.
> > - v1 Link:
> > https://lore.kernel.org/all/cover.1789110326.git.zihanx@nebusec.ai/
> >
> > net/netfilter/ipvs/ip_vs_ftp.c | 18 ++++++++++++++++++
> > 1 file changed, 18 insertions(+)
> >
> > diff --git a/net/netfilter/ipvs/ip_vs_ftp.c b/net/netfilter/ipvs/ip_vs_ftp.c
> > index 9e3e005a82635..4822a1a75212d 100644
> > --- a/net/netfilter/ipvs/ip_vs_ftp.c
> > +++ b/net/netfilter/ipvs/ip_vs_ftp.c
> > @@ -62,6 +62,17 @@ static unsigned short ports[IP_VS_APP_MAX_PORTS] = {21, 0};
> > module_param_array(ports, ushort, &ports_count, 0444);
> > MODULE_PARM_DESC(ports, "Ports to monitor for FTP control commands");
> >
> > +static bool is_control_port(u16 port)
> > +{
> > + unsigned int i;
> > +
> > + for (i = 0; i < ports_count; i++) {
> > + if (ports[i] == port)
> > + return true;
> > + }
> > + return false;
> > +}
> > +
> >
> > static char *ip_vs_ftp_data_ptr(struct sk_buff *skb, struct ip_vs_iphdr *ipvsh)
> > {
> > @@ -319,6 +330,10 @@ static int ip_vs_ftp_out(struct ip_vs_app *app, struct ip_vs_conn *cp,
> > return 1;
> > }
> >
> > + /* Do not redirect data to control ports */
> > + if (!port || is_control_port(ntohs(port)))
> > + return 0;
> > +
> > /* Now update or create a connection entry for it */
> > {
> > struct ip_vs_conn_param p;
> > @@ -529,6 +544,9 @@ static int ip_vs_ftp_in(struct ip_vs_app *app, struct ip_vs_conn *cp,
> > return 1;
> > }
> >
> > + if (!port || is_control_port(ntohs(cp->vport) - 1))
> > + return 0;
> > +
> > /* Passive mode off */
> > cp->app_data = (void *) IP_VS_FTP_ACTIVE;
> >
> > --
> > 2.43.0
Regards
--
Julian Anastasov <ja@ssi.bg>
prev parent reply other threads:[~2026-09-19 10:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 3:02 [PATCH net v2 0/2] ipvs: avoid stack overflow from recursive connection expiration Zihan Xi
2026-09-17 3:02 ` [PATCH net v2 1/2] " Zihan Xi
2026-09-18 16:49 ` Julian Anastasov
2026-09-19 10:06 ` Julian Anastasov
2026-09-21 3:19 ` netdev-bot+sashiko
2026-09-21 6:50 ` Julian Anastasov
2026-09-21 7:10 ` zihan xi
2026-09-17 3:02 ` [PATCH net v2 2/2] ipvs: reject FTP control ports as data ports Zihan Xi
2026-09-18 16:54 ` Julian Anastasov
2026-09-19 10:08 ` Julian Anastasov [this message]
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=a1ba4cd8-6e18-1ae9-fd96-8bb87f434f99@ssi.bg \
--to=ja@ssi.bg \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=horms@verge.net.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvs-devel@vger.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 \
--cc=zihanx@nebusec.ai \
/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
all inboxes | Powered by JetHome®