From: Mathias Krause <minipli@googlemail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Davidlohr Bueso <davidlohr@hp.com>,
Pax Team <pageexec@freemail.hu>,
Brad Spengler <spender@grsecurity.net>,
linux-kernel@vger.kernel.org,
Mathias Krause <minipli@googlemail.com>
Subject: [PATCH 0/2] IPC DoS fix
Date: Sat, 2 Nov 2013 22:26:37 +0100 [thread overview]
Message-ID: <1383427599-1980-1-git-send-email-minipli@googlemail.com> (raw)
Hi Linus,
this series fixes a bug in the IPC code that allows root to instantly crash
the system. The first patch fixes the bug, the second one prevents msgmax
from getting negative in the first place. As that *might* break existing
userspace (for good?!) it's a separate patch.
The cc list is quite randomly choosen as there seem to be no maintainer for
ipc/. :/
Please apply!
Mathias Krause (2):
ipc, msg: fix message length check for negative values
ipc, msg: forbid negative values for "msgmax"
ipc/ipc_sysctl.c | 6 +++---
ipc/msg.c | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-11-02 21:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 21:26 Mathias Krause [this message]
2013-11-02 21:26 ` [PATCH 1/2] ipc, msg: fix message length check for negative values Mathias Krause
2013-11-03 0:35 ` Linus Torvalds
2013-11-03 8:36 ` Mathias Krause
2013-11-03 11:36 ` [PATCHv2 0/2] IPC DoS fix Mathias Krause
2013-11-03 11:36 ` [PATCHv2 1/2] ipc, msg: fix message length check for negative values Mathias Krause
2013-11-03 11:36 ` [PATCHv2 2/2] ipc, msg: forbid negative values for "msg{max,mnb,mni}" Mathias Krause
2013-11-02 21:26 ` [PATCH 2/2] ipc, msg: forbid negative values for "msgmax" Mathias Krause
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=1383427599-1980-1-git-send-email-minipli@googlemail.com \
--to=minipli@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=davidlohr@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pageexec@freemail.hu \
--cc=spender@grsecurity.net \
--cc=torvalds@linux-foundation.org \
/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®