From: Jeremy Kerr <jk@codeconstruct.com.au>
To: netdev@vger.kernel.org
Cc: Matt Johnston <matt@codeconstruct.com.au>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Noam Rathaus <noamr@ssd-disclosure.com>
Subject: [PATCH net 0/4] net: mctp: struct sock lifetime fixes
Date: Tue, 24 Jan 2023 10:01:02 +0800 [thread overview]
Message-ID: <20230124020106.743966-1-jk@codeconstruct.com.au> (raw)
This series is a set of fixes for the sock lifetime handling in the
AF_MCTP code, fixing a uaf reported by Noam Rathaus
<noamr@ssd-disclosure.com>.
The Fixes: tags indicate the original patches affected, but some
tweaking to backport to those commits may be needed; I have a separate
branch with backports to 5.15 if that helps with stable trees.
Of course, any comments/queries most welcome.
Cheers,
Jeremy
---
Jeremy Kerr (3):
net: mctp: add an explicit reference from a mctp_sk_key to sock
net: mctp: move expiry timer delete to unhash
net: mctp: mark socks as dead on unhash, prevent re-add
Paolo Abeni (1):
net: mctp: hold key reference when looking up a general key
net/mctp/af_mctp.c | 10 +++++++---
net/mctp/route.c | 34 +++++++++++++++++++++-------------
2 files changed, 28 insertions(+), 16 deletions(-)
--
2.35.1
next reply other threads:[~2023-01-24 2:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 2:01 Jeremy Kerr [this message]
2023-01-24 2:01 ` [PATCH net 1/4] net: mctp: add an explicit reference from a mctp_sk_key to sock Jeremy Kerr
2023-01-24 2:01 ` [PATCH net 2/4] net: mctp: move expiry timer delete to unhash Jeremy Kerr
2023-01-24 2:01 ` [PATCH net 3/4] net: mctp: hold key reference when looking up a general key Jeremy Kerr
2023-01-24 2:01 ` [PATCH net 4/4] net: mctp: mark socks as dead on unhash, prevent re-add Jeremy Kerr
2023-01-25 13:10 ` [PATCH net 0/4] net: mctp: struct sock lifetime fixes 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=20230124020106.743966-1-jk@codeconstruct.com.au \
--to=jk@codeconstruct.com.au \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=noamr@ssd-disclosure.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.