From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, horms@kernel.org, marcelo.leitner@gmail.com,
bgeffon@google.com
Subject: Re: [PATCH net] sctp: validate cached peer INIT chunk length in COOKIE_ECHO processing
Date: Thu, 04 Jun 2026 15:40:12 +0000 [thread overview]
Message-ID: <178058761264.2484354.11440643164708781484.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <eb60825fa22d6f9e663c7d4dbb69f397b5d34d42.1780362366.git.lucien.xin@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 1 Jun 2026 21:06:06 -0400 you wrote:
> When a listening SCTP server processes a COOKIE_ECHO chunk, the cached
> peer INIT chunk embedded after the cookie is parsed and its parameters
> are later walked by sctp_process_init() using sctp_walk_params().
>
> However, the chunk header length of this cached INIT chunk was not
> validated against the remaining buffer in the COOKIE_ECHO payload. If
> the length field is inflated, the parameter walk can run beyond the
> actual received data, leading to out-of-bounds reads and potential
> memory corruption during later parameter handling (e.g. STATE_COOKIE
> processing and kmemdup() copies).
>
> [...]
Here is the summary with links:
- [net] sctp: validate cached peer INIT chunk length in COOKIE_ECHO processing
https://git.kernel.org/netdev/net/c/0861615c28de
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-06-04 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 1:06 [PATCH net] sctp: validate cached peer INIT chunk length in COOKIE_ECHO processing Xin Long
2026-06-04 10:47 ` Simon Horman
2026-06-04 15:40 ` 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=178058761264.2484354.11440643164708781484.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bgeffon@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=marcelo.leitner@gmail.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