"Control-Flow Integrity for the Linux kernel: A Security Evaluation" is the work I've done for my Masters thesis where I analyze how the PaX Team's (public) RAP holds up to stop ROP when applied to the Linux kernel. You may want to check out chapter 3. alunos.dcc.fc.up.pt/~up20140…
6
66
5
204
this is a sad joke for a 'thesis' i'm afraid. you should have kept true to your word and kept us in the loop about your findings to avoid all these errors.
1
You should also keep true to your word and assume defeat as I've found ways to bypass RAP on the public test patch?
6
3
Replying to @uid1000
next, irq stacks are not in .data, but percpu allocated. also interrupt context is always associated with a task, the one that was interrupted, it's just not something specific the irq handler can rely on so it has to schedule work in process context if it needs such.

Sep 18, 2019 · 9:51 PM UTC
1