From: Paolo Abeni <pabeni@redhat.com>
To: Hyunwoo Kim <v4bel@theori.io>,
kuniyu@amazon.com, davem@davemloft.net, edumazet@google.com
Cc: 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 v2] appletalk: Fix Use-After-Free in atalk_ioctl
Date: Tue, 12 Dec 2023 13:24:01 +0100 [thread overview]
Message-ID: <25d2081c0dd277976ff2133614bde290e3003b61.camel@redhat.com> (raw)
In-Reply-To: <20231209095552.GA406496@v4bel-B760M-AORUS-ELITE-AX>
On Sat, 2023-12-09 at 04:55 -0500, Hyunwoo Kim 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.
>
> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> Signed-off-by: Hyunwoo Kim <v4bel@theori.io>
> ---
> v1 -> v2: Change the code style
> ---
> net/appletalk/ddp.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/net/appletalk/ddp.c b/net/appletalk/ddp.c
> index 9ba04a69ec2a..016b8fb7f096 100644
> --- a/net/appletalk/ddp.c
> +++ b/net/appletalk/ddp.c
> @@ -1775,15 +1775,17 @@ static int atalk_ioctl(struct socket *sock, unsigned int cmd, unsigned long arg)
> break;
> }
> case TIOCINQ: {
> + long amount = 0;
> + struct sk_buff *skb;
Please, respect the reverse xmas tree order: no one-off exceptions even
in this period of the year (pun intended ;)
> /*
> * These two are safe on a single CPU system as only
> * user tasks fiddle here
> */
Please remove the now obsoleted comment above.
Cheers,
Paolo
prev parent reply other threads:[~2023-12-12 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-09 9:55 [PATCH v2] appletalk: Fix Use-After-Free in atalk_ioctl Hyunwoo Kim
2023-12-12 12:24 ` Paolo Abeni [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=25d2081c0dd277976ff2133614bde290e3003b61.camel@redhat.com \
--to=pabeni@redhat.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox