public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyril <tipecaml@gmail.com>
To: linux-newbie@vger.kernel.org
Subject: Linux 2.6.30 and the "init_cred" symbol
Date: Fri, 05 Mar 2010 04:54:37 +0100	[thread overview]
Message-ID: <4B90807D.7000906@gmail.com> (raw)

Hello all !

I have recently become interested in understanding some recent exploits 
written by Brad Spengler, and especially the one using a null-pointer 
dereference in tun_chr_poll() (this exploit can be found here : 
http://grsecurity.net/~spender/cheddar_bay.tgz).

After taking a look at his code, I decided to compile Linux 2.6.30, so I 
could run the exploit and play with the code a little. I ended up 
cloning the following repository 
(http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.30.y.git;a=summary) 
and doing a checkout of an older branch (in which the patch 
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.30.y.git;a=commit;h=3f8fd3f9f677ce452556aca82473b7fcac370830 
had not been applied). I compiled the kernel as a .deb package, and it 
works perfectly on a virtual machine running Debian.

The problem is I can't get to run the exploit : to do so, I would need 
to be able to resolve the address of the "init_cred" symbol. The fact is 
that the following command does not return anything :
$ grep init_cred /proc/kallsyms

According to http://lwn.net/Articles/287091/, init_cred is "the set of 
credentials used by the init process and by all kernel daemons", which 
makes me think this symbol should be there. Do you think I did something 
wrong when compiling the kernel, or is that normal not to find this 
symbol on certain versions of Linux ?

Thanks in advance !

Cyril Roelandt.
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs

                 reply	other threads:[~2010-03-05  3:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B90807D.7000906@gmail.com \
    --to=tipecaml@gmail.com \
    --cc=linux-newbie@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox