From: Vitaly Chikunov <vt@altlinux.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Cc: Ranganath V N <vnranganath.20@gmail.com>,
linux-rt-devel@lists.linux.dev, edumazet@google.com,
davem@davemloft.net, david.hunter.linux@gmail.com,
horms@kernel.org, jiri@resnulli.us, khalid@kernel.org,
kuba@kernel.org, pabeni@redhat.com, xiyou.wangcong@gmail.com,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
skhan@linuxfoundation.org
Subject: Re: [PATCH net v4 2/2] net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak
Date: Mon, 15 Dec 2025 00:38:16 +0300 [thread overview]
Message-ID: <3kwhg36anlckq57bez25aimvyj@altlinux.org> (raw)
In-Reply-To: <CAM0EoMneOSX=AMe53hQibY=O6n=KYnudAWfVtUdOf8qc_Bmw+Q@mail.gmail.com>
Jamal, and linux-rt-devel,
On Fri, Dec 12, 2025 at 11:29:24AM -0500, Jamal Hadi Salim wrote:
> On Fri, Dec 12, 2025 at 11:26 AM Jamal Hadi Salim <jhs@mojatatu.com> wrote:
> >
> > On Thu, Dec 11, 2025 at 7:54 PM Vitaly Chikunov <vt@altlinux.org> wrote:
> > >
> > > On Sun, Nov 09, 2025 at 02:43:36PM +0530, Ranganath V N wrote:
> > > > Fix a KMSAN kernel-infoleak detected by the syzbot .
> > > >
> > > > [net?] KMSAN: kernel-infoleak in __skb_datagram_iter
> > > >
> > > > In tcf_ife_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.
> > > >
> > > > This change silences the KMSAN report and prevents potential information
> > > > leaks from the kernel memory.
> > > >
> > > > This fix has been tested and validated by syzbot. This patch closes the
> > > > bug reported at the following syzkaller link and ensures no infoleak.
> > > >
> > > > Reported-by: syzbot+0c85cae3350b7d486aee@syzkaller.appspotmail.com
> > > > Closes: https://syzkaller.appspot.com/bug?extid=0c85cae3350b7d486aee
> > > > Tested-by: syzbot+0c85cae3350b7d486aee@syzkaller.appspotmail.com
> > > > Fixes: ef6980b6becb ("introduce IFE action")
> > > > Signed-off-by: Ranganath V N <vnranganath.20@gmail.com>
> > > > ---
> > > > net/sched/act_ife.c | 12 +++++++-----
> > > > 1 file changed, 7 insertions(+), 5 deletions(-)
> > > >
> > > > diff --git a/net/sched/act_ife.c b/net/sched/act_ife.c
> > > > index 107c6d83dc5c..7c6975632fc2 100644
> > > > --- a/net/sched/act_ife.c
> > > > +++ b/net/sched/act_ife.c
> > > > @@ -644,13 +644,15 @@ static int tcf_ife_dump(struct sk_buff *skb, struct tc_action *a, int bind,
> > > > unsigned char *b = skb_tail_pointer(skb);
> > > > struct tcf_ife_info *ife = to_ife(a);
> > > > struct tcf_ife_params *p;
> > > > - struct tc_ife opt = {
> > > > - .index = ife->tcf_index,
> > > > - .refcnt = refcount_read(&ife->tcf_refcnt) - ref,
> > > > - .bindcnt = atomic_read(&ife->tcf_bindcnt) - bind,
> > > > - };
> > > > + struct tc_ife opt;
> > > > struct tcf_t t;
> > > >
> > > > + memset(&opt, 0, sizeof(opt));
> > > > +
> > > > + opt.index = ife->tcf_index,
> > > > + opt.refcnt = refcount_read(&ife->tcf_refcnt) - ref,
> > > > + opt.bindcnt = atomic_read(&ife->tcf_bindcnt) - bind,
> > >
> > > Are you sure this is correct to delimit with commas instead of
> > > semicolons?
> > >
> > > This already causes build failures of 5.10.247-rt141 kernel, because
> > > their spin_lock_bh unrolls into do { .. } while (0):
> > >
> >
> > Do you have access to this?
> > commit 205305c028ad986d0649b8b100bab6032dcd1bb5
> > Author: Chen Ni <nichen@iscas.ac.cn>
> > Date: Wed Nov 12 15:27:09 2025 +0800
> >
> > net/sched: act_ife: convert comma to semicolon
> >
>
> Sigh. I see the problem: that patch did not have a Fixes tag;
> otherwise, it would have been backported.
Thanks! I will pick this for the local builds. But, perhaps, someone
should send it to stable@kernel.org to fix the older -rt kernels too.
Thanks,
>
> cheers,
> jamal
next prev parent reply other threads:[~2025-12-14 21:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 9:13 [PATCH v4 net 0/2] net: sched: initialize struct tc_ife to fix kernel-infoleak Ranganath V N
2025-11-09 9:13 ` [PATCH net v4 1/2] net: sched: act_connmark: initialize struct tc_ife to fix kernel leak Ranganath V N
2025-11-09 9:30 ` Eric Dumazet
2025-11-09 9:13 ` [PATCH net v4 2/2] net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak Ranganath V N
2025-11-09 9:31 ` Eric Dumazet
2025-12-12 0:54 ` Vitaly Chikunov
2025-12-12 16:26 ` Jamal Hadi Salim
2025-12-12 16:29 ` Jamal Hadi Salim
2025-12-14 21:38 ` Vitaly Chikunov [this message]
2025-12-15 16:27 ` Jamal Hadi Salim
2025-11-10 20:02 ` [PATCH v4 net 0/2] net: sched: initialize struct tc_ife to fix kernel-infoleak Cong Wang
2025-11-11 14:10 ` patchwork-bot+netdevbpf
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=3kwhg36anlckq57bez25aimvyj@altlinux.org \
--to=vt@altlinux.org \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=davem@davemloft.net \
--cc=david.hunter.linux@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=khalid@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rostedt@goodmis.org \
--cc=skhan@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox