From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
References: <CALS6=qWHytpevcJqB6TkgzUfUmpoxVeyJtvEKigJH3-cnw7vUQ@mail.gmail.com>
 <CAGXu5jKoHfPHadabqo=7FaOD1O-GRE1-GowfmZSs_oB+snWFaQ@mail.gmail.com> <CALS6=qXN_UxEYV-6kG9_r6kv5joYdVpKU6xOhxLsPAkshzN80g@mail.gmail.com>
In-Reply-To: <CALS6=qXN_UxEYV-6kG9_r6kv5joYdVpKU6xOhxLsPAkshzN80g@mail.gmail.com>
From: Kees Cook <keescook@chromium.org>
Date: Thu, 21 Feb 2019 09:15:54 -0800
Message-ID: <CAGXu5jJ11jw=RZ1X_KT7+9f_vjrvEpjADxdqedKLxSQjreG8Tw@mail.gmail.com>
Subject: Re: classes of methods for gaining access to kernel memory
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
To: Carter Cheng <cartercheng@gmail.com>
Cc: Kernel Hardening <kernel-hardening@lists.openwall.com>
List-ID: <kernel-hardening.lists.openwall.com>

On Thu, Feb 21, 2019 at 8:20 AM Carter Cheng <cartercheng@gmail.com> wrote:
> I was looking over some recent papers for Usenix Security and there are a=
 couple on data oriented programming and I have been wondering if there are=
 known mitigation techniques for this kind of data corruption attack or oth=
er attacks that don't involve control flow hijacking.

Can you share some URLs and/or examples? I'm sure other folks here
would be interested to read those too.

--=20
Kees Cook