From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>
Cc: davem@davemloft.net, Eric Dumazet <edumazet@google.com>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Sabrina Dubroca <sd@queasysnail.net>
Subject: [PATCH net 0/2] net: diag: fix a potential security issue
Date: Thu, 19 Oct 2017 15:32:23 +0800 [thread overview]
Message-ID: <cover.1508398111.git.lucien.xin@gmail.com> (raw)
This patch is to void the potential security issue that the family
or protocol modules are autoloaded when requesting _diag module by
not requesting _diag module if the family or protocol is not added
or registered in sock_diag and inet_diag.
As the repost of the patch '[PATCH net] sock_diag: request _diag
module only when the family or proto has been registered', this
patchset fixes the compiling errors when INET is not set, and
also split into two patches to make it clear to review.
Xin Long (2):
sock_diag: request _diag module only when the family has been
registered
inet_diag: request _diag module only when the proto has been
registered
include/linux/net.h | 1 +
include/net/protocol.h | 1 +
net/core/sock_diag.c | 21 +++++++++++++--------
net/ipv4/inet_diag.c | 3 ++-
net/ipv4/protocol.c | 6 ++++++
net/socket.c | 5 +++++
6 files changed, 28 insertions(+), 9 deletions(-)
--
2.1.0
next reply other threads:[~2017-10-19 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 7:32 Xin Long [this message]
2017-10-19 7:32 ` [PATCH net 1/2] sock_diag: request _diag module only when the family has been registered Xin Long
2017-10-19 7:32 ` [PATCH net 2/2] inet_diag: request _diag module only when the proto " Xin Long
2017-10-21 1:27 ` [PATCH net 0/2] net: diag: fix a potential security issue David Miller
[not found] ` <CADvbK_fWmmC3ggpoT--Pxk3GxZ8Gq_rbdFGTuXk-BuTHTO=eXw@mail.gmail.com>
2017-10-21 6:18 ` Eric Dumazet
2017-10-21 6:51 ` Xin Long
2017-10-21 7:45 ` Eric Dumazet
2017-10-21 8:45 ` Xin Long
2017-10-21 9:45 ` Xin Long
2017-10-21 11:16 ` David Miller
2017-10-21 11:14 ` David Miller
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=cover.1508398111.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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).