From: patchwork-bot+netdevbpf@kernel.org
To: Sung Byeongchan <tjdqudcks0424@naver.com>
Cc: alex.aring@gmail.com, stefan@datenfreihafen.org,
miquel.raynal@bootlin.com, linux-wpan@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] ieee802154: require CAP_NET_ADMIN for SIOCSIFADDR
Date: Wed, 18 Nov 2026 00:00:04 +0000 [thread overview]
Message-ID: <179496000428.1359162.2050059000473015924.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261107093601.619363-1-tjdqudcks0424@naver.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 7 Nov 2026 18:36:01 +0900 you wrote:
> PF_IEEE802154 DGRAM sockets are available to ordinary init-net processes.
> Their family-specific SIOCSIFADDR path calls the netdev ioctl directly and
> does not pass through the generic network-device setter capability check.
> An unprivileged process can therefore change the PAN ID and short address
> of a separately administrator-owned down WPAN interface.
>
> In a local fakelb fixture, uid 1000 changed both identifiers and the values
> remained active through a later administrator interface open in three of
> three fresh KASAN boots.
>
> [...]
Here is the summary with links:
- ieee802154: require CAP_NET_ADMIN for SIOCSIFADDR
https://git.kernel.org/netdev/net/c/a0abc1e4c9d5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-18 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 9:36 [PATCH] ieee802154: require CAP_NET_ADMIN for SIOCSIFADDR Sung Byeongchan
2026-11-07 9:41 ` netdev-bot+sinfo
2026-11-17 9:24 ` Miquel Raynal
2026-11-18 0:00 ` patchwork-bot+netdevbpf [this message]
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=179496000428.1359162.2050059000473015924.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=stefan@datenfreihafen.org \
--cc=tjdqudcks0424@naver.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.