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,
	jmaloy@redhat.com, tipc-discussion@lists.sourceforge.net,
	hoang.h.le@dektech.com.au
Subject: Re: [PATCH net-next] tipc: fix an use-after-free issue in tipc_recvmsg
Date: Sun, 25 Jul 2021 09:50:04 +0000	[thread overview]
Message-ID: <162720660482.12734.3061304983506878022.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <a60f2c4e9eb8cce9da01c5bd561684011f7fa7da.1627061136.git.lucien.xin@gmail.com>

Hello:

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

On Fri, 23 Jul 2021 13:25:36 -0400 you wrote:
> syzbot reported an use-after-free crash:
> 
>   BUG: KASAN: use-after-free in tipc_recvmsg+0xf77/0xf90 net/tipc/socket.c:1979
>   Call Trace:
>    tipc_recvmsg+0xf77/0xf90 net/tipc/socket.c:1979
>    sock_recvmsg_nosec net/socket.c:943 [inline]
>    sock_recvmsg net/socket.c:961 [inline]
>    sock_recvmsg+0xca/0x110 net/socket.c:957
>    tipc_conn_rcv_from_sock+0x162/0x2f0 net/tipc/topsrv.c:398
>    tipc_conn_recv_work+0xeb/0x190 net/tipc/topsrv.c:421
>    process_one_work+0x98d/0x1630 kernel/workqueue.c:2276
>    worker_thread+0x658/0x11f0 kernel/workqueue.c:2422
> 
> [...]

Here is the summary with links:
  - [net-next] tipc: fix an use-after-free issue in tipc_recvmsg
    https://git.kernel.org/netdev/net-next/c/cc19862ffe45

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-25  9:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23 17:25 [PATCH net-next] tipc: fix an use-after-free issue in tipc_recvmsg Xin Long
2021-07-25  9: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=162720660482.12734.3061304983506878022.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=hoang.h.le@dektech.com.au \
    --cc=jmaloy@redhat.com \
    --cc=kuba@kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    /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.