From: Steve Grubb <sgrubb@redhat.com>
To: oss-security@lists.openwall.com
Cc: Linux Audit <linux-audit@redhat.com>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: [oss-security] CVE request: Another Linux syscall auditing bug
Date: Thu, 19 Jun 2014 23:37:39 -0400 [thread overview]
Message-ID: <5505250.3yQZm9nuEg@x2> (raw)
In-Reply-To: <CALCETrVuwhQ1CST8dbaUYTDFtOn36Nts-SzPV+Uwz=qiXoiTtg@mail.gmail.com>
Hi,
Reminder again...please report bugs to linux-audit mail list.
On Thursday, June 19, 2014 06:26:38 PM Andy Lutomirski wrote:
> On a 32-bit x86 kernel with syscall auditing enabled, syscall(1000)
> will cause an OOPS. This problem goes at least as far back as Linux
> 3.11 and appears to be present in Linux 3.15 as well. I suspect that
> this bug is very old.
>
> In order to see this bug, you'll need syscall auditing on (auditctl -e
> 1 will do that) and you'll need 'sep' in flags in /proc/cpuinfo. That
> means that qemu -cpu qemu64 will not be exposed to this bug, but qemu
> -cpu host will on any recent CPU.
>
> Mitigations include:
> - Running under ptrace or strace.
> - Using any seccomp filter at all (phew!)
> - Turning off SEP (which is a big slowdown on all syscalls)
> - auditctl -a task,never
>
> I'd be rather surprised if this can be used for anything other than
> DoS, although the same underlying bug could potentially have more
> serious consequences.
>
> This bug was found (inadvertently, I presume) by Toralf Förster. The
> patch here:
>
> http://lkml.kernel.org/g/CALCETrW7U4AHG-a9oPbOt31z3wgzhjSu8b+yGpdM4+vNinKgsA
> @mail.gmail.com
>
> is reported to fix the bug, but it should not be considered to be
> well-tested.
>
> --Andy
parent reply other threads:[~2014-06-20 3:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CALCETrVuwhQ1CST8dbaUYTDFtOn36Nts-SzPV+Uwz=qiXoiTtg@mail.gmail.com>]
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=5505250.3yQZm9nuEg@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=luto@amacapital.net \
--cc=oss-security@lists.openwall.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