linux-hams.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: ralf@linux-mips.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, phind.uet@gmail.com,
	kuni1840@gmail.com, netdev@vger.kernel.org,
	linux-hams@vger.kernel.org,
	syzbot+5fafd5cfe1fc91f6b352@syzkaller.appspotmail.com
Subject: Re: [PATCH v1 net] netrom: Fix use-after-free of a listening socket.
Date: Tue, 24 Jan 2023 11:30:16 +0000	[thread overview]
Message-ID: <167455981697.20043.16136032100144497483.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230120231927.51711-1-kuniyu@amazon.com>

Hello:

This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:

On Fri, 20 Jan 2023 15:19:27 -0800 you wrote:
> syzbot reported a use-after-free in do_accept(), precisely nr_accept()
> as sk_prot_alloc() allocated the memory and sock_put() frees it. [0]
> 
> The issue could happen if the heartbeat timer is fired and
> nr_heartbeat_expiry() calls nr_destroy_socket(), where a socket
> has SOCK_DESTROY or a listening socket has SOCK_DEAD.
> 
> [...]

Here is the summary with links:
  - [v1,net] netrom: Fix use-after-free of a listening socket.
    https://git.kernel.org/netdev/net/c/409db27e3a2e

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



      reply	other threads:[~2023-01-24 11:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 23:19 [PATCH v1 net] netrom: Fix use-after-free of a listening socket Kuniyuki Iwashima
2023-01-24 11:30 ` 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=167455981697.20043.16136032100144497483.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@amazon.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=phind.uet@gmail.com \
    --cc=ralf@linux-mips.org \
    --cc=syzbot+5fafd5cfe1fc91f6b352@syzkaller.appspotmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).