linux-kernel - Re: [Security] proactive defense: using read-only memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <32620.1290039147@localhost>
Date:	Wed, 17 Nov 2010 19:12:27 -0500
From:	Valdis.Kletnieks@...edu
To:	Pavel Machek <pavel@....cz>
Cc:	Kees Cook <kees.cook@...onical.com>, linux-kernel@...r.kernel.org
Subject: Re: [Security] proactive defense: using read-only memory

On Wed, 17 Nov 2010 11:00:54 +0100, Pavel Machek said:

> > - Entry points to set_kernel_text_rw() and similar need to be blockable.
> >   Having these symbols available make kernel memory modification trivial;
> 
> What prevents attacker to just inlining those functions in the
> exploit?

Quite often, you are limited on how many bytes of exploit code you can inject.
If you have to do the whole thing in (say) 139 bytes, having to inlinine even
one function may make the exploit impossible to run.


Content of type "application/pgp-signature" skipped