public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Duoming Zhou <duoming@zju.edu.cn>
Cc: linux-hams@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, kuba@kernel.org,
	davem@davemloft.net, ralf@linux-mips.org, jreuter@yaina.de
Subject: Re: [PATCH] ax25: Fix NULL pointer dereference in ax25_kill_by_device
Date: Wed, 09 Mar 2022 12:50:10 +0000	[thread overview]
Message-ID: <164683021074.2371.639793018206811147.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220308081223.15919-1-duoming@zju.edu.cn>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Tue,  8 Mar 2022 16:12:23 +0800 you wrote:
> When two ax25 devices attempted to establish connection, the requester use ax25_create(),
> ax25_bind() and ax25_connect() to initiate connection. The receiver use ax25_rcv() to
> accept connection and use ax25_create_cb() in ax25_rcv() to create ax25_cb, but the
> ax25_cb->sk is NULL. When the receiver is detaching, a NULL pointer dereference bug
> caused by sock_hold(sk) in ax25_kill_by_device() will happen. The corresponding
> fail log is shown below:
> 
> [...]

Here is the summary with links:
  - ax25: Fix NULL pointer dereference in ax25_kill_by_device
    https://git.kernel.org/netdev/net/c/71171ac8eb34

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



      reply	other threads:[~2022-03-09 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-08  8:12 [PATCH] ax25: Fix NULL pointer dereference in ax25_kill_by_device Duoming Zhou
2022-03-09 12: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=164683021074.2371.639793018206811147.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=duoming@zju.edu.cn \
    --cc=jreuter@yaina.de \
    --cc=kuba@kernel.org \
    --cc=linux-hams@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox