All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: Shigeru Yoshida <syoshida@redhat.com>,
	 john.fastabend@gmail.com,  jakub@cloudflare.com
Cc: davem@davemloft.net,  edumazet@google.com,  pabeni@redhat.com,
	 netdev@vger.kernel.org,  bpf@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	 Shigeru Yoshida <syoshida@redhat.com>,
	 syzbot+fd7b34375c1c8ce29c93@syzkaller.appspotmail.com
Subject: RE: [PATCH bpf] bpf, sockmap: Fix NULL pointer dereference in sk_psock_verdict_data_ready()
Date: Tue, 20 Feb 2024 23:18:35 -0800	[thread overview]
Message-ID: <65d5a3cbac150_5fc5920879@john.notmuch> (raw)
In-Reply-To: <20240218150933.6004-1-syoshida@redhat.com>

Shigeru Yoshida wrote:
> syzbot reported the following NULL pointer dereference issue [1]:
> 
> BUG: kernel NULL pointer dereference, address: 0000000000000000
> ...
> RIP: 0010:0x0
> ...
> Call Trace:
>  <TASK>
>  sk_psock_verdict_data_ready+0x232/0x340 net/core/skmsg.c:1230
>  unix_stream_sendmsg+0x9b4/0x1230 net/unix/af_unix.c:2293
>  sock_sendmsg_nosec net/socket.c:730 [inline]
>  __sock_sendmsg+0x221/0x270 net/socket.c:745
>  ____sys_sendmsg+0x525/0x7d0 net/socket.c:2584
>  ___sys_sendmsg net/socket.c:2638 [inline]
>  __sys_sendmsg+0x2b0/0x3a0 net/socket.c:2667
>  do_syscall_64+0xf9/0x240
>  entry_SYSCALL_64_after_hwframe+0x6f/0x77
> 
> If sk_psock_verdict_data_ready() and sk_psock_stop_verdict() are called
> concurrently, psock->saved_data_ready can be NULL, causing the above issue.
> 
> This patch fixes this issue by calling the appropriate data ready function
> using the sk_psock_data_ready() helper and protecting it from concurrency
> with sk->sk_callback_lock.
> 
> Fixes: 6df7f764cd3c ("bpf, sockmap: Wake up polling after data copy")
> Reported-and-tested-by: syzbot+fd7b34375c1c8ce29c93@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=fd7b34375c1c8ce29c93 [1]
> Signed-off-by: Shigeru Yoshida <syoshida@redhat.com>
> ---

By ensuring order of ops on teardown we should never have a loop here. Also
this aligns with strp usage that also uses sk_callback_lock. Thanks. I
suspect we haven't seen it because when this is being used we never remove
socks from the map before the socket is released.

Acked-by: John Fastabend <john.fastabend@gmail.com>

>  net/core/skmsg.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/net/core/skmsg.c b/net/core/skmsg.c
> index 93ecfceac1bc..4d75ef9d24bf 100644
> --- a/net/core/skmsg.c
> +++ b/net/core/skmsg.c
> @@ -1226,8 +1226,11 @@ static void sk_psock_verdict_data_ready(struct sock *sk)
>  
>  		rcu_read_lock();
>  		psock = sk_psock(sk);
> -		if (psock)
> -			psock->saved_data_ready(sk);
> +		if (psock) {
> +			read_lock_bh(&sk->sk_callback_lock);
> +			sk_psock_data_ready(sk, psock);
> +			read_unlock_bh(&sk->sk_callback_lock);
> +		}
>  		rcu_read_unlock();
>  	}
>  }
> -- 
> 2.43.0
> 



  reply	other threads:[~2024-02-21  7:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-18 15:09 [PATCH bpf] bpf, sockmap: Fix NULL pointer dereference in sk_psock_verdict_data_ready() Shigeru Yoshida
2024-02-21  7:18 ` John Fastabend [this message]
2024-02-21 16:20 ` patchwork-bot+netdevbpf

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=65d5a3cbac150_5fc5920879@john.notmuch \
    --to=john.fastabend@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jakub@cloudflare.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syoshida@redhat.com \
    --cc=syzbot+fd7b34375c1c8ce29c93@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 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.