From: Greg KH <gregkh@linuxfoundation.org>
To: Qingfang DENG <dqfext@gmail.com>
Cc: stable@vger.kernel.org, Florian Westphal <fw@strlen.de>,
Shell Chen <xierch@gmail.com>
Subject: Re: [PATCH 5.15,5.10,5.4,4.19] netfilter: nft_tproxy: restrict to prerouting hook
Date: Fri, 17 Feb 2023 15:14:24 +0100 [thread overview]
Message-ID: <Y++LwO5sw8amUIFV@kroah.com> (raw)
In-Reply-To: <20230216124755.51762-1-dqfext@gmail.com>
On Thu, Feb 16, 2023 at 08:47:55PM +0800, Qingfang DENG wrote:
> From: Florian Westphal <fw@strlen.de>
>
> commit 18bbc3213383a82b05383827f4b1b882e3f0a5a5 upstream.
>
> TPROXY is only allowed from prerouting, but nft_tproxy doesn't check this.
> This fixes a crash (null dereference) when using tproxy from e.g. output.
>
> Fixes: 4ed8eb6570a4 ("netfilter: nf_tables: Add native tproxy support")
> Reported-by: Shell Chen <xierch@gmail.com>
> Signed-off-by: Florian Westphal <fw@strlen.de>
> Signed-off-by: Qingfang DENG <dqfext@gmail.com>
> ---
> net/netfilter/nft_tproxy.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2023-02-17 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 12:47 [PATCH 5.15,5.10,5.4,4.19] netfilter: nft_tproxy: restrict to prerouting hook Qingfang DENG
2023-02-17 14:14 ` Greg KH [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=Y++LwO5sw8amUIFV@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dqfext@gmail.com \
--cc=fw@strlen.de \
--cc=stable@vger.kernel.org \
--cc=xierch@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).