From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Cc: Florian Westphal <fw@strlen.de>
Subject: [PATCH nft] cache: don't crash when filter is NULL
Date: Tue, 1 Apr 2025 16:29:14 +0200 [thread overview]
Message-ID: <20250401142917.11171-1-fw@strlen.de> (raw)
a delete request will cause a crash in obj_cache_dump, move the deref
into the filter block.
Fixes: dbff26bfba83 ("cache: consolidate reset command")
Signed-off-by: Florian Westphal <fw@strlen.de>
---
src/cache.c | 6 ++++--
.../testcases/bogons/nft-f/delete_nonexistant_object_crash | 1 +
2 files changed, 5 insertions(+), 2 deletions(-)
create mode 100644 tests/shell/testcases/bogons/nft-f/delete_nonexistant_object_crash
diff --git a/src/cache.c b/src/cache.c
index b75a5bf3283c..c0d96bd14a80 100644
--- a/src/cache.c
+++ b/src/cache.c
@@ -902,6 +902,7 @@ static struct nftnl_obj_list *obj_cache_dump(struct netlink_ctx *ctx,
int family = NFPROTO_UNSPEC;
const char *table = NULL;
const char *obj = NULL;
+ bool reset = false;
bool dump = true;
if (filter) {
@@ -914,9 +915,10 @@ static struct nftnl_obj_list *obj_cache_dump(struct netlink_ctx *ctx,
}
if (filter->list.obj_type)
type = filter->list.obj_type;
+
+ reset = filter->reset.obj;
}
- obj_list = mnl_nft_obj_dump(ctx, family, table, obj, type, dump,
- filter->reset.obj);
+ obj_list = mnl_nft_obj_dump(ctx, family, table, obj, type, dump, reset);
if (!obj_list) {
if (errno == EINTR)
return NULL;
diff --git a/tests/shell/testcases/bogons/nft-f/delete_nonexistant_object_crash b/tests/shell/testcases/bogons/nft-f/delete_nonexistant_object_crash
new file mode 100644
index 000000000000..c369dec8c07d
--- /dev/null
+++ b/tests/shell/testcases/bogons/nft-f/delete_nonexistant_object_crash
@@ -0,0 +1 @@
+delete quota a b
--
2.49.0
next reply other threads:[~2025-04-01 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 14:29 Florian Westphal [this message]
2025-04-01 14:33 ` [PATCH nft] cache: don't crash when filter is NULL Pablo Neira Ayuso
2025-04-01 14:39 ` 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=20250401142917.11171-1-fw@strlen.de \
--to=fw@strlen.de \
--cc=netfilter-devel@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.