From: Florian Westphal <fw@strlen.de>
To: Eric Dumazet <edumazet@google.com>
Cc: Florian Westphal <fw@strlen.de>,
xingwei lee <xrivendell7@gmail.com>,
pabeni@redhat.com, davem@davemloft.net, kuba@kernel.org,
linux-hams@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, ralf@linux-mips.org,
syzkaller-bugs@googlegroups.com, samsun1006219@gmail.com
Subject: Re: KASAN: slab-use-after-free Read in ip_finish_output
Date: Thu, 14 Mar 2024 12:26:50 +0100 [thread overview]
Message-ID: <20240314112650.GE1038@breakpoint.cc> (raw)
In-Reply-To: <CANn89iLkDwnZdBY8CwkrQwCk2o7EAM9J1sv+uxU1tjKb=VB=Ag@mail.gmail.com>
Eric Dumazet <edumazet@google.com> wrote:
> Thanks for taking a look Florian.
>
> Perhaps not messing with truesize at all would help ?
>
> Something based on this POC :
>
> spin_lock(&qp->q.lock);
> + if (!qp->q.sk) {
> + struct sock *sk = skb->sk;
>
> + if (sk && refcount_inc_not_zero(&sk->sk_refcnt))
> + qp->q.sk = sk;
Unfortunetely I did not get this to work.
sk_refcnt is 0. sk is kept alive by sock_wfree destructor.
I don't know how to recover from this, refcnt cannot be "repaired"
anymore.
I could artificially inflate sk_wmem counter by 1, to prevent release,
but that needs yet another sock_wfree-like destructor.
I'm already not sure how this existing scheme works, there are
multiple places that check for skb->destructor == sock_wfree,
yet we have is_skb_wmem helper that checks __sock_wfree and tcp_wfree.
Removing defrag from output seems like best option, but it will
surely break some scenarios.
Or, I could just fail reasm if sk refcount is already 0, that would
likely work too?
next prev parent reply other threads:[~2024-03-14 11:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 10:00 KASAN: slab-use-after-free Read in ip_finish_output xingwei lee
2024-03-06 10:07 ` Eric Dumazet
2024-03-06 10:36 ` Florian Westphal
2024-03-06 10:41 ` Eric Dumazet
2024-03-12 13:21 ` Florian Westphal
2024-03-12 13:48 ` Eric Dumazet
2024-03-12 14:30 ` Florian Westphal
2024-03-14 11:26 ` Florian Westphal [this message]
2024-03-15 0:07 ` Florian Westphal
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=20240314112650.GE1038@breakpoint.cc \
--to=fw@strlen.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ralf@linux-mips.org \
--cc=samsun1006219@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xrivendell7@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;
as well as URLs for NNTP newsgroup(s).