From: Florian Westphal <fw@strlen.de>
To: Chenyuan Yang <chenyuan0y@gmail.com>
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, casey@schaufler-ca.com
Subject: Re: [PATCH] net: Initialize ctx to avoid memory allocation error
Date: Thu, 13 Mar 2025 21:10:07 +0100 [thread overview]
Message-ID: <20250313201007.GA26103@breakpoint.cc> (raw)
In-Reply-To: <20250313195441.515267-1-chenyuan0y@gmail.com>
[ trim CCs, CC Casey ]
Chenyuan Yang <chenyuan0y@gmail.com> wrote:
> It is possible that ctx in nfqnl_build_packet_message() could be used
> before it is properly initialize, which is only initialized
> by nfqnl_get_sk_secctx().
>
> This patch corrects this problem by initializing the lsmctx to a safe
> value when it is declared.
>
> This is similar to the commit 35fcac7a7c25
> ("audit: Initialize lsmctx to avoid memory allocation error").
Fixes: 2d470c778120 ("lsm: replace context+len with lsm_context")
> Signed-off-by: Chenyuan Yang <chenyuan0y@gmail.com>
> ---
> net/netfilter/nfnetlink_queue.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/net/netfilter/nfnetlink_queue.c b/net/netfilter/nfnetlink_queue.c
> index 5c913987901a..8b7b39d8a109 100644
> --- a/net/netfilter/nfnetlink_queue.c
> +++ b/net/netfilter/nfnetlink_queue.c
> @@ -567,7 +567,7 @@ nfqnl_build_packet_message(struct net *net, struct nfqnl_instance *queue,
> enum ip_conntrack_info ctinfo = 0;
> const struct nfnl_ct_hook *nfnl_ct;
> bool csum_verify;
> - struct lsm_context ctx;
> + struct lsm_context ctx = { NULL, 0, 0 };
> int seclen = 0;
> ktime_t tstamp;
Someone that understands LSM should clarify what seclen == 0 means.
seclen needs to be > 0 or no secinfo is passed to userland,
yet the secctx release function is called anyway.
Should seclen be initialised to -1? Or we need the change below too?
diff --git a/net/netfilter/nfnetlink_queue.c b/net/netfilter/nfnetlink_queue.c
--- a/net/netfilter/nfnetlink_queue.c
+++ b/net/netfilter/nfnetlink_queue.c
@@ -812,7 +812,7 @@ nfqnl_build_packet_message(struct net *net, struct nfqnl_instance *queue,
}
nlh->nlmsg_len = skb->len;
- if (seclen >= 0)
+ if (seclen > 0)
security_release_secctx(&ctx);
return skb;
@@ -821,7 +821,7 @@ nfqnl_build_packet_message(struct net *net, struct nfqnl_instance *queue,
kfree_skb(skb);
net_err_ratelimited("nf_queue: error creating packet message\n");
nlmsg_failure:
- if (seclen >= 0)
+ if (seclen > 0)
security_release_secctx(&ctx);
return NULL;
}
next prev parent reply other threads:[~2025-03-13 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 19:54 [PATCH] net: Initialize ctx to avoid memory allocation error Chenyuan Yang
2025-03-13 20:10 ` Florian Westphal [this message]
2025-03-14 16:41 ` Casey Schaufler
2025-03-14 16:47 ` Florian Westphal
2025-03-14 17:26 ` Casey Schaufler
2025-03-14 20:30 ` Florian Westphal
2025-03-15 18:34 ` Casey Schaufler
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=20250313201007.GA26103@breakpoint.cc \
--to=fw@strlen.de \
--cc=casey@schaufler-ca.com \
--cc=chenyuan0y@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 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).