Netdev List
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com
Cc: linux-wpan@vger.kernel.org, alex.aring@gmail.com,
	miquel.raynal@bootlin.com, netdev@vger.kernel.org
Subject: pull-request: ieee802154-next 2026-06-20
Date: Sat, 20 Jun 2026 19:49:03 +0200	[thread overview]
Message-ID: <20260620174903.1010671-1-stefan@datenfreihafen.org> (raw)

Hello Dave, Jakub, Paolo.

An overdue pull request for ieee802154, catching up on all the AI found issues
at last.

Shitalkumar Gandhi fixed problems in the ca8210 driver for cases where we could
have a leak or a pointer truncation.

Robertus Diawan Chris made sure we do not overwrite the return code when
associating.

Michael Bommarito worked on properly gating our netlink API use in the llsec
security context.

Ivan Abramov cleaned up the netns cases as he did in other subsystems.

Doruk Tan Ozturk ensures we have the correct skn ready in cryptoo operation (to
avoid a  silent overwrite).

Aleksandr Nogikh fixed a kernel-infoleak detected by syzbot.

regards
Stefan Schmidt

The following changes since commit b85966adbf5de0668a815c6e3527f87e0c387fb4:

  Merge tag 'net-next-7.2' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next (2026-06-17 08:17:00 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/wpan/wpan-next.git tags/ieee802154-for-net-next-2026-06-20

for you to fetch changes up to a6bfdfcc6711d1d5a92e98644359dedc67c0c858:

  ieee802154: allow legacy LLSEC ADD/DEL ops to pass strict validation (2026-06-19 23:02:42 +0200)

----------------------------------------------------------------
Aleksandr Nogikh (1):
      ieee802154: fix kernel-infoleak in dgram_recvmsg()

Doruk Tan Ozturk (1):
      mac802154: llsec: add skb_cow_data() before in-place crypto

Ivan Abramov (3):
      ieee802154: Restore initial state on failed device_rename() in cfg802154_switch_netns()
      ieee802154: Avoid calling WARN_ON() on -ENOMEM in cfg802154_switch_netns()
      ieee802154: Remove WARN_ON() in cfg802154_pernet_exit()

Michael Bommarito (2):
      ieee802154: admin-gate legacy LLSEC dump operations
      ieee802154: allow legacy LLSEC ADD/DEL ops to pass strict validation

Robertus Diawan Chris (1):
      mac802154: Prevent overwrite return code in mac802154_perform_association()

Shitalkumar Gandhi (2):
      ieee802154: ca8210: fix cas_ctl leak on spi_async failure
      ieee802154: ca8210: fix pointer truncation in kfifo on 64-bit

 drivers/net/ieee802154/ca8210.c |  9 +++++---
 net/ieee802154/core.c           | 51 +++++++++++++++++++++++------------------
 net/ieee802154/header_ops.c     |  9 +++++---
 net/ieee802154/ieee802154.h     | 17 ++++++++++++++
 net/ieee802154/netlink.c        | 36 ++++++++++++++---------------
 net/mac802154/llsec.c           | 14 +++++++++++
 net/mac802154/scan.c            |  1 +
 7 files changed, 91 insertions(+), 46 deletions(-)

             reply	other threads:[~2026-06-20 17:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-20 17:49 Stefan Schmidt [this message]
2026-06-21 22:00 ` pull-request: ieee802154-next 2026-06-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=20260620174903.1010671-1-stefan@datenfreihafen.org \
    --to=stefan@datenfreihafen.org \
    --cc=alex.aring@gmail.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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