Netdev List
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Anil Kaushik <anilkaushikwireless@gmail.com>
Cc: netdev-bot+sashiko@kernel.org, pablo@netfilter.org,
	laforge@gnumonks.org, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, andrew+netdev@lunn.ch,
	nicolas.dichtel@6wind.com, osmocom-net-gprs@lists.osmocom.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3] gtp: Require 'CAP_NET_ADMIN' when joining the gtp multicast group
Date: Thu, 29 Oct 2026 13:55:28 +0000	[thread overview]
Message-ID: <20261029135528.GH257209@horms.kernel.org> (raw)
In-Reply-To: <CAG0Mgm_DxY=zZwBW3xEeNE-1LC93OWPkO4HHw=qF2Qhti-Mf4g@mail.gmail.com>

On Thu, Oct 29, 2026 at 09:49:35AM +0530, Anil Kaushik wrote:
> On Thu, Oct 29, 2026 at 9:38 AM <netdev-bot+sashiko@kernel.org> wrote:
> >
> > Thank you for your contribution! Sashiko AI review found 1 potential
> > issue(s) to consider.
> >
> > Critical: 0 · High: 1 · Medium: 0 · Low: 0
> >
> > If you believe none of the issues are legitimate, please reply to each
> > issue of Medium severity or higher and explain why the AI is wrong.
> > If any of them are legitimate and you plan to respin, please let patchwork
> > know by including "pw-bot: cr" as a separate line at the end of your reply
> > (one such reply per series is enough).
> >
> > - [High] An unprivileged local user can still receive gtp multicast
> >   notifications (PDP add/delete and echo responses) by joining the…
> >
> > --
> >
> > gtp: Require 'CAP_NET_ADMIN' when joining the gtp multicast group
> >
> > This patch marks the gtp generic netlink multicast group with
> > GENL_MCAST_CAP_NET_ADMIN in drivers/net/gtp.c and with uns-admin-perm in
> > the gtp netlink spec. The goal is to stop unprivileged users from
> > receiving the PDP context add/delete and echo response notifications,
> > which carry the same data as a GETPDP reply.
> >
> 
> Yes, this works, but the gap is in the genetlink core, not in gtp.
> genl_unregister_mc_groups() clears the members of the IDs it frees, but
> nothing clears them when free IDs are given to a new family. So it hits
> every modular group with a GENL_MCAST_CAP_* flag, psample and
> drop_monitor too.
> 
> This patch is still needed, and it does not change. I will send a
> separate fix to net that clears the members of the new IDs in
> genl_validate_assign_mc_groups(), like the unregister path does.

Thanks Anil,

One step at a time seems like a good approach to me.

Reviewed-by: Simon Horman <horms@kernel.org>


  reply	other threads:[~2026-10-29 13:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 13:06 [PATCH net v3] gtp: Require 'CAP_NET_ADMIN' when joining the gtp multicast group Anil Kaushik
2026-10-29  4:08 ` netdev-bot+sashiko
2026-10-29  4:19   ` Anil Kaushik
2026-10-29 13:55     ` Simon Horman [this message]
2026-10-29  4:22 ` Anil Kaushik
2026-10-29 14:20 ` 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=20261029135528.GH257209@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=anilkaushikwireless@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=kuba@kernel.org \
    --cc=laforge@gnumonks.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev-bot+sashiko@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=osmocom-net-gprs@lists.osmocom.org \
    --cc=pabeni@redhat.com \
    --cc=pablo@netfilter.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