From: Aamir Ahmed <elb12345@hotmail.co.uk>
To: Florian Westphal <fw@strlen.de>
Cc: Aamir Ahmed <elb12345@hotmail.co.uk>,
Pablo Neira Ayuso <pablo@netfilter.org>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] netfilter: conntrack_irc: fix port value truncation in parse_dcc()
Date: Tue, 8 Sep 2026 03:03:42 +0100 [thread overview]
Message-ID: <PAXP251MB0010D8326ADF7FDF11D23452C8B12@PAXP251MB0010.EURP251.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <ap52kSh-U0VQ7z8P@strlen.de>
On Mon, Sep 07, 2026 at 10:32:17AM +0200, Florian Westphal wrote:
> Your other patch also rejects port == 0.
> Maybe also check and refuse for tmp_port < 1024 here.
Makes sense - the expectation is source-wildcarded and the DCC port is
the client's own listener, so a privileged port there is not something
the helper should open. v2 will reject tmp_port < 1024 || > 65535 and
drop the now-redundant dcc_port == 0 test in help() (or I can put the
floor there instead, so the forged-DCC warning still fires - your
preference). I will describe it as a behaviour change with your
Suggested-by rather than part of the truncation fix.
While respinning I noticed simple_strtoul() narrows to 32 bits before
the range check on 32-bit, so v2 will use simple_strtoull().
> This patch can be handled via nf-next, I think.
Will resend as [PATCH nf-next v2], without the stable Cc.
Kind Regards
Aamir A.
next prev parent reply other threads:[~2026-09-08 2:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 23:37 Aamir Ahmed
2026-09-07 8:32 ` Florian Westphal
2026-09-08 2:03 ` Aamir Ahmed [this message]
2026-09-09 21:40 ` netdev-bot+sashiko
2026-09-09 23:33 ` Aamir Ahmed
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=PAXP251MB0010D8326ADF7FDF11D23452C8B12@PAXP251MB0010.EURP251.PROD.OUTLOOK.COM \
--to=elb12345@hotmail.co.uk \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=stable@vger.kernel.org \
/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®