From: Yonghong Song <yonghong.song@linux.dev>
To: Cong Wang <xiyou.wangcong@gmail.com>, netdev@vger.kernel.org
Cc: bpf@vger.kernel.org, Cong Wang <cong.wang@bytedance.com>,
Ruan Bonan <bonan.ruan@u.nus.edu>,
John Fastabend <john.fastabend@gmail.com>,
Jakub Sitnicki <jakub@cloudflare.com>
Subject: Re: [Patch bpf] sock_map: fix a NULL pointer dereference in sock_map_link_update_prog()
Date: Sun, 27 Oct 2024 22:58:55 -0700 [thread overview]
Message-ID: <9117f014-3ad3-4d9a-9357-4b57d376c660@linux.dev> (raw)
In-Reply-To: <20241026185522.338562-1-xiyou.wangcong@gmail.com>
On 10/26/24 11:55 AM, Cong Wang wrote:
> From: Cong Wang <cong.wang@bytedance.com>
>
> The following race condition could trigger a NULL pointer dereference:
>
> sock_map_link_detach(): sock_map_link_update_prog():
> mutex_lock(&sockmap_mutex);
> ...
> sockmap_link->map = NULL;
> mutex_unlock(&sockmap_mutex);
> mutex_lock(&sockmap_mutex);
> ...
> sock_map_prog_link_lookup(sockmap_link->map);
> mutex_unlock(&sockmap_mutex);
> <continue>
>
> Fix it by adding a NULL pointer check. In this specific case, it makes
> no sense to update a link which is being released.
>
> Reported-by: Ruan Bonan <bonan.ruan@u.nus.edu>
> Fixes: 699c23f02c65 ("bpf: Add bpf_link support for sk_msg and sk_skb progs")
> Cc: Yonghong Song <yonghong.song@linux.dev>
> Cc: John Fastabend <john.fastabend@gmail.com>
> Cc: Jakub Sitnicki <jakub@cloudflare.com>
> Signed-off-by: Cong Wang <cong.wang@bytedance.com>
> ---
> net/core/sock_map.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/net/core/sock_map.c b/net/core/sock_map.c
> index 07d6aa4e39ef..9fca4db52f57 100644
> --- a/net/core/sock_map.c
> +++ b/net/core/sock_map.c
> @@ -1760,6 +1760,10 @@ static int sock_map_link_update_prog(struct bpf_link *link,
> ret = -EINVAL;
> goto out;
> }
> + if (!sockmap_link->map) {
> + ret = -EINVAL;
Thanks for the fix. Maybe we should use -ENOENT as the return error code?
In this case, update_prog failed due to sockmap_link->map == NULL which is
equivalent to no 'entry' to update.
> + goto out;
> + }
>
> ret = sock_map_prog_link_lookup(sockmap_link->map, &pprog, &plink,
> sockmap_link->attach_type);
next prev parent reply other threads:[~2024-10-28 5:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 18:55 [Patch bpf] sock_map: fix a NULL pointer dereference in sock_map_link_update_prog() Cong Wang
2024-10-28 5:58 ` Yonghong Song [this message]
2024-10-29 1:57 ` Martin KaFai Lau
2024-10-29 2:00 ` 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=9117f014-3ad3-4d9a-9357-4b57d376c660@linux.dev \
--to=yonghong.song@linux.dev \
--cc=bonan.ruan@u.nus.edu \
--cc=bpf@vger.kernel.org \
--cc=cong.wang@bytedance.com \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox