From: patchwork-bot+netdevbpf@kernel.org
To: henry martin <bsdhenrymartin@gmail.com>
Cc: edumazet@kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, nicolas.dichtel@6wind.com,
kees@kernel.org, i.maximets@ovn.org, leitao@debian.org,
jlayton@kernel.org, kexinsun@smail.nju.edu.cn,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v4] netlink: fix out-of-bounds bitmap access clearing stale mc groups
Date: Mon, 26 Oct 2026 08:20:05 +0000 [thread overview]
Message-ID: <179300280507.2542292.1871399042278528060.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261026030928.719276-1-bsdhenrymartin@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Dave Miller <davem@davem-thinkpadp1gen8.ibmlond.csb>:
On Mon, 26 Oct 2026 11:09:28 +0800 you wrote:
> netlink_realloc_groups() sizes nlk->groups to the number of groups
> that exist at bind/ADD_MEMBERSHIP time. When more multicast groups
> are registered later (e.g. a new genl family), existing sockets keep
> their smaller bitmap.
>
> When clearing a multicast group of a departing family,
> __netlink_clear_multicast_users() runs netlink_update_socket_mc() on
> each socket on mc_list, which does test_bit()/__assign_bit() on
> group - 1 with no regard to nlk->ngroups. Skip sockets whose bitmap
> predates the group: such a socket can never have joined it.
>
> [...]
Here is the summary with links:
- [net,v4] netlink: fix out-of-bounds bitmap access clearing stale mc groups
https://git.kernel.org/netdev/net/c/6430fb7f1cc4
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-10-26 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 3:09 [PATCH net v4] netlink: fix out-of-bounds bitmap access clearing stale mc groups Henry Martin
2026-10-26 3:16 ` netdev-bot+sinfo
2026-10-26 8:20 ` 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=179300280507.2542292.1871399042278528060.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bsdhenrymartin@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=jlayton@kernel.org \
--cc=kees@kernel.org \
--cc=kexinsun@smail.nju.edu.cn \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--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 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.