[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1843140.sMbTx3NoQB@x2>
Date: Wed, 28 May 2014 21:06:40 -0400
From: Steve Grubb <sgrubb@...hat.com>
To: oss-security@...ts.openwall.com
Cc: Andy Lutomirski <luto@...capital.net>
Subject: Re: CVE request: Linux kernel DoS with syscall auditing
On Wednesday, May 28, 2014 02:45:59 PM Andy Lutomirski wrote:
> Issuing a system call with a random large number will OOPS, depending
> on configuration. A configuration that will enable this bug is:
>
> # auditctl -a exit,always -S open
>
> No privilege whatsoever is required to trigger the OOPS.
Do you have more information about this? I don't get an oops and I run with
the audit system on all the time.
> It's possible that this can be extended to more than just a DoS --
> with some care and willingness to exploit timing attacks, this is a
> read of arbitrary single bits in kernel memory.
What platform? Where do the arbitrary bits go? What syscall are we talking
about?
There is a linux-audit mail list which seems to not have any emails about this
problem. That is really the best place to discuss any issues with this
subsystem and get it fixed.
Thanks,
-Steve
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
