From: Eric Dumazet <edumazet@google.com>
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: kuba@kernel.org, davem@davemloft.net, dsahern@kernel.org,
kuni1840@gmail.com, martin.lau@kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com
Subject: Re: [PATCH v1 net] tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink().
Date: Tue, 8 Oct 2024 11:54:21 +0200 [thread overview]
Message-ID: <CANn89iKWPDs8UXTu8NU+18DM4XE4wHz=CKeSY2AMoxB7tvLyKw@mail.gmail.com> (raw)
In-Reply-To: <20241007235251.84189-1-kuniyu@amazon.com>
On Tue, Oct 8, 2024 at 1:53 AM Kuniyuki Iwashima <kuniyu@amazon.com> wrote:
>
> From: Jakub Kicinski <kuba@kernel.org>
> Date: Mon, 7 Oct 2024 16:26:10 -0700
> > On Mon, 7 Oct 2024 07:15:57 -0700 Kuniyuki Iwashima wrote:
> > > Martin KaFai Lau reported use-after-free [0] in reqsk_timer_handler().
> > >
> > > """
> > > We are seeing a use-after-free from a bpf prog attached to
> > > trace_tcp_retransmit_synack. The program passes the req->sk to the
> > > bpf_sk_storage_get_tracing kernel helper which does check for null
> > > before using it.
> > > """
> >
> > I think this crashes a bunch of selftests, example:
> >
> > https://netdev-3.bots.linux.dev/vmksft-nf-dbg/results/805581/8-nft-queue-sh/stderr
>
> Oops, sorry, I copy-and-pasted __inet_csk_reqsk_queue_drop()
> for different reqsk. I'll squash the diff below.
>
> ---8<---
> diff --git a/net/ipv4/inet_connection_sock.c b/net/ipv4/inet_connection_sock.c
> index 36f03d51356e..433c80dc57d5 100644
> --- a/net/ipv4/inet_connection_sock.c
> +++ b/net/ipv4/inet_connection_sock.c
> @@ -1188,7 +1190,7 @@ static void reqsk_timer_handler(struct timer_list *t)
> }
>
> drop:
> - __inet_csk_reqsk_queue_drop(sk_listener, nreq, true);
> + __inet_csk_reqsk_queue_drop(sk_listener, oreq, true);
> reqsk_put(req);
> }
>
> ---8<---
>
> Thanks!
Just to clarify. In the old times rsk_timer was pinned, right ?
83fccfc3940c4 ("inet: fix potential deadlock in reqsk_queue_unlink()")
was fine I think.
So the bug was added recently ?
Can we give a precise Fixes: tag ?
Thank you.
next prev parent reply other threads:[~2024-10-08 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 14:15 [PATCH v1 net] tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink() Kuniyuki Iwashima
2024-10-07 23:26 ` Jakub Kicinski
2024-10-07 23:52 ` Kuniyuki Iwashima
2024-10-08 9:54 ` Eric Dumazet [this message]
2024-10-08 14:21 ` Kuniyuki Iwashima
2024-10-08 14:28 ` Eric Dumazet
2024-10-08 14:42 ` Kuniyuki Iwashima
2024-10-12 4:01 ` Martin KaFai Lau
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='CANn89iKWPDs8UXTu8NU+18DM4XE4wHz=CKeSY2AMoxB7tvLyKw@mail.gmail.com' \
--to=edumazet@google.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=martin.lau@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).