From: Simon Horman <horms@kernel.org>
To: Ranganath V N <vnranganath.20@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, jhs@mojatatu.com,
jiri@resnulli.us, kuba@kernel.org, pabeni@redhat.com,
xiyou.wangcong@gmail.com, david.hunter.linux@gmail.com,
khalid@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, skhan@linuxfoundation.org,
syzbot+0c85cae3350b7d486aee@syzkaller.appspotmail.com
Subject: Re: [PATCH v3 1/2] net: sched: act_connmark: initialize struct tc_ife to fix kernel leak
Date: Fri, 7 Nov 2025 10:38:31 +0000 [thread overview]
Message-ID: <aQ3MJ3ZPTxJqYPXT@horms.kernel.org> (raw)
In-Reply-To: <20251106195635.2438-2-vnranganath.20@gmail.com>
On Fri, Nov 07, 2025 at 01:26:33AM +0530, Ranganath V N wrote:
> In tcf_connmark_dump(), the variable 'opt' was partially initialized using a
> designatied initializer. While the padding bytes are reamined
> uninitialized. nla_put() copies the entire structure into a
> netlink message, these uninitialized bytes leaked to userspace.
>
> Initialize the structure with memset before assigning its fields
> to ensure all members and padding are cleared prior to beign copied.
>
> Signed-off-by: Ranganath V N <vnranganath.20@gmail.com>
Hi Ranganath,
Sorry for not noticing in my review of v2, but as this series fixes bugs in
code present in net it should be targeted at net. This is done by
including net in the subject of each email, like this:
Subject: [PATCh net v3 1/2] ...
And this patch should have a fixes tag (patch 2/2 already has one).
Fixes: 22a5dc0e5e3e ("net: sched: Introduce connmark action")
Also, when posting v4, please be sure to wait until 24h have
elapsed since the posting of v3.
For more information about the above please see
https://docs.kernel.org/process/maintainer-netdev.html
> ---
> net/sched/act_connmark.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/net/sched/act_connmark.c b/net/sched/act_connmark.c
> index 3e89927d7116..2aaaaee9b6bb 100644
> --- a/net/sched/act_connmark.c
> +++ b/net/sched/act_connmark.c
> @@ -195,13 +195,15 @@ static inline int tcf_connmark_dump(struct sk_buff *skb, struct tc_action *a,
> const struct tcf_connmark_info *ci = to_connmark(a);
> unsigned char *b = skb_tail_pointer(skb);
> const struct tcf_connmark_parms *parms;
> - struct tc_connmark opt = {
> - .index = ci->tcf_index,
> - .refcnt = refcount_read(&ci->tcf_refcnt) - ref,
> - .bindcnt = atomic_read(&ci->tcf_bindcnt) - bind,
> - };
> + struct tc_connmark opt;
> struct tcf_t t;
>
> + memset(&opt, 0, sizeof(opt));
> +
> + index = ci->tcf_index;
> + refcnt = refcount_read(&ci->tcf_refcnt) - ref;
> + bindcnt = atomic_read(&ci->tcf_bindcnt) - bind;
I think some editing errors have crept in here,
because the above does not compile: index should be opt.index, ...
> +
> rcu_read_lock();
> parms = rcu_dereference(ci->parms);
--
pw-bot: changes-requested
next prev parent reply other threads:[~2025-11-07 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 19:56 [PATCH v3 0/2] net: sched: initialize struct tc_ife to fix kernel-infoleak Ranganath V N
2025-11-06 19:56 ` [PATCH v3 1/2] net: sched: act_connmark: initialize struct tc_ife to fix kernel leak Ranganath V N
2025-11-07 10:38 ` Simon Horman [this message]
2025-11-08 1:26 ` kernel test robot
2025-11-06 19:56 ` [PATCH v3 2/2] net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak Ranganath V N
2025-11-08 1:15 ` kernel test robot
2025-11-08 1:26 ` kernel test robot
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=aQ3MJ3ZPTxJqYPXT@horms.kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=david.hunter.linux@gmail.com \
--cc=edumazet@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=khalid@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhan@linuxfoundation.org \
--cc=syzbot+0c85cae3350b7d486aee@syzkaller.appspotmail.com \
--cc=vnranganath.20@gmail.com \
--cc=xiyou.wangcong@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 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.