From: Andy Lutomirski <luto@amacapital.net>
To: Andy Lutomirski <luto@amacapital.net>,
Philipp Kern <pkern@google.com>,
"H. Peter Anvin" <hpa@linux.intel.com>,
linux-kernel@vger.kernel.org, "H. J. Lu" <hjl.tools@gmail.com>,
Eric Paris <eparis@redhat.com>,
security@kernel.org, greg@kroah.com, linux-audit@redhat.com
Subject: [PATCH v2 0/2] Fix auditsc DoS and mark it BROKEN
Date: Wed, 28 May 2014 18:43:59 -0700 [thread overview]
Message-ID: <cover.1401327752.git.luto@amacapital.net> (raw)
CONFIG_AUDITSYSCALL is awful. Patch 2 enumerates some reasons.
Patch 1 fixes a nasty DoS and possible information leak. It should
be applied and backported.
Patch 2 is optional. I leave it to other peoples' judgment.
Andy Lutomirski (2):
auditsc: audit_krule mask accesses need bounds checking
audit: Move CONFIG_AUDITSYSCALL into staging and update help text
Andy Lutomirski (2):
auditsc: audit_krule mask accesses need bounds checking
audit: Mark CONFIG_AUDITSYSCALL BROKEN and update help text
init/Kconfig | 13 ++++++++-----
kernel/auditsc.c | 27 ++++++++++++++++++---------
2 files changed, 26 insertions(+), 14 deletions(-)
--
1.9.3
next reply other threads:[~2014-05-29 1:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 1:43 Andy Lutomirski [this message]
2014-05-29 1:44 ` [PATCH v2 1/2] auditsc: audit_krule mask accesses need bounds checking Andy Lutomirski
2014-05-29 2:23 ` Eric Paris
2014-05-29 2:27 ` Andy Lutomirski
2014-05-29 2:43 ` Eric Paris
2014-05-29 2:46 ` Andy Lutomirski
2014-05-29 1:44 ` [PATCH v2 2/2] audit: Mark CONFIG_AUDITSYSCALL BROKEN and update help text Andy Lutomirski
2014-05-29 2:09 ` Eric Paris
2014-05-29 2:40 ` Andy Lutomirski
2014-05-29 2:54 ` Eric Paris
2014-05-29 3:01 ` Andy Lutomirski
2014-05-29 13:05 ` Steve Grubb
2014-05-29 16:04 ` Andy Lutomirski
2014-05-29 16:25 ` Steve Grubb
2014-05-29 16:46 ` Andy Lutomirski
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.1401327752.git.luto@amacapital.net \
--to=luto@amacapital.net \
--cc=eparis@redhat.com \
--cc=greg@kroah.com \
--cc=hjl.tools@gmail.com \
--cc=hpa@linux.intel.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pkern@google.com \
--cc=security@kernel.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