From: patchwork-bot+netdevbpf@kernel.org
To: Alexey Simakov <bigalex934@gmail.com>
Cc: marcelo.leitner@gmail.com, lucien.xin@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, linux-sctp@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH] sctp: fix null derefer in sctp_sf_do_5_1D_ce()
Date: Fri, 10 Oct 2025 08:37:32 +0000 [thread overview]
Message-ID: <176008545226.469542.15958145151013253820.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251009173248.11881-1-bigalex934@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 9 Oct 2025 20:32:49 +0300 you wrote:
> The check of new_asoc->peer.adaptation_ind can fail,
> leaving ai_ev unitilialized. In that case, the code
> can jump to the nomem_authdev label and later call
> sctp_ulpevent_free() with a null ai_ev pointer.
> Leading to potential null dereference.
>
> Add check of ai_ev pointer before call of
> sctp_ulpevent_free function.
>
> [...]
Here is the summary with links:
- sctp: fix null derefer in sctp_sf_do_5_1D_ce()
https://git.kernel.org/netdev/net-next/c/2f3119686ef5
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-10-10 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 17:32 [PATCH] sctp: fix null derefer in sctp_sf_do_5_1D_ce() Alexey Simakov
2025-10-10 8:37 ` 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=176008545226.469542.15958145151013253820.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bigalex934@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=lvc-project@linuxtesting.org \
--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;
as well as URLs for NNTP newsgroup(s).