From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <v4bel@theori.io>
Cc: <davem@davemloft.net>, <dhowells@redhat.com>,
<edumazet@google.com>, <horms@kernel.org>, <imv4bel@gmail.com>,
<kuba@kernel.org>, <lukas.bulwahn@gmail.com>,
<mkl@pengutronix.de>, <netdev@vger.kernel.org>,
<pabeni@redhat.com>, <kuniyu@amazon.com>
Subject: Re: [PATCH] appletalk: Fix Use-After-Free in atalk_ioctl
Date: Thu, 7 Dec 2023 15:42:44 +0900 [thread overview]
Message-ID: <20231207064244.22412-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20231206120923.GA14115@ubuntu>
From: Hyunwoo Kim <v4bel@theori.io>
Date: Wed, 6 Dec 2023 04:09:23 -0800
> 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>
> ---
> net/appletalk/ddp.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/net/appletalk/ddp.c b/net/appletalk/ddp.c
> index 9ba04a69ec2a..f240d5338bc9 100644
> --- a/net/appletalk/ddp.c
> +++ b/net/appletalk/ddp.c
> @@ -1775,15 +1775,16 @@ static int atalk_ioctl(struct socket *sock, unsigned int cmd, unsigned long arg)
> break;
> }
> case TIOCINQ: {
> + long amount = 0;
> /*
> * These two are safe on a single CPU system as only
> * user tasks fiddle here
> */
> + spin_lock_irq(&sk->sk_receive_queue.lock);
nit: please call spin_lock() after declaring all variables; otherwise
checkpatch.pl will complain.
> struct sk_buff *skb = skb_peek(&sk->sk_receive_queue);
> - long amount = 0;
Also, please keep the reverse xmas tree.
> -
> if (skb)
> amount = skb->len - sizeof(struct ddpehdr);
> + spin_unlock_irq(&sk->sk_receive_queue.lock);
> rc = put_user(amount, (int __user *)argp);
> break;
> }
> --
> 2.25.1
>
prev parent reply other threads:[~2023-12-07 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 12:09 [PATCH] appletalk: Fix Use-After-Free in atalk_ioctl Hyunwoo Kim
2023-12-07 6:42 ` Kuniyuki Iwashima [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=20231207064244.22412-1-kuniyu@amazon.com \
--to=kuniyu@amazon.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=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 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 NNTP newsgroup(s).