From: Johannes Berg <johannes@sipsolutions.net>
To: Michael Bommarito <michael.bommarito@gmail.com>,
linux-wireless@vger.kernel.org
Cc: Avraham Stern <avraham.stern@intel.com>,
Arend van Spriel <arend.vanspriel@broadcom.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: nl80211: require admin perm on SET_PMK / DEL_PMK
Date: Wed, 22 Apr 2026 08:23:19 +0200 [thread overview]
Message-ID: <e4b3f365a32b633babcd4cefde3fc32460e07e0d.camel@sipsolutions.net> (raw)
In-Reply-To: <20260421224552.4044147-1-michael.bommarito@gmail.com> (sfid-20260422_004558_248010_38F9E184)
On Tue, 2026-04-21 at 18:45 -0400, Michael Bommarito wrote:
>
> Both ops were introduced without a .flags gate, so the generic
> netlink layer dispatches them to an unprivileged caller instead
> of rejecting with -EPERM at the permission check. Every other
> connection-state op in the adjacent block (CONNECT, ASSOCIATE,
> AUTHENTICATE, SET_KEY, ...) carries GENL_UNS_ADMIN_PERM; SET_PMK
> / DEL_PMK were introduced without the flag in 2017 and left
> unchanged by later refactors. Johannes checked the original
> Intel submission history and confirmed there is no admin check
> in any prior revision either, so this seems likely to be a
> simple oversight rather than an intentional carve-out.
FWIW, this submission did originally come from Avi, but we no longer
have a driver using it (it was never upstream anyway), so that now the
only affected driver is brcmfmac, AFAICT (other non-upstream drivers I
wouldn't know, of course.)
Arend, it does seem like the right thing to do here, but I wanted to
confirm with you and thus asked Michael to CC you, what do you think?
johannes
next prev parent reply other threads:[~2026-04-22 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 22:45 [PATCH] wifi: nl80211: require admin perm on SET_PMK / DEL_PMK Michael Bommarito
2026-04-22 6:23 ` Johannes Berg [this message]
2026-04-22 8:42 ` Arend van Spriel
2026-04-22 8:32 ` Arend van Spriel
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=e4b3f365a32b633babcd4cefde3fc32460e07e0d.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--cc=avraham.stern@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michael.bommarito@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