lkml.org 
[lkml]   [2004]   [Jan]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
Subjectchecking the calling eip of a system call
From
Hello,

A friend of mine wrote some kernel code that without getting too much into
how exactly the code works, checks the calling eip of a system call and
just verifies that its not coming from 'bad' areas, bad areas being
defined as the stack/heap/data/bss, While I realize this hardly fixes a
possible buffer overflow (this wouldnt affect a return into libc type
exploit for instance). He recently asked me to take a look at it and give
him my opinion to see if he should further development in it. So really my
question is, assuming the impletemention of it is good- what problems
could this present to the kernel itself? It seems like a decent basic
sanity check - but there is nothing like it (AFAIK) in the kernel already.
So as I said, what problems could this present, other than breaking self
modifying code and the likes?

thanks,
jnf
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:59    [W:0.017 / U:0.080 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site