Thread (1 message) 1 message, 1 author, 2021-05-05

Re: [PATCH] net/nfc: fix use-after-free llcp_sock_bind/connect

From: Leon Romanovsky <leon@kernel.org>
Date: 2021-05-05 11:40:00
Subsystem: networking [general], nfc subsystem, the rest · Maintainers: "David S. Miller", Eric Dumazet, Jakub Kicinski, Paolo Abeni, David Heidelberg, Linus Torvalds

Possibly related (same subject, not in this thread)

On Wed, May 05, 2021 at 12:35:48PM +0300, Nadav Markus wrote:
On Wed, May 5, 2021 at 7:46 AM Leon Romanovsky [off-list ref] wrote:
quoted
On Tue, May 04, 2021 at 07:01:01PM +0300, Or Cohen wrote:
quoted
Hi, can you please elaborate?

We don't understand why using kref_get_unless_zero will solve the
problem.

Please don't reply in top-posting format.
------

The rationale behind _put()/_get() wrappers over kref is to allow
delayed release after all consumers are gone.

In order to make it happen, the developer should ensure that consumers
don't have an access to the kref-ed struct. This is done with
kref_get_unless_zero().

In your case, you simply increment some counter without checking if
nfc_llcp_local_get() actually succeeded.
Hi Leon - as far as we understand, the underlying issue is not incrementing
the kref counter without checking if the function nfc_llcp_local_get
succeeded or not. The function itself increments the reference count.

The issue is that the nfc_llcp_local_put might be called twice on the
llcp_sock->local field, however only one reference (the one that was gotten
via nfc_llcp_local_get) is incremented. llcp_local_put will be called in
two locations. The first one is just inside the bind function, if
nfc_llcp_get_local_ssap fails. The second one is called unconditionally, at
the socket destruction, at the function nfc_llcp_sock_free.

Hence, our proposed solution is to prevent the second nfc_llcp_local_put
from attempting to decrement the kref count, by setting local to NULL. This
makes sense, as we immediately do so after decrementing the single ref
count we took when calling nfc_llcp_local_get. Since we are under the sock
lock, this also should be race safe, as no one should access the
llcp_sock->local field without this lock's protection.
quoted
For example, what protection do you have from races between
llcp_sock_bind(),
nfc_llcp_sock_free() and llcp_sock_connect()?
As we replied, the llcp_sock->local field is protected under the lock sock,
as far as we understand.
quoted
So in case you have some lock outside, it is unclear how use-after-free
is possible, because nfc_llcp_find_local() should return NULL.
In case, no lock exists, except reducing race window, you didn't fix
anything
and didn't sanitize lcp_sock too.
We don't quite get what race are we talking about here - our trigger
program doesn't even utilize threads. All it has to do is to
cause nfc_llcp_local_get to fail - this can be seen clearly in our original
trigger program. To clarify, the two sockets that are created there point
to the same nfc_llcp_local struct (via their local field). The destruction
of the first socket causes the reference count of the pointed object to
drop to zero (since the code increments the ref count of the object from 1
to 2, but dercements it twice). The second socket later attempts to
decrement the ref count of the same (already freed) nfc_llcp_local object,
causing a kernel crash.

So at the end, we are talking about situation where _get()/_put() are
protected by the lock and local can't disappear. Can you please help me to find
this socket lock? Did I miss it in bind path?

net/socket.c:
  int __sys_bind(int fd, struct sockaddr __user *umyaddr, int addrlen)
    sock->ops->bind(..)
     llcp_sock_bind(..)

And if we put lock issue aside, all your change can be squeezed to the following:
diff --git a/net/nfc/llcp_sock.c b/net/nfc/llcp_sock.c
index a3b46f888803..cc9ee634269d 100644
--- a/net/nfc/llcp_sock.c
+++ b/net/nfc/llcp_sock.c
@@ -99,7 +99,6 @@ static int llcp_sock_bind(struct socket *sock, struct sockaddr *addr, int alen)
        }

        llcp_sock->dev = dev;
-       llcp_sock->local = nfc_llcp_local_get(local);
        llcp_sock->nfc_protocol = llcp_addr.nfc_protocol;
        llcp_sock->service_name_len = min_t(unsigned int,
                                            llcp_addr.service_name_len,
@@ -108,13 +107,11 @@ static int llcp_sock_bind(struct socket *sock, struct sockaddr *addr, int alen)
                                          llcp_sock->service_name_len,
                                          GFP_KERNEL);
        if (!llcp_sock->service_name) {
-               nfc_llcp_local_put(llcp_sock->local);
                ret = -ENOMEM;
                goto put_dev;
        }
        llcp_sock->ssap = nfc_llcp_get_sdp_ssap(local, llcp_sock);
        if (llcp_sock->ssap == LLCP_SAP_MAX) {
-               nfc_llcp_local_put(llcp_sock->local);
                kfree(llcp_sock->service_name);
                llcp_sock->service_name = NULL;
                ret = -EADDRINUSE;
@@ -122,6 +119,7 @@ static int llcp_sock_bind(struct socket *sock, struct sockaddr *addr, int alen)
        }

        llcp_sock->reserved_ssap = llcp_sock->ssap;
+       llcp_sock->local = nfc_llcp_local_get(local);

        nfc_llcp_sock_link(&local->sockets, sk);

Thanks
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help