Tainting from user space
Posted May 25, 2006 18:19 UTC (Thu) by caitlinbestler
Parent article: Tainting from user space
How does a user mode library obtain access to raw memory
without the kernel granting that access?
If the kernel has granted such access, it should view
itself as tainted whether or not the user-mode code
voluntarily flags itself that way.
As to the core problem, the Linux kernel realy isn't
able to comply because even it does not KNOW that it
has access to true physical memory -- it could itself
be virtualized. So what's the point?
to post comments)