From: Vlad Efanov <vefanov@ispras.ru>
To: Eric Dumazet <edumazet@google.com>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH] udp6: Fix race condition in udp6_sendmsg & connect
Date: Fri, 26 May 2023 19:57:47 +0300 [thread overview]
Message-ID: <e058a2e7-707c-a66d-b1b2-ac3086f77ec0@ispras.ru> (raw)
In-Reply-To: <CANn89iJkOOcombRniD7PP4KY=5Z6tx5QMQ-M24KS_AZ0h4nAcg@mail.gmail.com>
Yes.
There is no lock for this lines and my patch does not broken this logic.
I sugessted to set lock only for lines 1566-1571
(ip6_sk_dst_lookup_flow() call).
Best regards,
Vlad.
On 26.05.2023 19:46, Eric Dumazet wrote:
> On Fri, May 26, 2023 at 6:09 PM Vlad Efanov <vefanov@ispras.ru> wrote:
>> Eric,
>>
>>
>> udp6_sendmsg() currently still locks the socket (on line 1595).
>>
> Not really, look more closely at lines 1580 -> 1594
>
>
>> Best regards,
>>
>> Vlad.
>>
>>
>> On 26.05.2023 18:29, Eric Dumazet wrote:
>>> On Fri, May 26, 2023 at 5:08 PM Vladislav Efanov <VEfanov@ispras.ru> wrote:
>>>> Syzkaller got the following report:
>>>> BUG: KASAN: use-after-free in sk_setup_caps+0x621/0x690 net/core/sock.c:2018
>>>> Read of size 8 at addr ffff888027f82780 by task syz-executor276/3255
>>> Please include a full report.
>>>
>>>> The function sk_setup_caps (called by ip6_sk_dst_store_flow->
>>>> ip6_dst_store) referenced already freed memory as this memory was
>>>> freed by parallel task in udpv6_sendmsg->ip6_sk_dst_lookup_flow->
>>>> sk_dst_check.
>>>>
>>>> task1 (connect) task2 (udp6_sendmsg)
>>>> sk_setup_caps->sk_dst_set |
>>>> | sk_dst_check->
>>>> | sk_dst_set
>>>> | dst_release
>>>> sk_setup_caps references |
>>>> to already freed dst_entry|
>>>> The reason for this race condition is: udp6_sendmsg() calls
>>>> ip6_sk_dst_lookup() without lock for sock structure and tries to
>>>> allocate/add dst_entry structure to sock structure in parallel with
>>>> "connect" task.
>>>>
>>>> Found by Linux Verification Center (linuxtesting.org) with syzkaller.
>>>>
>>>> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
>>> This is a bogus Fixes: tag
>>>
>>> In old times, UDP sendmsg() was using the socket lock.
>>>
>>> Then, in linux-4.0 Vlad Yasevich made UDP v6 sendmsg() lockless (and
>>> racy in many points)
>>>
>>>
>>>> Signed-off-by: Vladislav Efanov <VEfanov@ispras.ru>
>>>> ---
>>>> net/ipv6/udp.c | 3 +++
>>>> 1 file changed, 3 insertions(+)
>>>>
>>>> diff --git a/net/ipv6/udp.c b/net/ipv6/udp.c
>>>> index e5a337e6b970..a5ecd5d93b0a 100644
>>>> --- a/net/ipv6/udp.c
>>>> +++ b/net/ipv6/udp.c
>>>> @@ -1563,12 +1563,15 @@ int udpv6_sendmsg(struct sock *sk, struct msghdr *msg, size_t len)
>>>>
>>>> fl6->flowlabel = ip6_make_flowinfo(ipc6.tclass, fl6->flowlabel);
>>>>
>>>> + lock_sock(sk);
>>>> dst = ip6_sk_dst_lookup_flow(sk, fl6, final_p, connected);
>>>> if (IS_ERR(dst)) {
>>>> err = PTR_ERR(dst);
>>>> dst = NULL;
>>>> + release_sock(sk);
>>>> goto out;
>>>> }
>>>> + release_sock(sk);
>>>>
>>>> if (ipc6.hlimit < 0)
>>>> ipc6.hlimit = ip6_sk_dst_hoplimit(np, fl6, dst);
>>>> --
>>>> 2.34.1
>>>>
>>> There must be another way really.
>>> You just killed UDP performance.
next prev parent reply other threads:[~2023-05-26 16:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 15:08 Vladislav Efanov
2023-05-26 15:29 ` Eric Dumazet
2023-05-26 15:49 ` Ефанов Владислав Александрович
2023-05-26 16:09 ` Vlad Efanov
2023-05-26 16:46 ` Eric Dumazet
2023-05-26 16:57 ` Vlad Efanov [this message]
2023-05-26 15:33 ` Paolo Abeni
2023-05-26 15:58 ` Ефанов Владислав Александрович
2023-05-26 16:00 ` Eric Dumazet
2023-05-26 16:41 ` Vlad Efanov
2023-05-26 16:47 ` Eric Dumazet
2023-05-26 17:00 ` Vlad Efanov
2023-05-26 18:13 ` Paolo Abeni
2023-05-29 14:13 ` Vlad Efanov
2023-05-30 11:39 ` [PATCH v2] " Vladislav Efanov
2023-05-31 9:40 ` 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=e058a2e7-707c-a66d-b1b2-ac3086f77ec0@ispras.ru \
--to=vefanov@ispras.ru \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemdebruijn.kernel@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
all inboxes | Powered by JetHome®