All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	linux-sctp@vger.kernel.org, marcelo.leitner@gmail.com
Subject: Re: [PATCH net] sctp: update active_key for asoc when old key is being replaced
Date: Wed, 21 Jul 2021 15:50:04 +0000	[thread overview]
Message-ID: <162688260434.19956.7821872857113679.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <a1e260329384a040f11f0f393327e25cf909da2e.1626811621.git.lucien.xin@gmail.com>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Tue, 20 Jul 2021 16:07:01 -0400 you wrote:
> syzbot reported a call trace:
> 
>   BUG: KASAN: use-after-free in sctp_auth_shkey_hold+0x22/0xa0 net/sctp/auth.c:112
>   Call Trace:
>    sctp_auth_shkey_hold+0x22/0xa0 net/sctp/auth.c:112
>    sctp_set_owner_w net/sctp/socket.c:131 [inline]
>    sctp_sendmsg_to_asoc+0x152e/0x2180 net/sctp/socket.c:1865
>    sctp_sendmsg+0x103b/0x1d30 net/sctp/socket.c:2027
>    inet_sendmsg+0x99/0xe0 net/ipv4/af_inet.c:821
>    sock_sendmsg_nosec net/socket.c:703 [inline]
>    sock_sendmsg+0xcf/0x120 net/socket.c:723
> 
> [...]

Here is the summary with links:
  - [net] sctp: update active_key for asoc when old key is being replaced
    https://git.kernel.org/netdev/net/c/58acd1009226

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2021-07-21 15:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20 20:07 [PATCH net] sctp: update active_key for asoc when old key is being replaced Xin Long
2021-07-21 15: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=162688260434.19956.7821872857113679.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --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 \
    /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.