From: patchwork-bot+netdevbpf@kernel.org
To: Ritvik Tanksalkar <ritviktanksalkar@gmail.com>
Cc: kuba@kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, horms@kernel.org, netdev@vger.kernel.org,
linux-hams@vger.kernel.org, stanksal@purdue.edu,
falwasmi@purdue.edu
Subject: Re: [PATCH net] net: rose: fix invalid array index in rose_kill_by_device()
Date: Tue, 30 Dec 2025 10:50:07 +0000 [thread overview]
Message-ID: <176709180705.3210717.17273237853991917461.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251222212227.4116041-1-ritviktanksalkar@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 22 Dec 2025 21:22:27 +0000 you wrote:
> From: Pwnverse <stanksal@purdue.edu>
>
> rose_kill_by_device() collects sockets into a local array[] and then
> iterates over them to disconnect sockets bound to a device being brought
> down.
>
> The loop mistakenly indexes array[cnt] instead of array[i]. For cnt <
> ARRAY_SIZE(array), this reads an uninitialized entry; for cnt ==
> ARRAY_SIZE(array), it is an out-of-bounds read. Either case can lead to
> an invalid socket pointer dereference and also leaks references taken
> via sock_hold().
>
> [...]
Here is the summary with links:
- [net] net: rose: fix invalid array index in rose_kill_by_device()
https://git.kernel.org/netdev/net/c/6595beb40fb0
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:[~2025-12-30 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 21:22 [PATCH net] net: rose: fix invalid array index in rose_kill_by_device() Sai Ritvik Tanksalkar
2025-12-22 21:27 ` Ritvik Tanksalkar
2025-12-30 10:50 ` 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=176709180705.3210717.17273237853991917461.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=falwasmi@purdue.edu \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ritviktanksalkar@gmail.com \
--cc=stanksal@purdue.edu \
/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;
as well as URLs for NNTP newsgroup(s).