Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1307941
| From | Daniel Axtens <dja@axtens.net> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC] kernel/panic: place an upper limit on number of oopses |
| Date | 2016-01-13 01:40 +0100 |
| Message-ID | <qQhDH-cE-7@gated-at.bofh.it> (permalink) |
| References | <qQcNJ-5oL-25@gated-at.bofh.it> <qQgHE-80F-23@gated-at.bofh.it> <qQhu2-8P-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Solar Designer <solar@openwall.com> writes: > Jann Horn <jann@thejh.net> wrote: >> To prevent an attacker from turning a mostly harmless oops into an >> exploitable issue using a refcounter wraparound caused by repeated >> oopsing, limit the number of oopses. > > This may also reduce the likelihood of successful exploitation of some > other vulnerabilities involving memory corruption, where an unsuccessful > attempt may inadvertently trigger an Oops. The attacker would then need > to succeed in fewer than the maximum allowed number of Oops'es. Jann's > currently proposed default of 0x100000 is too high to make a difference > in that respect, but people may set it differently. > > On Wed, Jan 13, 2016 at 10:34:39AM +1100, Daniel Axtens wrote: >> I'm torn between making the limit configurable and not adding to the >> massive proliferation of config options. > > What about reusing panic_on_oops for the configurable limit? The > currently supported values of 0 and 1 would retain their meaning, > 2 would panic after 2nd Oops, and so on. I thought about this, then I looked at where panic_on_oops was used and I thought it would be a pretty invasive change. I'm also nervous about changing the semantics of panic_on_oops under people... > > There's overlap with grsecurity's banning of users on Oops, but I think > it makes sense to have both the trivial change proposed by Jann (perhaps > with the reuse of panic_on_oops for configuration) and grsecurity-style > banning (maybe with a low configurable limit, rather than always on > first Oops). > > Alexander
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC] kernel/panic: place an upper limit on number of oopses Jann Horn <jann@thejh.net> - 2016-01-12 20:30 +0100
Re: [RFC] kernel/panic: place an upper limit on number of oopses Daniel Axtens <dja@axtens.net> - 2016-01-13 00:40 +0100
Re: [RFC] kernel/panic: place an upper limit on number of oopses Jann Horn <jann@thejh.net> - 2016-01-13 01:00 +0100
Re: [RFC] kernel/panic: place an upper limit on number of oopses Solar Designer <solar@openwall.com> - 2016-01-13 01:30 +0100
Re: [RFC] kernel/panic: place an upper limit on number of oopses Daniel Axtens <dja@axtens.net> - 2016-01-13 01:40 +0100
Re: [RFC] kernel/panic: place an upper limit on number of oopses Jann Horn <jann@thejh.net> - 2016-01-13 19:10 +0100
csiph-web