From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: davem@davemloft.net, netdev@vger.kernel.org, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com
Subject: [PATCH net 0/2] Netfilter fixes for net
Date: Sat, 2 Jul 2022 21:10:26 +0200 [thread overview]
Message-ID: <20220702191029.238563-1-pablo@netfilter.org> (raw)
Hi,
The following patchset contains Netfilter fixes for net:
1) Insufficient validation of element datatype and length in
nft_setelem_parse_data(). At least commit 7d7402642eaf updates
maximum element data area up to 64 bytes when only 16 bytes
where supported at the time. Support for larger element size
came later in fdb9c405e35b though. Picking this older commit
as Fixes: tag to be safe than sorry.
2) Memleak in pipapo destroy path, reproducible when transaction
in aborted. This is already triggering in the existing netfilter
test infrastructure since more recent new tests are covering this
path.
Please, pull these changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git
Thanks.
----------------------------------------------------------------
The following changes since commit f8ebb3ac881b17712e1d5967c97ab1806b16d3d6:
net: usb: ax88179_178a: Fix packet receiving (2022-06-30 10:41:57 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git HEAD
for you to fetch changes up to 9827a0e6e23bf43003cd3d5b7fb11baf59a35e1e:
netfilter: nft_set_pipapo: release elements in clone from abort path (2022-07-02 21:04:19 +0200)
----------------------------------------------------------------
Pablo Neira Ayuso (2):
netfilter: nf_tables: stricter validation of element data
netfilter: nft_set_pipapo: release elements in clone from abort path
net/netfilter/nf_tables_api.c | 9 +++++++-
net/netfilter/nft_set_pipapo.c | 48 +++++++++++++++++++++++++++++-------------
2 files changed, 41 insertions(+), 16 deletions(-)
next reply other threads:[~2022-07-02 19:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 19:10 Pablo Neira Ayuso [this message]
2022-07-02 19:10 ` [PATCH net 1/2] netfilter: nf_tables: stricter validation of element data Pablo Neira Ayuso
2022-07-03 11:30 ` patchwork-bot+netdevbpf
2022-07-02 19:10 ` [PATCH net 2/2] netfilter: nft_set_pipapo: release elements in clone from abort path Pablo Neira Ayuso
-- strict thread matches above, loose matches on Subject: below --
2025-04-10 10:36 [PATCH net 0/2] Netfilter fixes for net Pablo Neira Ayuso
2025-01-09 12:35 Pablo Neira Ayuso
2024-09-11 22:25 Pablo Neira Ayuso
2024-08-28 21:47 Pablo Neira Ayuso
2024-07-31 21:30 Pablo Neira Ayuso
2024-07-11 9:39 Pablo Neira Ayuso
2024-06-26 23:38 Pablo Neira Ayuso
2024-01-03 11:29 Pablo Neira Ayuso
2023-12-22 10:42 Pablo Neira Ayuso
2023-12-22 10:49 ` Pablo Neira Ayuso
2023-12-22 10:53 ` Pablo Neira Ayuso
2023-12-20 15:15 Pablo Neira Ayuso
2023-10-25 10:08 Pablo Neira Ayuso
2023-04-21 10:56 Pablo Neira Ayuso
2023-04-20 17:06 Pablo Neira Ayuso
2023-04-21 3:25 ` Jakub Kicinski
2023-01-31 13:31 Pablo Neira Ayuso
2023-01-23 21:15 Pablo Neira Ayuso
2022-11-18 14:29 Pablo Neira Ayuso
2022-10-19 6:52 Pablo Neira Ayuso
2022-05-26 20:54 Pablo Neira Ayuso
2022-04-12 9:42 Pablo Neira Ayuso
2022-04-05 10:09 Pablo Neira Ayuso
2021-06-02 12:44 Pablo Neira Ayuso
2021-02-09 21:35 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=20220702191029.238563-1-pablo@netfilter.org \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.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).