All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hyunwoo Kim <v4bel@theori.io>
Cc: pabeni@redhat.com, davem@davemloft.net, edumazet@google.com,
	kuniyu@amazon.com, imv4bel@gmail.com, kuba@kernel.org,
	horms@kernel.org, dhowells@redhat.com, lukas.bulwahn@gmail.com,
	mkl@pengutronix.de, netdev@vger.kernel.org
Subject: Re: [PATCH v3] appletalk: Fix Use-After-Free in atalk_ioctl
Date: Thu, 14 Dec 2023 11:10:25 +0000	[thread overview]
Message-ID: <170255222524.10804.9204019996221133985.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231213041056.GA519680@v4bel-B760M-AORUS-ELITE-AX>

Hello:

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

On Tue, 12 Dec 2023 23:10:56 -0500 you wrote:
> Because atalk_ioctl() accesses sk->sk_receive_queue
> without holding a sk->sk_receive_queue.lock, it can
> cause a race with atalk_recvmsg().
> A use-after-free for skb occurs with the following flow.
> ```
> atalk_ioctl() -> skb_peek()
> atalk_recvmsg() -> skb_recv_datagram() -> skb_free_datagram()
> ```
> Add sk->sk_receive_queue.lock to atalk_ioctl() to fix this issue.
> 
> [...]

Here is the summary with links:
  - [v3] appletalk: Fix Use-After-Free in atalk_ioctl
    https://git.kernel.org/netdev/net/c/189ff16722ee

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



      reply	other threads:[~2023-12-14 11:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13  4:10 [PATCH v3] appletalk: Fix Use-After-Free in atalk_ioctl Hyunwoo Kim
2023-12-14 11:10 ` 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=170255222524.10804.9204019996221133985.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=imv4bel@gmail.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@amazon.com \
    --cc=lukas.bulwahn@gmail.com \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=v4bel@theori.io \
    /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.