From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>, stable <stable@vger.kernel.org>
Subject: Re: Inconsistency about backports to stable series for 6e1acfa387b9 ("netfilter: nf_tables: validate registers coming from userspace.")?
Date: Mon, 26 Jun 2023 01:16:23 +0200 [thread overview]
Message-ID: <ZJjKxyKJLc12BUEi@calendula> (raw)
In-Reply-To: <ZJhYcEqINyrKpCWV@eldamar.lan>
Hi,
On Sun, Jun 25, 2023 at 05:08:32PM +0200, Salvatore Bonaccorso wrote:
> Hi Pablo,
>
> While checking netfilter backports to the stable series, I noticed
> that 6e1acfa387b9 ("netfilter: nf_tables: validate registers coming
> from userspace.") was backported in various series for stable, and
> included in 4.14.316, 4.19.284, 5.4.244, 5.15.32, 5.16.18, 5.17.1,
> where the original fix was in 5.18-rc1.
>
> While the commit has
>
> Fixes: 49499c3e6e18 ("netfilter: nf_tables: switch registers to 32 bit addressing")
>
> the 6e1acfa387b9 change got not backported to the 5.10.y series.
>
> The backports to the other series are
>
> https://lore.kernel.org/stable/20230516151606.4892-1-pablo@netfilter.org/
> https://lore.kernel.org/stable/20230516150613.4566-1-pablo@netfilter.org/
> https://lore.kernel.org/stable/20230516144435.4010-1-pablo@netfilter.org/
>
> Pablo, was this an oversight and can the change as well be applied to
> 5.10.y?
>
> From looking at the 5.4.y series, from the stable dependencies,
> 08a01c11a5bb ("netfilter: nftables: statify nft_parse_register()") is
> missing in 5.10.y, then 6e1acfa387b9 ("netfilter: nf_tables: validate
> registers coming from userspace.") can be applied (almost, the comment
> needs to be dropped, as done in the backports).
>
> I'm right now not understanding what I'm missing that it was for 5.4.y
> but not 5.10.y after the report of the failed apply by Greg.
>
> At least the two attached bring 5.10.y inline with 5.4.y up to 4) from
> https://lore.kernel.org/stable/20230516144435.4010-1-pablo@netfilter.org/
> but I'm unsure if you want/need as well the remaining 5), 6), 7), 8)
> and 9).
Let me take a look, I can prepare a batch for 5.10.y based on 5.4.y as
you suggest. I'll keep you on Cc.
prev parent reply other threads:[~2023-06-25 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 15:08 Inconsistency about backports to stable series for 6e1acfa387b9 ("netfilter: nf_tables: validate registers coming from userspace.")? Salvatore Bonaccorso
2023-06-25 23:16 ` Pablo Neira Ayuso [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=ZJjKxyKJLc12BUEi@calendula \
--to=pablo@netfilter.org \
--cc=carnil@debian.org \
--cc=gregkh@linuxfoundation.org \
--cc=sashal@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.