[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jKoHfPHadabqo=7FaOD1O-GRE1-GowfmZSs_oB+snWFaQ@mail.gmail.com>
Date: Wed, 20 Feb 2019 17:17:07 -0800
From: Kees Cook <keescook@...omium.org>
To: Carter Cheng <cartercheng@...il.com>
Cc: Kernel Hardening <kernel-hardening@...ts.openwall.com>
Subject: Re: classes of methods for gaining access to kernel memory
On Sun, Feb 10, 2019 at 3:13 AM Carter Cheng <cartercheng@...il.com> wrote:
> I was reading a paper on kernel data attacks and the paper mentions methods for gaining control of kernel memory beyond overflow type attacks. This would seem to suggest that methods exist for this in certain cases beyond what can be caught by spatial safety checks. Are there general classes of such methods that one needs to be aware of? And what are they?
If I follow what you're asking, I'd think race conditions would be an
example of another major class of attacks against the kernel. For
example, look at the DirtyCOW attack: that was a race condition
against the kernel's VFS that wouldn't get caught by bounds checking,
etc, etc.
--
Kees Cook
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
