From: David Miller <davem@davemloft.net>
To: ebiggers@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
maowenan@huawei.com, xiyou.wangcong@gmail.com,
lorenzo@google.com, penguin-kernel@i-love.sakura.ne.jp,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH net] net: socket: set sock->sk to NULL after calling proto_ops::release()
Date: Mon, 25 Feb 2019 10:41:56 -0800 (PST) [thread overview]
Message-ID: <20190225.104156.1331861489514486019.davem@davemloft.net> (raw)
In-Reply-To: <20190221221356.173485-1-ebiggers@kernel.org>
From: Eric Biggers <ebiggers@kernel.org>
Date: Thu, 21 Feb 2019 14:13:56 -0800
> From: Eric Biggers <ebiggers@google.com>
>
> Commit 9060cb719e61 ("net: crypto set sk to NULL when af_alg_release.")
> fixed a use-after-free in sockfs_setattr() when an AF_ALG socket is
> closed concurrently with fchownat(). However, it ignored that many
> other proto_ops::release() methods don't set sock->sk to NULL and
> therefore allow the same use-after-free:
...
> Rather than fixing all these and relying on every socket type to get
> this right forever, just make __sock_release() set sock->sk to NULL
> itself after calling proto_ops::release().
>
> Reproducer that produces the KASAN splat when any of these socket types
> are configured into the kernel:
...
> Fixes: 86741ec25462 ("net: core: Add a UID field to struct sock.")
> Signed-off-by: Eric Biggers <ebiggers@google.com>
Applied and queued up for -stable, thanks Eric.
prev parent reply other threads:[~2019-02-25 18:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 22:13 Eric Biggers
2019-02-22 2:51 ` Al Viro
2019-02-22 17:45 ` Eric Dumazet
2019-02-22 17:57 ` Eric Biggers
2019-02-22 18:25 ` Eric Dumazet
2019-02-22 19:08 ` Al Viro
2019-02-22 18:05 ` Cong Wang
2019-02-25 18:41 ` David Miller [this message]
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=20190225.104156.1331861489514486019.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ebiggers@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@google.com \
--cc=maowenan@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=viro@zeniv.linux.org.uk \
--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
all inboxes | Powered by JetHome®